Triggers
Triggers are the components that initiate a Flow. This article describes the trigger types and how to use them in your Flows. For more information, see Introduction to Automation.
Scheduling
Use the scheduling trigger when you need the flow to start by assigning the dates and times of your choosing. Select the frequency and the time you would like your trigger to run. You can also choose a start date and an ending date.
When you finish setting your scheduling presets, you can complete your flow by adding conditions and actions.
Data Load Finish
Use the Data Load Finish trigger when you need the flow to start each time a data load job is finished on the dataset. Select the dataset name you would like this flow to monitor. This trigger supports only managed datasets that have been loaded at least once.
Records Added
Use the Records Added trigger when you need the flow to run as soon as new data is received – for example, when a new record has been added to a data source. This trigger also starts each time a record is added by a data load process.
To set up this trigger, drag and drop the Records Added trigger, then select the name of the dataset to monitor. The flow starts when a change is detected.
Note: This trigger runs with each record addition and can have substantial cost implications, depending on the number of records added.
Records Updated
Use a Records Updated trigger to start the flow when information in an existing dataset has been updated. This trigger also starts each time a record is updated by a data load process. Select the dataset name to monitor, then add conditions and actions.
Note: This trigger runs with each record update and can have substantial cost implications, depending on the number of records updated.
Webhook
Use the Webhook trigger to automatically generate a unique URL for the flow from an external application.
Select Generate Another to replace the current URL.
Note: Replacing a URL cannot be undone. Use this feature with care.
To prevent unauthorized end users from starting a flow using the webhook URL, select Require Authentication. This option requires end users to be authenticated using JSON web tokens (JWT). For more information, see Embedding Widgets Using a Security Token.