Start a flow
When a Data Table row changes
Starts the flow once for each row added, changed or deleted in a Data Table.
Nodes › TriggersOpen in Neblex
- Good for
- Reacting to your own tables
- Role
- Starts a flow
- Find it in
- Nodes › Triggers
When to use it
- A change to a row in a Data Table should start work, whoever made it: a flow, a person or an import.
- Rows should be handled in the order they changed.
- A deleted row should still arrive with its last values.
Reach for something else when
Poll for changesWhen the data lives in another system's database.Data tableWhen a step in a running flow reads or writes the table.
Example
Watch the Orders table for changed rows and email the customer when status becomes shipped.
How it works
- Settings
- Data table; Start on: a row is added, changed or deleted [all three].
- Behaviour
- Every change counts, whoever makes it: a flow's Data Table step, the Data Tables page, an import or the API. The flow starts after the change is saved, once per changed row, with one record: the row by column name with
id,createdAt,updatedAtand_change(added,changedordeleted). A deleted row arrives as it was. An upsert counts as added for a new row and changed for an existing one. A row's changes start runs in the order they were made. The flow watches from the moment it is active and stops when it is switched off; a start the platform cannot make yet (the monthly quota, storage) is tried again until it starts. Emptying a table starts one run per removed row. - Example
- Watch Orders for changed rows and send the customer an email when
statusbecomesshipped.
Add it to a flow
- Open the flow from Build › Workflows.
- Open Nodes and find When a Data Table row changes under Triggers. Drag it onto the canvas as the first step.
- Connect it to the next step and open its settings with ✎ Edit.
- Save and test with Run, then set the flow Active so it starts on its own.
More in Start a flow
WebhookStarts the flow the moment another system calls its address.Nodes › TriggersForm (starts flow)Starts the flow when someone submits a form, with their answers as the input.Nodes › TriggersScheduleRuns the flow on a repeating interval or at set times.Nodes › TriggersPoll for changesChecks a system regularly and starts a run only for records that are new or changed.Nodes › TriggersLive streamSubscribes to a queue, topic or stream and runs the flow for each message as it arrives.Nodes › TriggersWhen calledMakes the flow callable by other flows, the API and AI agents, with a declared input and output.Nodes › Triggers