See the supported connectors for Application Integration.
A trigger is an external event that initiates a task, or sequence of tasks, in an integration. You can think of a trigger as an entry point to your integration and the event tied to the trigger causes the tasks associated with the trigger to run.
You can add multiple triggers to your integration. However, when an event occurs, only the trigger associated with the event begins executing its tasks. For more information, see Adding multiple triggers in an integration.
For the list of all the available out-of-the-box triggers, see All triggers.
Connector Event triggers (Preview)
Adding multiple triggers in an integrationYou can add one or more triggers in an integration where each trigger is associated with a different task. The integration starts from the trigger for which the event occurs. For example, consider your integration has two triggers where
Trigger-1is associated with
Trigger-2is associated with a downstream task
Task-5. Now suppose an event triggers
Trigger-2, the integration runs from
If multiple triggers run at the same time, each trigger runs its copy of the integration. In the
preceding example, if both
Trigger-2 run simultaneously,
Trigger-1 runs the integration from
Task-1 onwards, and
runs a separate copy of the integration from
Task-5 onwards. There is no overlap between the execution flows of the two integrations.