How do Join Paths work in Remote automations?

Join Paths let you bring multiple parallel workflow branches back together into a single step in your automation. This article explains what Join Paths are, how to set them up, and when to use them.

What is a Join Path?

A Join Path is a synchronization point in an automation that waits for all incoming parallel branches to finish before the workflow continues.

You can split a workflow into several parallel paths that run at the same time. A Join Path reconnects those branches. It collects the results from every branch and only moves forward once all of them are complete.

This means you can build end-to-end processes where a final step depends on all parallel work being done first.

When should I use a Join Path?

Use a Join Path when your automation has two or more parallel branches that must all finish before a downstream action runs.

For example, during onboarding, you might need HR, IT, and Finance to each complete separate tasks before the new hire receives a single confirmation message. Without a Join Path, there is no way to wait for all three branches to finish before sending that message.

How do I set up a Join Path?

1. Go to Workflows > Automations and create a new automation or edit an existing one.
2. Set up a trigger (for example, "New hire joins").
3. Create parallel branches.
4. Configure the actions within each branch as needed.
5. Drag the line from the end of each branch into the final node on the canvas (for example, "Send confirmation email").
6. The system creates a Join that waits for every connected branch to complete.
7. Add any actions you need after the Join node.
8. Save and publish the automation.

Example: Onboarding completion notification

1. Trigger: A new team member, Alex, joins the company.
   • Branch 1: HR sends a welcome email to Alex.
   • Branch 2: IT requests the confirmation document from Alex.
   • Branch 3: HR sends an onboarding survey to Alex.
2. Join — the workflow waits for all three branches to finish.
3. Remote sends a "You're all set!" email to Alex.

What happens if one branch fails?

The Join does not proceed until every incoming branch has completed. If one branch fails, the other completed branches wait at the Join point. Once you retry the failed branch and it completes successfully, the Join triggers and the workflow continues downstream.

Can I use more than one Join Path in an automation?

Yes. You can place Join nodes at different points in the same automation to synchronize different sets of branches. Each Join operates independently and waits for its own incoming branches to finish.

Can I add steps after the Join node?

Yes. The Join node is a synchronization point, not an endpoint. You can add any actions, conditions, delays, or even further branching after a Join.

How does a Join Path relate to Multi-Flow Branching?

Multi-Flow Branching splits a workflow into parallel paths. Join Paths bring those paths back together. They are complementary features:

• Multi-Flow Branching = split into parallel branches.
• Join Paths = wait for all branches to finish, then continue as one.

You cannot use a Join Path without first creating parallel branches using Multi-Flow Branching.