Creating flow templates is an essential step to offer integrations in your app. This article will take you through the process of building a flow template. Ready to create your first template?

<aside> 💡 Quick Start

1. Choose connector and trigger
2. Choose connector and action
3. Provide data mapping
4. Save and publish

</aside>

Choose your trigger

Drag the app that should do the trigger from the right side into the field for the trigger. Now you can select your trigger from the drop down menu.

Provide additional details

Sometimes it is useful or even necessary to provide some additional details for the flow to work properly.

1. Array Splitting Key Sometimes the API response is an array, or may contain an array as a field inside the returned object. The Array Splitting Key tells the system that instead of returning the array, it should split it and send back individual objects. You can find it in the API documentation for the connector you want to use.
2. Snapshot Key The system saves snapshots to only grab newly created objects. It is often a field called something like "lastUpdated," "modfiedDate," etc. Because it is different for every API (and in some APIs it is different for every endpoint), it has to be provided as a parameter here.
3. Sync Param This is similar to the snapshot key, except it is used in cases where an API supports "delta" lookups, and will only return newly created or edited objects.
4. Other Server By default, the library we use to make the API calls will only function for servers which are defined in the API specification. However, many services use more server names than what are able to be included in the spec. Sometimes they are even different for each client.

Choose your action

Now, drag the second app to the action field and choose the action from the dropdown. Here, you can later add additional details in the “Other Server” field.