Automation
Macro / Sub-flow
Uses a saved flow as a single step: these rows go into its first step (with columns renamed if you say so), and whatever it produces comes back out.
When to use it
Use it when the same run of steps — a shared cleansing flow, a standard enrichment — appears in many flows and should be fixed in one place.
In a pipeline
File InputMacro / Sub-flowExport CSV
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Flow | select | Yes | Select a saved flow… |
| Rename columns on the way in (JSON) | textarea | — | {"Customer":"customer_id"} |
Example
Reuse the shared cleanse
- Rename columns on the way in (JSON)={"Customer":"customer_id"}
| Customer | Total |
|---|---|
| c-1042 | 120 |
The saved flow receives the rows with Customer renamed to customer_id, in place of what its first step would have read.
Worth knowing
- Edit the saved flow once and every flow that uses it as a Macro gets the change on its next run.
- A preview runs the sub-flow as a preview too: nothing is written.
- Sub-flows may use sub-flows, at most 3 levels deep, and never themselves.