A flow needs only a source and a destination, but most real flows do more: look up a customer ID before creating an order, copy a file to an archive on the way through, send the same records to a second application, call a tool, or route records down different branches. You add all of these from the same place on the canvas. This article covers adding a step and configuring the settings that are specific to lookup and transfer steps; each other step kind links to the article that explains it.
Add a step
- Go to Build
> Flows, and then select the flow.
- In Flow builder, select Add step at the end of the flow, or select +
between two steps.
- Select the Application and the Step type, select or create a Connection, name the step, and then select Next. For how integrator.io suggests steps you already have, see Reuse an existing flow step.
Steps run in the order they appear on the canvas. You can drag a step to a different position; its mapping, filters, and other settings move with it. Check them after you reorder.
Lookup steps
A lookup retrieves additional data for each record and adds it to the record — for example, the customer details for each order a source exported. Choose one of two step types:
- Look up additional records (per record) — queries another application or database and adds the results to each record.
- Look up additional files (per record) — retrieves a file for each record and attaches it as a BLOB. Available only for applications whose API supports BLOB export.
After the connection and name, set the lookup:
| Setting | What it does |
|---|---|
| One to many | Yes (advanced) if each looked-up record contains child records that should each become a record of its own; then enter the Path to many — the path to the array to split. No if each lookup result supplements one record. |
| API Name and Operation | The API and operation to call. The options depend on the application. |
| Configure search parameters | Select Launch to refine the query. The settings depend on the API you chose. |
| Export type | All returns everything that matches. Delta returns only what changed since the flow last ran. Once returns one record, for testing. Limit returns the number of records you set. |
A lookup adds data to every record. A page can't be larger than 5 MB, and neither can a single record.
To merge the lookup's results into each record, configure results mapping on the step; see Lookups and results mapping. To use a lookup cache instead of calling an application, see Lookup caches overview.
Transfer steps
A transfer step copies the records or files passing through the flow to another location without changing them, and the flow continues to the next step with the original data. Use Transfer files into destination application as the step type and configure the destination as you would an import. For a worked example, see Example file transfer: Salesforce to NetSuite.
Additional destinations
A flow can have more than one import. Records reach each destination in canvas order, and the response from one import is available to the steps after it; see Response mapping, results mapping, and handling failed records.
Other step kinds
| Step | See |
|---|---|
| Tool | Use tool import steps in a flow |
| AI agent | Create an AI agent |
| Guardrail | Understand Celigo guardrails |
| Publish to a topic | Publish messages from a flow |
| Branching | Manage branching in your flow |