Every step in Flow builder has a menu of options that shape the records it handles: filters that decide which records continue, transformations that reshape them, hook scripts that run custom logic, and mapping that matches fields to the destination. The menu is grouped by Incoming data (what happens before the step runs) and Outgoing data (what happens to its results). This article is a map of those options — which step kinds have each one, what it does, and where it's explained in full.
Go to Build > Flows, open a flow, point to the step, and then select Actions
. An option that's already configured shows Already added.
Source steps (exports and listeners)
| Option | What it does | See |
|---|---|---|
| Schedule override | Gives this source its own schedule instead of the flow's. | Schedule a flow |
| Set as source for preview | When the flow has several sources, chooses whose records appear in the previews of later steps. | Run a flow |
| Outgoing data: Transformation | Renames, removes, or restructures fields in each record before it moves on. | Transform data in integrator.io |
| Outgoing data: Output filter | Decides which records continue to the next step; the rest are dropped. | Filter records in a flow |
| Outgoing data: Pre save page hook | Runs a script on each page of records before the page is saved. | Export hooks |
| Clone | Adds a copy of the step to the flow — for example, a second copy of an export with its own schedule override. | Schedule a flow |
| Remove | Removes the step from the flow. The export itself stays in your account. | — |
Lookup steps
| Option | What it does | See |
|---|---|---|
| Incoming data: Input filter | Decides which records this step processes; records it rejects skip the step but continue down the flow. | Filter records in a flow |
| Incoming data: Mapping | Maps source fields to the lookup's fields. | Mapper 2.0 |
| Outgoing data: Transformation | Restructures the lookup's results. | Transform data in integrator.io |
| Outgoing data: Output filter | Allows only lookup results that match a condition to continue. | Filter records in a flow |
| Outgoing data: Pre save page hook | Runs a script on each page of results before the page is saved. | Export hooks |
To merge what the lookup returns back into each record, configure results mapping; see Lookups and results mapping.
Import steps
AI agent steps, guardrail steps, and publish steps (an import to Celigo Topics) have the same menu as any other import.
| Option | What it does | See |
|---|---|---|
| Incoming data: Input filter | Decides which records this step processes; records it rejects skip the step but continue down the flow. | Filter records in a flow |
| Incoming data: Pre map hook | Runs a script on the records before mapping. | Import hooks |
| Incoming data: Mapping | Maps source fields to the destination's fields. | Mapper 2.0 |
| Incoming data: Post map hook | Runs a script on the mapped records before they're sent. | Import hooks |
| Outgoing data: Post submit hook | Runs a script after the destination responds. | Import hooks |
| Outgoing data: Transformation | Restructures the import's result data for the steps after it. | Transform data in integrator.io |
| Outgoing data: Response mapping | Makes the destination's response available to later steps. | Response mapping, results mapping, and handling failed records |
| Outgoing data: Post response map hook | Runs a script after the response is mapped. | Import hooks |
| Outgoing data: Error handling | Sets what happens to a record the step fails on. | Unified error view |
| Clone | Adds a copy of the step to the flow. | — |
| Remove | Removes the step from the flow. The import, agent, or guardrail itself stays in your account. | — |
A guardrail step flags records rather than stopping them, so the routing happens in the steps after it — branching, filters, or mapping on the result it returns; see Understand Celigo guardrails. For AI agent steps, see Create an AI agent; for publish steps, see Publish messages from a flow.
Tool steps
A tool step has the import menu without Post submit hook and Transformation.
| Option | What it does | See |
|---|---|---|
| Incoming data: Input filter | Decides which records this step processes; records it rejects skip the step but continue down the flow. | Filter records in a flow |
| Incoming data: Pre map hook | Runs a script on the records before mapping. | Import hooks |
| Incoming data: Mapping | Maps source fields to the tool's inputs. | Mapper 2.0 |
| Incoming data: Post map hook | Runs a script on the mapped records before they're sent to the tool. | Import hooks |
| Outgoing data: Response mapping | Makes the tool's response available to later steps. | Response mapping, results mapping, and handling failed records |
| Outgoing data: Post response map hook | Runs a script after the response is mapped. | Import hooks |
| Outgoing data: Error handling | Sets what happens to a record the tool fails on. | Use tool import steps in a flow |
| Clone | Adds a copy of the step to the flow. | — |
| Remove | Removes the step from the flow. The tool itself stays in your account. | — |
Preview a step's data
Each step's editor has a preview that shows the request integrator.io will send and a sample of what comes back, so you can check a step without running the flow. See Preview export data and Preview import data.