You can create your flows from scratch or by using a pre-built template.
Creating an event-driven flow from scratch
- On the Dashboard in IBM App Connect Designer, click New > Event-driven flow.
- Enter a name that identifies the purpose of your flow.
- Select the source application, and the event to trigger the flow.
- Select and configure one or more target applications, and the actions to be performed.
- Optionally, you can use the Toolbox tab to provide specialized processing. For example, you can add an “If” node to provide conditional processing, or a “For each” node to process retrieved items.
- To start the flow, open the options menu [⋮] in the banner and click Start flow. Then click Dashboard to exit the flow.
See the tutorial Creating an event-driven flow.
For more examples of creating event-driven flows, see:
Creating an event-driven flow from a template
A quick and easy way to create flows is to start with a pre-built template. The App Connect Templates gallery contains a growing catalog of templates, covering a range of cognitive, marketing, sales, support, business ops, e-commerce, and finance use cases. These templates make use of key applications such as Salesforce, SAP, Netsuite, Watson, MS Dynamics, Marketo, and others.
To browse and perhaps use a template, click the template tile in the gallery. In the overlay displayed, you can read information about how to use the template and can click a button to create the flow from the template. You can then validate the flow, which opens in the flow editor, to ensure you are connected to the appropriate accounts, review the mappings, and optionally adapt the flow for your own needs.
Another helpful way to create a pre-built flow is to import a flow definition file that’s provided as a sample or generated from an exported flow:
- Some sample files are included in the ot4i/app-connect-samples repository on GitHub, and referenced from blog posts, tutorials, and other doc pages.
- You can use the export function in App Connect to export a flow definition to a file. The file can then be imported into other App Connect environments or shared with other App Connect users who want to configure identical or similar flows. For information about exporting and importing flows, see Exporting and importing flows.