Help Center

Workflow Branches, Email Open Branching & Exit Steps

Branch nodes let you create conditional paths inside a single workflow. Using branches, you can send contacts down different paths based on whether a condition is met, whether a filter passed, or whether an email was opened.

This makes it easier to handle multiple scenarios in one workflow instead of creating separate workflows for each case.

What Branch Nodes Do

A Branch node evaluates the result of the node directly before it and then routes the workflow down one of two paths. This gives you an if / then / else structure inside the workflow builder.

How Branch Nodes Work

1. Place a supported node before the branch.
2. Add a Branch node immediately after it.
3. Choose how the branch should behave.
4. Connect different actions to each path.

Important: A Branch node must always come directly after a supported node. It evaluates only the result of the node placed immediately before it.

Supported Nodes Before a Branch

Branches can follow:

• Contact Filters
• Appointment Filters
• Form Submission Filters
• Send Email nodes

The Branch node always evaluates the result of the node placed immediately before it.

Branching After Filters

When a Branch follows a filter node, the branch can route the workflow based on whether the filter condition passed or failed.

• Yes — go down the true path if the filter passed
• No — go down the true path if the filter failed

This is useful when you want different actions for contacts who match a condition versus those who do not.

Example: Virtual vs. In-Person Appointment Follow-Up

1. Add an Appointment Filter that checks whether the meeting location is Virtual.
2. Add a Branch node immediately after the filter.
3. On the Yes path, send a virtual meeting follow-up email with next steps or links.
4. On the No path, send an in-person meeting follow-up email.

This allows both follow-ups to live in a single workflow instead of maintaining separate workflows.

Branching After Send Email

When a Branch follows a Send Email node, you can branch based on whether the email was opened.

• Yes - Email was opened — go down the true path if the recipient opened the email
• No - Email was not opened — go down the true path if the email was not opened

This lets you create follow-up logic based on email engagement.

Example: Follow-Up Based on Email Opens

1. Add a Send Email node with your initial message.
2. Add a Wait node, such as waiting 3 days.
3. Add a Branch node set to Yes - Email was opened.
4. On the true path, send a follow-up email acknowledging engagement.
5. On the false path, send a reminder email with a different subject line.

Tip: Always add a delay before branching on email opens so recipients have enough time to open the email.

Why Click-Based Branching Is Not Supported

Branch nodes do not support email click-based branching. This is intentional.

Email click tracking can be unreliable because many email clients and security tools pre-scan or rewrite links automatically. That can create false clicks and make the workflow take the wrong path.

To keep workflow behavior more reliable, LeadCenter supports email-open branching but not click-based branching.

Instead of click-based branching, use more dependable signals such as:

• Email open tracking with a delay
• Landing page visits or form submissions
• Tag changes or other CRM-based engagement signals
• Explicit actions captured inside LeadCenter

Exit Steps

The Exit Step can do more than simply end the current workflow path. When a contact reaches an Exit Step, the workflow run ends and that contact is permanently prevented from entering that same workflow again in the future.

Important: This block applies across all versions of the same workflow. Publishing a new version does not remove the exclusion.

How Exit Steps Work

1. A contact enters a workflow through a supported trigger.
2. The contact progresses through the workflow.
3. When the contact reaches an Exit Step, that run ends immediately.
4. If the same workflow would normally trigger again later for that same contact, it will not start again.

No configuration is required for an Exit Step. It simply ends that path and permanently excludes the contact from future runs of the same workflow.

What Is Not Blocked by an Exit Step

• Filtered contacts — contacts that did not pass a filter are not excluded and can enter later if they match.
• Terminated or failed runs — manually stopped or failed runs do not create a permanent exclusion.
• Workflow paths without an Exit Step — if a workflow finishes naturally without an Exit Step, no permanent block is created.

When to Use an Exit Step

• Use an Exit Step if the workflow should run only once per contact.
• Let the workflow end naturally if you want the workflow to stay repeatable later.

Common Use Cases

• Onboarding workflows — make sure a contact goes through onboarding only once
• One-time follow-up workflows — prevent repeat sends of the same communication
• Branching workflows — end one branch permanently while another continues differently

Example: Exit Step in a Branching Workflow

Imagine a workflow triggered by Contact Updated when a tag changes.

• A contact enters the workflow after receiving a tag such as Seminar Attendee.
• The workflow sends the appropriate follow-up and then reaches an Exit Step.
• Later, that same contact gets another qualifying update.
• Because the contact already reached the Exit Step in that workflow, the workflow does not run again.

Best Practices

• Always place supported nodes before branches: a Branch only evaluates the node directly before it.
• Use clear filter logic: make sure filters are easy to understand and test.
• Name nodes clearly: descriptive filter and action names make larger workflows easier to maintain.
• Test both paths: verify that both the true and false paths behave as expected.
• Use Exit Steps intentionally: once reached, the contact is permanently excluded from that workflow.
• Use deterministic signals where possible: tags, filters, and explicit actions are more reliable than inferred engagement.

Frequently Asked Questions

Can a Branch node work without a filter or send email node before it?

No. A Branch must come directly after a supported node and evaluates only that node’s result.

Can I branch based on whether an email was clicked?

No. Click-based branching is not supported because click tracking can be unreliable.

Does an Exit Step stop only the current run or future runs too?

It does both. It ends the current run and permanently blocks future runs of the same workflow for that contact.

Can filtered contacts still enter later?

Yes. If a contact was filtered out and never reached an Exit Step, they can still enter later if they match the workflow conditions.

Can I automatically re-enroll a contact after they reach an Exit Step?

No. Reaching an Exit Step permanently excludes that contact from the same workflow.

What happens if I publish a new version of the workflow?

The Exit Step exclusion still applies. Publishing a new version does not remove the block for contacts who already reached that Exit Step.

Need Assistance?

If you have questions or need help building workflows with branches or Exit Steps, contact support@leadcenter.ai.