Help Center

Workflow Branches

Workflow Branches let you create conditional logic inside a single workflow. Using branches, you can send contacts down different paths based on whether a condition is met or not — similar to an “if / then / else” decision.

This allows you to handle multiple scenarios in one workflow instead of creating separate workflows for each case.

How Workflow Branches Work

A Branch node evaluates the result of the filter directly before it and then continues the workflow on one of two paths.

1. Add a Filter (such as a Contact Filter or Appointment Filter).
2. Add a Branch node immediately after the filter.
3. Choose how the branch should behave based on the filter result.
4. Connect actions to each branch path.

Important: A Branch node must always come directly after a filter. Branches only evaluate the result of the filter immediately before them.

Supported Filters

Branches work with supported filter nodes, including:

• Contact Filters
• Appointment Filters
• Form Submission Filters

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

Example: Virtual vs In-Person Appointment Follow-Up

Use a workflow branch to send different follow-ups based on how the appointment took place.

1. Add an Appointment Filter that checks whether the meeting location is Virtual.
2. Add a Branch node immediately after the filter.
3. Yes path: Send a virtual meeting follow-up email with next steps, links, or a recording.
4. 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 automations.

Exit Step

The Exit Step allows you to stop a workflow early.

• The workflow ends immediately when it reaches an Exit Step.
• No configuration is required.
• Useful when one branch should stop while another continues.

Exit Steps are commonly used at the end of one branch path when no further actions should run for that scenario.

Best Practices

• Always place filters before branches: Branches only evaluate the filter directly before them.
• Use clear filter logic: Make sure your filter conditions are easy to understand and test.
• Name nodes clearly: Descriptive filter and action names make complex workflows easier to maintain.
• Test both paths: Verify that both the Yes and No paths behave as expected.
• Use Exit Steps intentionally: End workflows cleanly when a path should not continue.

Why Use Workflow Branches

• Create smarter, more personalized automation.
• Reduce the need for duplicate workflows.
• Handle different scenarios cleanly in one flow.
• Keep automation logic easier to understand and maintain.

Need Assistance?

If you have questions or need help building workflows with branches, contact LeadCenter Support at support@leadcenter.ai.