Introduction

When creating new automations, we are faced by many, many different types of event types, many, many different potential conditions, and again, many, many different actions to choose from.

In this help article, we will look at all the conditions of automations

What are conditions?

Conditions define who or what an automation applies to. While the event tells the platform when to check, conditions decide if the action should actually run.

Think of conditions as the rules that must be true before the platform moves forward.

For example:

Event: A learner completes Module 1
Condition: The learner is in the Belgium group
Action: Unlock Module 2

In this case, the automation only runs for Belgium learners, even though the event (completing Module 1) could happen for everyone.

💡 Tip:

You can add one or more conditions. If you use more than one, you can decide whether all conditions must be true (And), if any one condition is enough (Or) or you can create condition groups (combining both AND and OR conditions)

Remember:

AND: automation will be applied if all selected conditions are met.
OR: automation will be applied if one of the conditions are met.

Condition overview

Condition	Sub-condition	Description	Example use case
Is activity	Completed / Incompleted / Failed / All	Targets users based on completion state of a specific activity	Unlock Module 2 only when Module 1 is completed
Is journey/ section	Completed / Incompleted / All	Targets users based on completion state of a journey or section	Unlock the “Advanced” journey when “Basics” section is completed
Is programme	Completed / Incompleted / All	Targets users based on programme completion state	Assign a certificate when a user completes a full programme
Is goal	Completed / Committed / Uncommitted	Targets users based on goal completion or commitment	Notify users who committed to a goal but have not yet completed it
Is user	N/A	Targets a specific user	Test automation by unlocking content only for your own account
Is group	Negate option available	Targets users in a specific group (or everyone not in the group if negated)	Unlock onboarding content for the Belgium group only
General time condition	Start and end timespan	Runs automation only within a fixed time frame	Unlock Module 1 for all learners between Sept 1 and Sept 30
User-specific time condition	Contract start date, Contract end date, First login, Last login, Creation date	Compares current time with a user-specific field	Unlock onboarding Module 1 for 7 days after the contract start date
User progression	Percentage of activities / Number of activities	Targets users based on their progress across activities	Unlock the next block when user has completed 80% of their activities
All activities completed	N/A	Targets only users who completed all assigned activities	Move learner into “Graduated” group after finishing all modules
Unconditional	N/A	Applies to all users regardless of other conditions	Send a global notification to everyone on the platform
Is activity in event	N/A	Applies only if the activity being completed is the selected one	Grant a badge when “Safety Training” is completed
Is activity in journey/ section	N/A	Applies only if the activity being completed is inside the selected journey/section	Unlock next section of the onboarding journey when a “Basics” activity is completed
Activity graded	Minimum grade threshold	Applies only if the grade of an activity is above or below a threshold	Notify a learner if they fail an activity with grade below 60%
Is group in event	N/A	Applies only if the user is added/removed to a specific group in the event	Trigger automation when a user is added to the “Managers” group
Add condition group	And / Or	Groups multiple conditions together using logic operators	(User is in Group A OR Group B) AND (Has completed Activity X)

Tip!

When adding a lot of similar conditions, you can also duplicate a condition. The editor will automatically open for quick adjustments.

All about conditions (automations)