Browse documentation

Workflows

Workflow patterns and best practices

Apply supported message, logic, AI, integration, action, handoff, and terminal-node patterns.

Automation buildersBeginnerAvailable

What this guide covers

  • Patterns show how implemented nodes fit together without claiming unsupported data sources or schedule behavior.
  • Prerequisites: Review every node's prerequisites and the relevant connected service.
  • Result: The workflow has explicit paths, observable results, and no node that depends on data produced later.
  • Limit: Examples do not bypass WhatsApp service-window, template, connection, permission, or balance rules.

What this is and when to use it

Patterns show how implemented nodes fit together without claiming unsupported data sources or schedule behavior.

When to use Workflow patterns and best practices
Use it whenExpected outcome
You need a safe starting topology for a new workflow.The workflow has explicit paths, observable results, and no node that depends on data produced later.

Before you begin

  1. Review every node's prerequisites and the relevant connected service.

Complete the task

  1. Start with the smallest trigger-to-outcome path.
  2. Add validation and a clear End Flow for success and failure paths.
  3. Use Human Handoff when human judgment is required.
  4. Use Test with alternative inputs.
  5. Monitor early live executions and cost.

Confirm it worked

  1. The workflow has explicit paths, observable results, and no node that depends on data produced later.

Common problems

Workflow patterns and best practices troubleshooting
SymptomWhat to check
An example needs unavailable dataReplace the conceptual step with an implemented integration, webhook, function, or provided variable.
A delay is used as a calendarUse Scheduled trigger for calendar recurrence; Delay only waits inside an execution.

Current limitations

Examples do not bypass WhatsApp service-window, template, connection, permission, or balance rules.

Where to go next