You are here:
Create record-triggered orchestrations to respond to record changes that require user input or additional record updates. Specify whether to trigger the orchestration based on new and changed records of a specific object in the Start element. Use Flow Trigger Explorer to manage the order of record-triggered automations.
| View supported editions for Flow Orchestration. |
Autolaunched orchestrations don’t use triggers and need another mechanism to launch them, such as custom Apex classes or custom URLs.
In Flow Orchestration, the trigger occurs after a record is saved.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.