Automation
Parameter Input
Declares the inputs a flow runs with — a customer id, an as-of date — and hands them on as one row with a typed column per parameter.
When to use it
Use it instead of hard-coding run inputs in node settings, so the same flow runs for another customer or another month by changing one value.
In a pipeline
Parameter InputJoin TablesFilter RowsExport CSV
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Parameters (JSON) | textarea | Yes | [{"name":"customer_id","type":"text","default":""},{"name":"as_of_date","type":"date","default":"2026-01-31"}] |
| Values for this run (JSON) | textarea | — | {"customer_id":"C-1042"} |
Example
A customer and a cut-off date
- Parameters (JSON)=[{"name":"customer_id","type":"text","default":"C-1001"},{"name":"as_of_date","type":"date","default":"2026-01-31"},{"name":"min_total","type":"number","default":"100"}]
- Values for this run (JSON)={"customer_id":"C-1042"}
| customer_id | as_of_date | min_total |
|---|---|---|
| C-1042 | 2026-01-31 | 100 |
customer_id comes from Values for this run; the other two from their defaults. min_total is a number, so later formulas can compare with it.
Worth knowing
- Use it instead of hard-coding run inputs: every parameter is also a $variable ($customer_id) in any node's settings, and a column you can join onto your data.
- A published flow's callers (the Flow API), a webhook or a parent flow set parameters by name, like Variables; /schema lists them.
- Each parameter is {"name", "type", "default"}; type is text, number, date (YYYY-MM-DD) or boolean (true / false, yes / no). A blank default gives an empty value.
- Values for this run is for manual runs: fill in only the names you want to change and clear it again afterwards. A name that is not declared is reported, not ignored.
- Names must be unique and cannot start with __, which FlowDoo keeps for internal columns.