Smarter Workflow Conditions: Engagement, Segments, and Tags

New Feature

Until now, workflow conditions could only check basic contact fields like name, email, or source. That meant you had no way to branch a workflow based on what a contact actually did — or where they belonged.

Today we're shipping a major upgrade to workflow conditions. You can now gate workflow steps on email engagement, segment membership, and tags.

What's new

Email engagement conditions

Add a condition step that checks whether a contact opened or clicked a specific email earlier in the workflow. Each check is its own condition type, so you can combine them to build precise logic.

Example: Send a follow-up email, wait 2 days, then add a condition that checks "has opened" the first email. Contacts who opened continue to the next step. Contacts who didn't are exited from the workflow — or you can add a second condition to check "has not clicked" and route accordingly.

Available checks:

• Email Opened — has opened / has not opened
• Email Clicked — has clicked / has not clicked

Each condition references a specific Send Email step in your workflow, so there's no ambiguity about which email you're measuring.

Segment conditions

Check whether a contact belongs to a segment at the moment the condition runs. Segments are evaluated in real time — not cached — so the result reflects the contact's current state.

• is in — contact matches the segment's rules right now
• is not in — contact does not match

This is useful for branching based on dynamic criteria like lead score thresholds, lifecycle stage, or any combination of rules you've built into a segment.

Tag conditions

Check whether a contact has (or doesn't have) a specific tag. Tags are often applied by automations, form submissions, or manual actions — so this lets you react to signals from other parts of your workflow.

• has tag — contact currently has the tag
• does not have tag — contact does not have the tag

Example: Tag contacts as "demo-requested" when they submit a form, then use a tag condition in your nurture workflow to skip the sales pitch email for contacts who already have that tag.

How it works in the builder

When you add or edit a Condition step, the condition type dropdown now has three groups:

For engagement conditions, you pick which earlier Send Email step to check. For segment and tag conditions, a dropdown loads your active segments or tags so you can select the one you want.

Combining conditions

Because each condition type is a separate step, you can chain them to express complex logic. For example:

1. Send Email — "Welcome to the trial"
2. Delay — 3 days
3. Condition — Email Opened: has opened Step 1
4. Condition — Tag: does not have tag "converted"
5. Send Email — "Here's what you're missing"

This targets contacts who showed interest (opened) but haven't converted yet — exactly the audience that benefits from a nudge.

Available on all plans

These condition types are available to everyone. No plan upgrade required.