How to Build a Conditional Automation

A condition checks information about an enrolled contact and sends them down a Yes or No path. Conditional automation requires Kelune CRM Pro. Use conditions when the next step should depend on profile, membership, or engagement data.

Plan the decision

Write the condition as a question with a clear yes-or-no answer. For example:

• Does the contact have the Customer tag?
• Is the contact in the Newsletter list?
• Did the contact open the welcome email?

Decide what should happen on both paths before editing the automation.

Add and configure the condition

1. Open the automation in the canvas builder.
2. Add a Condition after the trigger, action, or delay where the decision belongs.
3. Choose the condition type.
4. Complete the required field, list, tag, segment, or email settings.
5. Save the condition.
6. Add the appropriate next steps to its Yes and No outputs.

Available condition types include:

• Field Value, with the available comparison operator and value.
• In List or Not In List.
• Has Tag or Does Not Have Tag.
• Email Opened or Email Clicked.
• In Segment or Not In Segment.

Build both branches

For a welcome-email follow-up, the workflow might be:

1. Send the welcome email.
2. Wait three days so contacts have time to engage.
3. Check Email Clicked.
4. On Yes, add an Interested tag and send the next offer.
5. On No, send a lighter reminder or end the journey.

Place an engagement condition after a reasonable delay. Checking immediately after the send would place most contacts on the No path before they have time to open or click.

Test the paths

Use separate test contacts whose data should produce different results. Confirm that:

• One test contact reaches the Yes path.
• Another reaches the No path.
• Each branch runs only its own actions.
• Delays, emails, list changes, and tags are correct.
• Neither path reconnects to a step that creates an unintended loop.

Save and activate the automation only after both paths behave as intended. Monitor the first live enrollments and pause the automation if contacts take an unexpected branch.