Who This Is For / When to Use
This article is for admins and builders who want to automate actions based on course progress, access changes, or membership activity. Use Course Triggers when workflows need to respond to learning activity, product access, or user logins.
What Are Course Triggers in Kyrios?
Course Triggers are workflow entry conditions that enroll a contact into a workflow when a specific course-related event occurs, such as a lesson starting, a product being completed, or access being granted or removed. Each trigger listens for one defined event and immediately adds the contact to the workflow when that event happens.
Available Course Trigger Options
Each Course Trigger represents a single, specific event that can start a workflow.
Category Started
Runs when a contact starts a specified course category.Category Completed
Runs when a contact completes a specified course category.Lesson Started
Runs when a contact starts a lesson.Lesson Completed
Runs when a contact completes a lesson.New Signup
Runs when a contact signs up for a membership.Offer Access Granted
Runs when a contact is granted access to a specific offer.Offer Access Removed
Runs when a contact’s access to an offer is removed.Product Access Granted
Runs when a contact is granted access to a product.Product Access Removed
Runs when a contact’s access to a product is removed.Product Started
Runs when a contact starts a product.Product Completed
Runs when a contact completes a product.User Login
Runs every time a contact logs into their membership.
How to Create a Workflow Using Course Triggers
Creating a workflow with Course Triggers follows the same setup pattern as other Kyrios workflows.
Step 1: Create a New Workflow
Navigate to Automation → Workflows, then click Create Workflow and choose Start from Scratch.
Step 2: Add a Course Trigger
Click Add New Trigger at the top of the workflow canvas. In the trigger selection panel, scroll to the Course-related triggers and select the desired trigger type.
Step 3: Configure Trigger Details and Filters
After selecting a trigger, configure its settings. Filters allow the workflow to run only for specific offers, products, categories, or lessons. Filters are optional but strongly recommended for precise automation.
Example: Selecting Offer Access Granted and filtering by a specific offer ensures the workflow runs only when that offer is granted, not for all offers.
Step 4: Add Workflow Actions
After saving the trigger, add the actions the workflow should perform, such as sending messages, applying tags, or updating CRM fields. Multiple triggers can connect to the same action path.
Step 5: Save, Test, and Publish
Use Test Workflow to validate behavior. When ready, switch the workflow from Draft to Published and click Save.
Using Multiple Course Triggers in One Workflow
A single workflow can include multiple Course Triggers that all lead into the same sequence of actions. This is useful when different access events should trigger identical automation.
Example use case:
Offer Access Granted
Product Access Granted
Both triggers can enroll contacts into the same onboarding or notification workflow.
Using Filters with Course Triggers
Filters refine when a trigger fires. Without filters, the trigger activates for all matching events.
Common filter examples:
Run only for a specific offer
Run only for a specific product
Run only for a specific category or lesson
Filters ensure workflows do not run unintentionally for unrelated courses or products.
Common Issues and Fixes
Workflow Runs for All Products or Offers
Cause: No filters were applied to the trigger.
Fix: Edit the trigger and add a filter to target a specific product, offer, or category.
Workflow Does Not Trigger as Expected
Cause: The trigger event has not actually occurred (for example, access was already granted before the workflow was published).
Fix: Confirm the trigger event happens after the workflow is published, then test again.
User Login Trigger Fires Multiple Times
Cause: The User Login trigger activates on every login event.
Fix: Add conditions or workflow logic to prevent repeated actions if needed.