Meta tags:
description=Branching allows you to send different emails based on a contact s properties within a single workflow.;

Headings (most frequently used words):

branching, audience, filters, branches, workflows, documentation, index, on, this, page, creating, workflow, node, types, experiments, converging, deleting, learn, api, cli, guides, upgrade, notice,

Text of the page (most frequently used words):
the (45), #branch (22), node (20), #workflows (16), you (16), branches (15), audience (12), filter (12), contact (11), will (11), workflow (11), filters (10), branching (10), nodes (9), all (8), different (8), can (7), for (7), contacts (7), and (6), this (6), want (6), emails (6), are (5), page (5), each (5), target (5), email (5), they (5), send (5), experiments (4), click (4), converging (4), only (4), that (4), more (4), your (4), upgrade (4), api (4), loops (4), may (3), next (3), single (3), deleting (3), removed (3), when (3), select (3), with (3), multiple (3), same (3), any (3), reroute (3), use (3), have (3), create (3), follow (3), matching (3), down (3), documentation (3), first (3), add (3), based (3), properties (3), creating (3), contain (2), pausing (2), delete (2), head (2), icon (2), following (2), end (2), not (2), paths (2), now (2), below (2), connection (2), common (2), case (2), converge (2), path (2), example (2), before (2), about (2), apply (2), stops (2), later (2), created (2), two (2), settings (2), old (2), behavior (2), has (2), added (2), notice (2), right (2), matches (2), defined (2), which (2), learn (2), types (2), users (2), copy (2), integrations (2), started (2), guides (2), transactional (2), events (2), search (2), index (2), support, responses, generated, using, mistakes, assistant, linkedin, previous, yes, was, helpful, last, modified, june, 2026, final, deleted, trash, remove, including, result, since, allow, circular, valid, visible, invalid, dimmed, located, here, how, set, back, lead, onboarding, but, timer, waits, week, sending, read, reach, remain, downstream, from, after, toggled, between, marked, retain, logic, until, explicitly, press, button, shown, options, panel, information, see, been, changed, new, match, previously, would, who, matched, parallel, equivalent, default, making, most, empty, conditions, reaches, evaluated, left, builder, proceed, remaining, skipped, none, exit, every, always, determine, testing, timers, many, like, clicking, option, appears, hover, just, automatically, edit, their, where, type, adding, free, versus, paid, crafting, user, journey, whether, completed, action, allows, within, basics, recipes, deliverability, getting, uploads, themes, lists, messages, components, completion, campaigns, auth, overview, cli, changelog, webhooks, sdks, examples, reference, introduction, security, agent, skills, account, smtp, goals, triggering, guide, editing, get, navigation, log, home, skip, main, content, file, discover, available, pages, exploring, further, fetch, complete, docs, llms, txt,

Text of the page (random words):
branching workflows loops documentation index fetch the complete documentation index at docs llms txt use this file to discover all available pages before exploring further skip to main content loops home page contact us log in loops search navigation workflows branching workflows search k learn get started editing emails workflows guide triggering workflows pausing workflows branching workflows experiments events goals contacts transactional email integrations smtp account agent skills for loops security api api introduction api reference examples sdks webhooks api changelog cli overview auth campaigns completion components contact properties contacts email messages events lists themes transactional uploads workflows guides all guides getting started workflows deliverability integrations creating emails recipes email basics on this page creating a branching workflow audience filters upgrade notice converging branches deleting branches workflows branching workflows copy page branching allows you to send different emails based on a contact s properties within a single workflow copy page a common use case for crafting a user journey is to send different emails based on whether a contact has completed an action or not for example you may want to send a different email to free users versus paid users you can do this by adding a branch node to your workflow creating a branching workflow to create a branching workflow click the icon where you want branching to be added and select the branch node type two audience filter nodes are automatically created for you edit the audience filter settings for each to send different contacts down each branch based on their properties you can add as many branches as you like to your workflow add more branches by clicking the branch option that appears on hover just below the branch node each branch can contain emails timers audience filters more branches and experiments node types learn about the different node types experiments add a b testing to your workflows audience filters every branch is defined by an audience filter which is always the first node in a branch filters determine which contacts follow each branch when a contact reaches a branch node the audience filter nodes are evaluated left to right as defined in the workflow builder the contact will proceed to the first matching filter and the remaining filters are skipped if the contact matches none of the filters they exit the workflow you can create the equivalent of a default path by making the right most filter have empty conditions so that it matches any contact upgrade notice previously a branch node would send contacts who matched multiple filters down multiple parallel branches this behavior has been changed now in any new branches added to workflows contacts will only follow the first branch they match branches with the old behavior are marked in your workflows they will retain the old logic until you explicitly press the upgrade branch node button shown in the branch head node s options panel for more information see the branch node upgrade documentation the audience filter nodes created after a branching node can be toggled between two settings all following nodes the audience filter will apply to all nodes downstream of the filter if a contact stops matching the filter later down the branch they will be removed from the workflow next node only the audience filter will only apply when contacts reach the next node in the branch if a contact stops matching the filter later in the branch they will remain in the workflow audience filters read more about audience filters converging branches a common use case is to have different branches converge back to the same path for example you may want to create branches with different filters that lead to different onboarding emails but have all branches converge on a single timer that waits a week before sending the same follow up email here s how you can set up converging paths in a workflow 1 reroute a connection click reroute connection located below a node 2 click on a target node now select the target node you want to reroute to since workflows do not allow circular paths only valid target nodes will be visible and any invalid target nodes will be dimmed 3 end result you ll end up with multiple nodes converging on the same target deleting branches to delete all branches select the head branch node and click the trash icon this will remove all branches including all nodes following it if you want to delete a single branch you can do so by deleting each node in the branch you want removed when the final node is deleted the branch will be removed last modified on june 12 2026 was this page helpful yes no pausing workflows previous experiments next i x linkedin assistant responses are generated using ai and may contain mistakes contact support