Build a multi-step workflow
Learn how to add multiple action steps to a single workflow so one trigger can update several apps at once.
What multi-step workflows do
Every workflow starts with one trigger. At minimum, that trigger connects to one action, but you can add as many action steps as you need. Each time the trigger fires, all action steps run in sequence, one after the other.
A few examples of what this makes possible:
- A new employee added in EmCentrix → create a record in QuickBooks Desktop and send a Slack notification and add a row to a Google Sheet
- A form submission → create a task in Asana and add a contact to Salesforce
Each action step is configured independently. Different apps, different field mappings, different events. The only thing they share is the trigger that starts them.
Before you begin
Before you start, make sure you have:
- A workflow open in the builder with the trigger fully configured and tested
- At least one action step already configured and tested
- Login credentials for any additional apps you plan to connect
Adding a second action step
1. Open your workflow in the builder
From the Home page, click the workflow name in the Your Workflows section to open it in the builder.
2. Click the + button below the last action node
On the canvas, click the + button below your last action node. A new unconfigured action node appears, showing "Select the task for your workflow to run."
Alternatively, click the + Add button in the top toolbar.
3. Configure the new action step
Click the new action node to open its configuration panel. Work through the tabs in order:
- Setup: select the app and event
- Account: connect or select the app account
- Mapping: map fields from the trigger to the destination
- Test: test the action to confirm it writes correctly
See Connect an app to your workflow and Map fields between your apps for detailed walkthroughs of each step.
4. Republish the workflow
Once the new action step is configured and tested, click the blue Publish button in the top toolbar. The updated workflow is now live with all action steps active.
How tasks are counted in multi-step workflows
Each action step that runs successfully counts as one task against your monthly allowance. A workflow with three action steps that runs 50 times in a month consumes 150 tasks.
If a step fails, it doesn't consume a task. Only successful action executions count.
See Understanding your plan and task limits for more detail.
What happens when one step fails
Action steps run in sequence. If an earlier step fails, later steps in the same run do not execute.
For example, if your workflow has three action steps and step 2 fails, step 3 will not run for that trigger event. Steps that ran before the failure (step 1 in this example) are not rolled back. Any data already written to those apps stays written.
To see exactly which step failed and why, open Workflows → Activities, find the failed run, and click the magnifying glass icon to view the execution log. See How to read workflow error messages for a full walkthrough.
Auto Retry
By default, if a run fails Conduitly pauses the workflow automatically. If you want failed workflows to retry instead of pausing, enable Auto Retry in the workflow settings. Click the settings icon in the top toolbar and toggle Enable Auto Retry to on.
Removing an action step
To remove a step you no longer need, click the × button on that action node on the canvas. The step is removed immediately. Republish the workflow to apply the change.
Note: Removing a step removes its configuration permanently. If you think you may need it again, consider deactivating the workflow instead of deleting the step.