Automation Setup – Certification Cloud

Learn how to automate events within VAIRKKO using Automation Rules.

What is Automation?

VAIRKKO’s Automation feature allows you to create rules that trigger actions automatically when certain conditions are met.

Simply put:
When X happens, and conditions Y are met → action Z occurs.

How Automation Works

Every automation rule is made up of three parts:

• Trigger (X): What happens in VAIRKKO
• Condition (Y): Filters that must be met
• Action (Z): What happens as a result

Examples of Automation Rules

How to Set Up an Automation Rule

Step 1: Access Automation

Go to System Configuration → Automation

[Insert Screenshot – Automation menu]

Step 2: Create or Manage Rules

• View existing rules
• Click “New Rule” (top right) to create one

[Insert Screenshot – New Rule button]

Configure Your Rule

Step 3: Define the Trigger

Choose what event will start the automation:

• Certification Expiration
• Certification Issuance
• Compliance Rule Collection Progress
• Roadmap Completion

Only one trigger can be selected per rule.

Step 4: Add Conditions (Optional)

Conditions act as filters to refine when the rule runs.

Examples include:

• Specific certification
• Employee group, department, or location
• Roadmap membership
• Completion percentages

You can add multiple conditions.

[Insert Screenshot – Conditions section]

Step 5: Define Actions

Actions determine what happens when the trigger and conditions are met.

Common actions include:

• Add or remove employee from group
• Assign training (LMS, roadmap, skills test, etc.)
• Issue or expire certifications
• Send notifications (email, text message, or VAIRKKO inbox message)

You can add multiple actions.

[Insert Screenshot – Actions section]

Step 6: Name and Save

• Enter a clear name for your rule
• Click Save

Step 7: Activate the Rule

Toggle the rule ON when you are ready to use it.

[Insert Screenshot – Toggle ON]

Helpful Tips

• Start with simple rules, then add conditions as needed
• Use clear naming conventions (e.g., “Cert Expiration – Assign Refresher”)
• Test rules before relying on them in production