How to create multi-flow branching automations

This article explains how to create and manage multi-flow branching automations in Remote. Multi-flow branching lets you run multiple independent workflows from a single trigger event.

What is multi-flow branching?

Multi-flow branching allows you to set up multiple parallel branches within a single automation. When a trigger event fires, all branches start and run at the same time. Each branch operates independently, so if one branch fails, the others continue without interruption.

Before multi-flow branching, automations ran in a strict sequence where every step followed the one before it. This made it difficult to model real-world processes that require several things to happen at once.

How to create a multi-flow branching automation

[Alt text: Screenshot showing the automation canvas with multiple branches from a trigger node]

1. Go to Workflows > Automations.
2. Select Create automation or open an existing one.
3. Choose a trigger event (for example, "First day of employment").
4. From the trigger event, select the + button to add a new branch. This creates a parallel flow.
5. Repeat step four to add more branches.
6. Configure each branch with its own sequence of actions and conditions.
7. Select Save and then Publish to activate the automation.

Example: New hire onboarding

A single trigger ("First day of employment") can kick off three branches simultaneously:

1. Branch 1: Send a welcome email
2. Branch 2: Send an onboarding survey
3. Branch 3: Create an IT provisioning task

All three branches begin at the same time, and each runs to completion on its own.

Permissions

• Only Company Admins (Owners) can create and manage automations.

Frequently asked questions

Can branches converge back into a single step?

Not in the current release. Each branch runs independently until it finishes. Branch convergence is a separate future project.

What happens if one branch fails?

The other branches continue running. Each branch is independent, so a failure in one does not affect the rest.

What about my existing automations?

Existing automations continue to work as before. The new canvas is backward-compatible, and legacy workflows are translated to the updated model at runtime.