LinkedIn
Twitter
Private Triggers
Private triggers enable you to break large flows into various subflows. You can invoke private triggers only from other integration flows within Application Integration. Being invokable only from other integrations increases security and reduces the risk. You can view the execution logs for a private task in the execution logs of the invoker integration.
The following list states the benefits of using private triggers:
- Minimize cost: Private triggers are not counted towards execution run pricing.
- Increases security: Restrict flows to be invoked only from other integrations as private triggers cannot be triggered independently from public APIs.
- Improve performance: Private triggers reduces the latency between sub-integration callout.
Create and configure the private trigger workflow
1. In the Google Cloud console, create an integration.
2. In the integration editor navigation bar, click Triggers to view the list of available triggers.
3. Click and place the Private element to the designer.
4. Click the Private Trigger element in the integration editor to view the trigger configuration panel. The configuration panel displays the Trigger ID, which is a machine-generated ID in the format private_trigger/TRIGGER_NAME. No further configuration is required for this trigger
5. More details
Invoke Private trigger from another integration
After published an integration that has a private trigger configured, you can invoke this trigger from another integration.
You can have more than one private trigger in your integration. Each private trigger is assigned a unique Trigger ID.
You can view the execution logs for a private trigger in the logs of the main execution workflow.
Private triggers can be invoked from the following flow control tasks:
Limitation
If your private trigger workflow contains any of the following async tasks, then you can't trigger the private workflow from the main workflow with the SYNC execution strategy:
And for published private trigger workflow, it is not testable due to security concerns, it can be tested for draft version or invoking from other integrations to do the testing
Conclusion
In summary, integrating private triggers into workflows offers several advantages: cost reduction by exempting them from additional execution run pricing, heightened security by restricting flow invocation to public calls, and improved performance through decreased latency in sub-integration callouts. Moreover, the inclusion of all execution logs within the top-level integration execution simplifies debugging processes, further enhancing operational efficiency and maintenance capabilities.
