Workflow Steps
- What steps are and how they form the body of a workflow
- How to add, configure, and manage steps using the Etapas section
- How to debug steps individually or all at once
- How step execution order works
Steps (Etapas) are the actions your workflow performs after the trigger fires. Each step represents a single operation -- such as sending a message, updating a record, or calling an external service. Steps execute in sequence from top to bottom, meaning each step completes before the next one begins.
Adding steps
To add a step to your workflow:
- Open the workflow creation or editing form.
- Scroll down to the Etapas (Steps) section.
- Click the Adicionar passo (Add step) button.
- A new step will be added to the list. Configure it by selecting the step type and filling in its parameters.
- Repeat to add as many steps as your workflow requires.
Each step you add appears in the list in the order it will execute. You can add multiple steps to build complex automations that perform several actions in sequence.
Configuring a step
When you add a step, you will need to configure it based on what action you want it to perform. Each step type has its own set of fields and options. For example:
- A "send message" step may require you to specify the message text and the recipient
- An "update record" step may require you to select which field to change and what value to set
- A "call webhook" step may require you to provide an external URL and the data payload
You can use {{variable}} placeholder syntax within step fields to insert dynamic data from the trigger or from previous steps. For example, typing {{client.name}} in a message field will be replaced with the actual client name when the workflow runs. See Workflow inputs for more on variable placeholders.
Debugging steps
The Etapas section provides built-in debugging tools to help you test your workflow before activating it:
- Depurar tudo (Debug all) -- Click this button to run all steps in debug mode. This lets you see exactly what each step will do with sample data, without actually executing the workflow in production. It is the fastest way to verify that your entire workflow behaves as expected.
- You can also debug individual steps one at a time to isolate issues in a specific part of the workflow.
Debugging is especially useful when your workflow includes multiple steps that depend on each other, since you can inspect the output of each step and confirm that data is flowing correctly.
Clearing all steps
If you want to start over with a clean slate, click the Limpar todos os itens (Clear all items) button. This removes all steps from the workflow at once. Use this with caution, as it cannot be undone.
Step execution order
Steps execute from top to bottom in the exact order they appear in the Etapas section. Key points to keep in mind:
- Sequential execution: Each step must complete before the next step begins.
- Data flow: The output or result of one step can be referenced by subsequent steps using
{{variable}}placeholders. - Failure handling: If a step fails during execution, the workflow may stop at that point. Check the execution logs to identify which step failed and why.
Build your workflow incrementally. Add one step at a time, use Depurar tudo to test after each addition, and confirm everything works before adding the next step. This approach makes it much easier to identify and fix problems.