How do I use branching paths in automations?

Branching paths let you add conditional logic to your automations so different actions run based on specific criteria.

This article explains how to add and configure branching paths (IF/ELSE) in Remote automations. With branching paths, you can evaluate a condition and route your workflow down one of two paths, reducing the need for duplicate automations and making complex workflows easier to manage.

Who can use branching paths?

Branching paths are available to all Remote customers with access to the Automations feature. The following users can create and manage automations that include branching paths:

1. Company Owners

What problem does branching paths solve?

Without conditional logic, automations run the same steps for every scenario. If you need different actions for different situations, such as sending country-specific documents during onboarding, you would have to create separate automations for each case. This leads to a large number of near-identical workflows that are difficult to maintain and scale.

Branching paths solve this by letting you set a condition within a single automation. The workflow splits into two paths:

• IF true path runs when the condition is met.
• IF false path runs when the condition is not met.

Only one path runs per automation execution.

How do I add a branching path to an automation?

Follow these steps to add conditional logic to an existing or new automation.

1. Navigate to Automations

   Log into Remote and go to Workflows on the sidebar. Select Automations.

2. Create an automation

   Open an existing automation on the canvas, or select Create automation manually to start a new one.

3. Add a trigger event

   If you are building a new automation, click the trigger node on the canvas and select a trigger event in the sidebar (for example, "First day of employment").

4. Add the Branching paths node

   Click the + button on the canvas where you want the conditional split. Select Branching paths from the available node options. A new node appears with two outgoing paths: IF true and IF false.

5. Configure the condition

   Click the Branching paths node to open the sidebar. Set the condition you want to evaluate. Conditions are based on available employee and employment data fields, such as:

   • Country
   • Employment type
   • Department
   • Job title

   The available fields depend on the trigger context of your automation.

6. Add actions to each path

   Click the + button on the IF true path and add the action nodes that should run when the condition is met. Then do the same for the IF false path.

   For example:

   • IF Country = 🇩🇪 Germany: Send the DE-specific compliance document.
   • IF false: Send the global welcome pack.

7. Review and publish

   Review the full automation on the canvas to confirm the logic is correct. When ready, click Publish.

Can I nest branching paths inside each other?

Yes. You can place a Branching paths node inside either the IF true or IF false path of another Branching paths node. This lets you model more complex conditional logic within a single automation.

For example, you could first check the country, then within the "Germany" path, check the specific job title to determine which onboarding documents to send.

Can I have more than two branches?

Each Branching paths node supports one condition with two outcomes (true or false). To handle additional scenarios, nest Branching paths nodes within each other.

Multi-condition branching (IF / ELSE IF / ELSE) is planned as a separate future release.

Can I combine branching paths with other automation features?

Branching paths work with other automation capabilities:

• Multi-Flow Branching: You can add Branching paths inside a Multi-Flow branch. Multi-Flow runs all branches at the same time (this and that), while Branching paths runs only one path based on a condition (this or that). They solve different problems and complement each other.
• Delay Steps: You can add Delay Steps before, after, or inside either path of a Branching paths node for time-sensitive workflows.