Variables, approvals, and runs

Variables & data passing

Each step can read outputs from earlier steps. Use the variable picker in step settings to insert fields (email subject, form answers, agent draft, and so on).

Project / environment variables can store shared values (API bases, channel IDs) so you do not hard-code secrets in every step — use connections for credentials.

Approvals

Approvals keep humans in control:

1. Add an approval step where judgment is required.
2. When the flow reaches it, an assignee reviews.
3. On approve, the flow continues; on reject, follow your configured path.

Use approvals before irreversible actions (payments, deletes, external emails).

Runs

• Open run history for a flow to see success, failure, and step I/O.
• Re-run or fix configuration when a step fails.
• Watch concurrency and monthly run limits on your plan.

Debugging tips

• Check trigger payload shape first.
• Validate connection auth.
• Confirm AI/agent steps have a configured provider when required.
• Narrow the flow: disable later steps until earlier ones succeed.