When you create an event-driven flow, you first need to identify which event in the source application should trigger the flow. Depending on the application and event, you’ll also need to ensure that certain prerequisites are met in the source application itself. For example, if you want your flow to trigger when a new attendee registers for an event in Eventbrite, you’ll need to have one or more events set up in Eventbrite, which should be monitored for new attendees.
For certain App Connect events, simply selecting the event name in the flow editor is enough and you won’t be prompted to complete any fields; for example, if you want your flow to trigger when a new lead is added to Insightly (as shown in the following image) or when a new email message is received in Gmail.
For other event types, you might need to complete a few fields; for example:
- If you want your flow to trigger when a new task is added to Asana, you’ll need to identify an existing team and project that should be monitored for new tasks, as shown in the image below.
- If you want to trigger a flow when a new message is posted in Slack, you’ll need to create a Slash command in the Slack UI that uses a Callback URL provided by App Connect.
- If you want to use a Marketo event to trigger a flow, you’ll need to configure and activate a Webhook in Marketo, with a Callback URL provided by App Connect.
- If you want to trigger a flow by polling an application for new or updated objects, you’ll need to specify timestamp fields that indicate when the object was created or modified, the timestamp format and time zone, and a polling frequency. For example, you can poll an IBM Db2 database for new or updated rows in a table and then trigger the flow whenever such rows are detected.
You can also use the Scheduler in the App Connect toolbox to trigger your flows at regular intervals or at specific dates and times. For more information, see Configuring your flow to run at scheduled times.