Trigger data contains the values received when a workflow starts. Later nodes can use fields from that payload and outputs from earlier connected steps. Capture a real sample for your trigger so you can choose fields that actually exist.
Capture trigger data
- Add and configure the workflow’s trigger.
- Click Test Flow → Listen new response. The editor saves the workflow before it starts listening.
- Send a safe test event through the configured trigger, such as a test form submission or webhook request.
- Wait for the editor to report that a sample was captured.
Screenshot to add: Test Flow panel showing Listen new response and captured trigger sample
Map a value into a later node
- Select the node that needs the data and open its settings.
- In a supported field, open the variable picker.
- Choose a field from the trigger payload or from an earlier step in the connected workflow path.
- Check the inserted variable and save the workflow.
- Test the workflow again and confirm that the later node receives the expected value.
Screenshot to add: Variable picker showing trigger fields and earlier node outputs
Understand variable sources
- Trigger data is shown under the configured trigger’s label after sample data or a supported trigger schema is available.
- Earlier node outputs are listed for steps that come before the selected node in the connected path.
- Variables use tokens such as
{{trigger.field}}for trigger fields and{{nodes.node-id.field}}for node outputs. Choose the actual field from the picker rather than guessing its name. - All data (JSON) can insert the whole trigger payload where that option is available.
If the picker says there are no variables yet, listen for trigger data or add the required steps before the selected node. Available fields depend on the captured payload, the node type, and the connections leading to the current node.
For the full test process, see Test a Workflow Before Activating It.