Create powerful conditional workflow paths using Branch nodes. You can now branch your workflows based on filter conditions or whether an email was opened by the recipient.
Branch nodes enable "if/then/else" style logic in your automations. They evaluate the result of the previous node and route the workflow down different paths.
When a branch follows a Filter node (e.g., Lead Filter, Appointment Filter), you can branch based on whether the filter condition passed or failed:
When a branch follows a Send Email node, you can branch based on whether the recipient opened the email:
This allows you to create follow-up sequences that respond to recipient engagement.
You may notice that Branch nodes do not support conditions based on email link clicks. This is intentional.
Email click tracking is fundamentally unreliable due to technical limitations across modern email clients, especially on mobile devices. Many popular clients—including Apple Mail, Gmail, and Outlook—use link prefetching, security scanning, and proxy services that can trigger false clicks without any real user interaction.
Additionally, privacy-focused features and corporate security tools often rewrite or pre-scan links, making it impossible to accurately determine whether a human actually clicked a link or whether the click was generated automatically by the email client or a security system.
Because of these limitations, branching workflows based on email clicks can lead to incorrect automation paths, poor user experience, and unintended actions. To ensure workflow reliability and predictable outcomes, click-based branching is not supported.
Instead, we recommend using:
Sources:
Use Exit Step nodes to terminate workflow execution on branch paths that should not continue further. Exit Step nodes require no configuration and simply mark the workflow as completed when reached.
If you can’t find the answers you’re looking for, our support specialists are available to answer your questions and troubleshoot if necessary.