You can create your flows from scratch or by using a pre-built template.

Creating flows for an API from scratch

If you want a developer to be able to create an app that makes use of the data in your cloud-based applications, you can provide an API. For example, you might provide an API that can create, retrieve, and update customers in your CRM system.

Creating flows for an API involves the following steps:

  1. On the Dashboard in IBM App Connect Designer, click New > Flows for an API.
  2. Enter a name that identifies the purpose of your flow.
  3. Create one or more models that define the structure of the objects that you want to create or retrieve.
  4. Choose the create, retrieve, or update operations to perform against each model.
  5. Configure a flow that implements each operation:
    1. Add one or more target applications that hold the data.
    2. Optionally 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.
  6. Click Start API to save and start your flow.

See the tutorial Creating flows for an API.

For more examples of creating flows for an API, see:

Creating flows for an API from a template

A pre-built template provides a quick and easy way to create flows.

The App Connect Templates gallery contains a growing catalog of templates that make use of key applications such as Salesforce, SAP, Netsuite, Watson, MS Dynamics, Marketo, and others. The Templates gallery contains templates for both event-driven flows and flows for APIs, and you can access and use the templates for both flow types in the same way. For further information about accessing and using a template for an API flow, see Creating an event-driven flow from a template.

You can also create a pre-built flow by importing a flow definition file that was exported from another App Connect environment or by another user. For information about exporting and importing flows, see Exporting and importing flows.

Join The Discussion

Your email address will not be published. Required fields are marked *