In an event-driven flow, you identify an event that can occur to trigger the flow to run. The event can be a change in the first application in the flow (the source application), a scheduled interval or specific dates and times, or when called by another flow. You also identify actions to be performed in one or more target applications when the flow runs. The flow links the event to the actions so that, whenever the event occurs, the actions are automatically triggered in the target applications.
For example, you might create a flow so that at scheduled dates and times (the event), App Connect automatically performs a sequence of actions to retrieve data about sales contacts from an on-premises Db2 database, use IBM Watson to analyse the tone of any comments in the data, and then update or create a lead in Salesforce.
A quick and easy way to create an event-driven flow is to use a pre-built template from the App Connect gallery of templates, or to import a flow definition file from supplied samples or from an exported flow.
Alternatively, you can create a new flow from scratch, perhaps following one of the App Connect tutorials for specific use cases. You just need to select an event to trigger the flow, one or more actions to be performed in target applications or APIs, and optionally select specialized processing such as conditional logic, logging, batch processing, and CSV parsing.