Skip to content

Workflow Conditions

Add if/else branches to your workflows to execute different actions based on record data or engagement status.

Condition branch

How Conditions Work

A condition step evaluates a rule and splits the workflow into two paths:

  • Yes path -- Actions to execute when the condition is true
  • No path -- Actions to execute when the condition is false

Each path can have its own set of actions, delays, and even nested conditions.

Setting Up a Condition

  1. In the workflow builder, click Add Action and select If/else branch
  2. Define the condition to evaluate
  3. Add actions to the Yes path
  4. Add actions to the No path (or leave empty to do nothing)

Condition Types

You can evaluate conditions based on:

Record Properties

Check the current value of any field on the triggering record:

  • "Deal stage is still Proposal Sent"
  • "Contact lifecycle stage is Customer"
  • "Ticket priority is Urgent"

Engagement Data

Check email engagement from previous workflow actions:

  • "Contact opened previous email"
  • "Contact clicked a link in the last email"

Time-Based

Check relative dates:

  • "Deal close date is within 7 days"
  • "Last activity was more than 14 days ago"

Example

A common pattern is to check if a deal has progressed after a delay:

  1. Trigger -- Deal moves to Proposal Sent
  2. Action -- Create task for the owner
  3. Delay -- Wait 3 days
  4. Condition -- Is the deal still at Proposal Sent?
    • Yes -- Send notification to owner, post to Slack
    • No -- Do nothing (the deal progressed on its own)
You
Add a condition to the workflow: if the deal hasn't moved in 3 days, notify the manager
Outsprint AI
Added an if/else branch after the 3-day delay. If the deal stage hasn't changed, the manager will be notified.

Pro Tip

Use conditions after delays to avoid unnecessary actions. Checking the record state before acting prevents notifications about deals that have already progressed.

What's Next