tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

Merge Workflow Paths with Join: Run Shared Steps Once

FlowMattic Join step: Router routes to Slack and email converge on a Join, then a single FluentCRM step runs once.

When you merge workflow paths, the steps that every outcome shares only need to be built once. FlowMattic’s Join step does exactly that: after a Router or a Branch splits a run, the Join brings the routes back into one chain, and the steps after it run once, whichever route the run took.

Without it, every route ends on its own, so a CRM update or a log row that should follow every outcome has to be copied into each route. With a Join, you build that tail once. It is for anyone whose workflows branch and then need to finish the same way.

What is the Join step?

Join by FlowMattic is a built-in step with one action event, Join Paths: “Continue the workflow with common steps after a Router or Branch.” FlowMattic selects that action for you when you add the step. It arrived in FlowMattic 7.2.0 and works with Router routes, Branch Yes/No paths and nested structures.

A Join is a convergence point, not a calculation. It doesn’t evaluate anything: the run reaches it when the route that executed finishes. Its one setting, Merged Fields, solves the problem that comes with merging: later steps can’t know which route ran, so they need one place to read a value from. It sits with the other workflow logic modules in the builder.

How to merge workflow paths with a Join

  1. Build your Router or Branch and the steps in each route.
  2. Add a step at the end of one route (or path) and choose Join by FlowMattic. The builder connects the end of every route in that Router or Branch into the Join and centres it under them.
  3. Add the shared steps below the Join. They run once per run.
  4. Optionally, open the Join’s Configure tab and define Merged Fields (see below).
  5. Use the Test tab: it shows your merged fields with sample values, so the steps after the Join can be tested without a live run.
FlowMattic Join Paths step merging two workflow paths
A Join step bringing two paths back together, with its Configure tab open.

The builder checks placement as you add the step. If the Join can’t go where you dropped it, a “Join Paths cannot go here” message explains why:

  • It must be inside a Router route or a Branch path.
  • Each Router or Branch can have only one Join. Add further steps after the existing Join instead.
  • Two Joins can’t be joined together. If a route already ends in a nested Join, add a step after that Join first.
  • If a route ends in a nested Router or Branch without its own Join, seal that inner one with a Join first.

Merged Fields: one tag, whichever route ran

After a merge, a step can’t safely map a value from inside one route, because that route may not have run. Merged Fields fix this. You define a field once, map a value for each route, and every step after the Join reads a single tag, {joinN.key}, where N is the Join’s step number.

SettingWhat it does
FieldThe key later steps use, for example user_email.
One input per routeThe value to use when that route ran: a dynamic tag from that route’s steps or static text.
+ Add merged fieldAdds another field.
Review & addAppears when FlowMattic finds fields common to every route’s test data. You pick which to add; each value is taken from the route’s step closest to the Join. Generic keys such as status and message are left out.

At run time, each field takes its value from the route that executed. If more than one Router route matched, the first route with a value wins, and a route you left unmapped contributes nothing. After a Join, the dynamic tag picker lists the Join’s merged fields instead of the routes’ internal steps, so you can’t accidentally map a value from a route that didn’t run.

In Task History, the Join’s entry records “Paths joined — the workflow continues with the common steps.”, the executed_route (the route’s name, or Yes/No for a Branch), and, as its input, the per-route mapping of each merged field.

Use cases

Two alert styles, one CRM update

Priority orders alert the team in Slack, standard orders get an email, and every order is tagged in the CRM once.

WooCommerce new order → Router (Priority / Standard) → Slack / Send Email → Join → FluentCRM tag

Log every lead, whichever list it joined

Business emails go to HubSpot, personal ones to Mailchimp. A merged field contact_id maps each tool’s ID, so the log row has one column for both.

Form submission → Branch (email Ends with a free-mail domain) → Yes: Mailchimp / No: HubSpot Create Contact → Join (merged field contact_id) → Google Sheets row

One reply step for AI drafts in different tones

Support tickets from paying customers get a detailed AI draft, others a short one. A merged field reply_text feeds one review step.

Fluent Support Ticket Created → Branch (plan Exactly matches pro) → Yes: AI Agent (detailed) / No: AI Agent (short) → Join (merged field reply_text) → Send Email to the support lead for review

Receipts and dunning, one billing record

A SaaS billing webhook either confirms a payment or reports a failure. Both outcomes end in the same record in your own database.

Webhook (billing event) → Branch (type Exactly matches invoice.paid) → Yes: Send Email receipt / No: Send Email payment reminder → Join → WP Tables New Record

Per-plan data pulls, one client report

An agency pulls different metrics for clients on different plans, then sends every client the same report.

Schedule (monthly) → Router (Basic / Growth) → API request per plan → Join (merged field visits) → Generate PDF from Template → Send Email

Always finish the run, even when no route matched

Without a Join, a Router whose routes all fail their conditions ends the run. With a Join, the run still reaches the common steps, so a summary or audit step always happens.

Webhook (return request) → Router (Refund / Exchange) → Send Email to finance / Fluent Support ticket → Join → Slack summary to #orders

Tips and gotchas

  • Map merged fields for every route. Tags from routes that didn’t run are blank, and an unmapped route contributes nothing. When no route ran at all, a merged field has no value.
  • Deleting a Join takes everything below it. The shared steps after the Join go with it, so check before you delete.
  • Delete the Join before its Router or Branch. While a Join is attached, the builder blocks removing the Router or Branch it closes, with the message “Delete the Join first”.
  • Nested decisions join inside out. Seal the inner Router or Branch with its own Join, then join the outer one.
  • Test before mapping. Run each route’s test once so “Review & add” can suggest the fields common to every route.

Related features

  • Router: split one event into named routes, each with its own conditions.
  • Branch: a single yes or no decision with two paths.
  • Task History: see which route each run took and what the Join resolved.

FAQ

How do I merge workflow paths after a Router?

Add a Join by FlowMattic step at the end of any one route. The builder connects every route of that Router into it, and the steps you add below the Join run once per run.

Do the steps after a Join run once for each route?

No. They run once per run, whichever route or path executed. If a step should repeat per route, keep it inside the routes, above the Join.

How do steps after a Join use data from inside a route?

Through Merged Fields. Define a field on the Join, map a value per route, and read it later as {joinN.key}. The value comes from the route that ran.

Join is included in every FlowMattic plan, with unlimited workflows and runs on your own server. See the plans and pricing and start building workflows that branch and merge cleanly.

More from the blog