Types of Conditions
ParsaLink automations support four types of conditions, each serving a different purpose:
| Type | Purpose |
|---|
| Trigger Conditions | Filter which records enroll in the automation at all |
| Step Conditions | Skip individual actions based on the record’s current state |
| Exit Conditions | Cancel all remaining actions and unenroll the record |
| Else Actions | Run an alternative action when a step condition fails |
Trigger Conditions
Trigger conditions are filters applied at the moment the trigger fires. If the conditions are not met, the record is not enrolled and no actions run.
Example: Trigger = Lead Created, with trigger condition Source = Website Form
This automation will only run for leads that came from the website. Leads created manually or imported via CSV will not enroll.
Adding trigger conditions:
- In the automation builder, click Add Condition below the trigger.
- Choose the field to evaluate.
- Select an operator and value.
- Add multiple conditions with AND/OR logic.
Step Conditions
Step conditions are evaluated at the moment a specific action is about to run (after any wait steps before it). If the condition fails, that step is skipped — but the automation continues to the next step.
Example: In a lead nurture sequence, you want to skip the Day 5 follow-up email if the lead has already been converted.
Add a step condition on the Day 5 email: Lead.status ≠ Converted
If the lead has been converted by Day 5, the email step is skipped, but any subsequent steps (like a manager notification) still run.
Adding step conditions:
- Click the action step in the automation builder.
- Click Add Condition on that step.
- Configure the condition. The action runs only if the condition passes.
Exit Conditions
Exit conditions are checked continuously (or at each step) during an enrolled record’s journey through an automation. If the condition is ever met, all remaining actions are cancelled and the record is unenrolled.
Example: Exit condition = Opportunity.stage = Closed Won
If any opportunity record enrolled in this automation reaches Closed Won, stop all remaining follow-up actions. The deal is done — no more emails needed.
Common exit conditions:
- Lead converted (stop nurture emails)
- Contact stage = Customer (stop prospect sequences)
- Email unsubscribed (always add this to email sequences)
- Case resolved (stop escalation actions)
Adding exit conditions:
- In the automation builder, click Exit Conditions in the configuration panel.
- Add one or more conditions. Meeting ANY condition triggers an exit (OR logic).
Else Actions
An else action is an alternative action that runs when a step condition fails. Instead of simply skipping the step, you can do something different.
Example:
- Step: Send proposal follow-up email
- Step Condition:
Proposal.status = Viewed
- Else Action: Send a different email with subject “Did you get a chance to look at the proposal?”
If the condition passes (proposal was viewed), send the standard follow-up. If not (proposal was not yet viewed), send the “did you get a chance to look” version instead.
Adding else actions:
- Add a step condition to an action step.
- Click Add Else Action to configure what happens when the condition is not met.
Supported Operators
The following operators are available when building conditions:
| Operator | Description | Example |
|---|
eq | Equals | Status = Qualified |
neq | Does not equal | Source ≠ Cold Outreach |
contains | Field contains substring | Email contains @gmail |
not_contains | Field does not contain substring | Company not_contains LLC |
is_set | Field has any value (not empty) | Phone is_set |
is_empty | Field has no value | AssignedTo is_empty |
gt | Greater than | OpportunityValue > 10000 |
lt | Less than | LeadScore < 5 |
Condition Best Practices
Always add an email unsubscribe exit condition to any automation that sends emails: Contact.emailOptOut = true or Lead.emailOptOut = true. This automatically stops email sequences for anyone who opts out.
Step conditions are evaluated using the record’s data at the time the step runs, not at enrollment. This means a 5-day wait step will check the record’s current state on day 5, not the state from when the automation started.
