Workflow Triggers in Kyrios

This article is for Kyrios users building workflows who need to understand which triggers are available and which trigger should be used to start automation based on contact activity, events, payments, appointments, or system changes.

A workflow trigger is the event that starts a workflow and enrolls a contact when specific conditions are met.

A trigger always runs first in a workflow and determines when automation begins. Actions follow triggers and define what happens next after the trigger fires.

You can configure one or multiple triggers in a single workflow, and each trigger can optionally include filters to narrow when it runs.

Workflow triggers are configured inside the Workflow Builder and are evaluated in the order they appear.

Filters allow you to limit a trigger so it only fires when specific conditions are met.

For example, the Form Submitted trigger can run for all forms or be limited to a specific form using filters.

Contact triggers run when contact-level data changes.

Runs daily at 8:00 AM when a contact’s date of birth matches the current day.

Common use cases: Sending birthday messages, coupons, or special offers.

Runs whenever any contact information is modified.

Common use cases: Syncing data, internal notifications, or updating records.

Runs when a new contact is created in Kyrios.

Common use cases: Welcome messages and onboarding workflows.

Runs when a contact opts out of one or more communication channels.

Common use cases: Compliance handling and opt-out management.

Runs when a specific tag is added to or removed from a contact.

Common use cases: Segmentation, campaign entry, or conditional automation.

Runs based on a custom date field stored on the contact record.

Common use cases: Follow-ups, renewals, or anniversary reminders.

Runs when a note is added or edited on a contact.

Common use cases: Internal tracking and handoff workflows.

Runs when a manual task is created or completed.

Common use cases: Sales task follow-ups and accountability tracking.

Runs when a contact’s engagement score reaches defined thresholds.

Common use cases: Identifying highly engaged or disengaged contacts.

Event triggers run when a system or interaction event occurs.

Runs when data is received from an external system via webhook.

Common use cases: Third-party integrations and custom automation.

Runs when a call reaches a specific status such as incoming, completed, or missed.

Common use cases: Call tracking and follow-up automation.

Runs when an email is opened, clicked, bounced, or unsubscribed.

Common use cases: Email engagement tracking and re-engagement workflows.

Runs when a customer replies or interacts in a conversation channel.

Common use cases: Automated responses and support workflows.

Runs when any form is submitted.

Common use cases: Lead capture and form-based automation.

Runs near real-time (polled every 5 minutes) when a selected Google Form receives a response.

Common use cases: External form submissions synced into Kyrios workflows.

Runs when a tracked link is clicked.

Common use cases: Click-based engagement tracking.

Runs when a Facebook lead form is submitted.

Common use cases: Social lead capture.

Runs when an Instagram lead form is submitted.

Common use cases: Social lead capture from Instagram campaigns.

Runs when a LinkedIn lead form is submitted.

Common use cases: B2B lead capture.

Runs based on video interaction events.

Common use cases: Video engagement follow-ups.

Runs after number validation checks whether a phone number is valid or a landline.

Common use cases: Preventing SMS delivery failures and reducing messaging costs.

Runs when an SMS message fails to send.

Common use cases: Error handling and retry logic.

Runs when a visitor views specific funnel or website pages.

Common use cases: Page-based engagement automation.

Runs when a quiz is submitted.

Common use cases: Quiz-based segmentation and follow-up.

Runs when a new review is received.

Common use cases: Review alerts and reputation management.

Runs when a new prospect record is created.

Common use cases: Immediate follow-up automation.

Appointment triggers run when calendar events occur.

Runs when an appointment is scheduled, rescheduled, canceled, or marked as no-show.

Common use cases: Appointment reminders and follow-ups.

Runs when a customer books an appointment.

Common use cases: Confirmation messages and preparation workflows.

Opportunity triggers run when pipeline or opportunity data changes.

Runs when an opportunity’s status updates.

Runs when a new opportunity is created.

Runs when any opportunity data changes.

Runs when an opportunity moves between pipeline stages.

Runs when an opportunity remains in a stage for a defined period.

Common use cases: Sales follow-ups and pipeline optimization.

Affiliate triggers run when affiliate-related events occur.

Runs when a new affiliate is created.

Runs when an affiliate generates a sale.

Runs when an affiliate joins a campaign and captures referral data.

Common use cases: Affiliate onboarding and commission tracking.

Course triggers run when contacts interact with courses or memberships.

Runs based on progress through course categories.

Runs based on lesson progress.

Runs when a user signs up for a course.

Runs when access to an offer is granted or revoked.

Runs when access to a course product changes.

Runs when a course is started or completed.

Runs when a user logs in to access a course or membership.

Payment triggers run when financial events occur.

Runs when invoice details or status change.

Runs when a payment is successfully received.

Runs when an order form is submitted.

Runs when any product purchase is submitted.

Runs when documents or contracts are changed.

Runs when a subscription status updates.

Runs when a refund is processed.

Shopify triggers run when connected Shopify store events occur.

Runs when a cart is abandoned.

Runs when an order is placed.

Runs when an order is fulfilled.

IVR triggers run when inbound phone interactions occur.

Runs when an IVR session begins.

Pro tip: Start with the IVR Workflow Recipe for faster setup.

These triggers run when users comment on social posts.

Runs when a comment is added to a post.

Common use cases: Engagement automation and moderation.

Community triggers run when group access or engagement changes.

Runs when a contact is added to or removed from a community group.

Runs when a member’s leaderboard level changes.

Certificate triggers run when certificates are issued.

Runs when a certificate is issued through workflows.

Note: Issued certificates appear in Memberships → Certificates → Issued Certificates.

Yes. Multiple triggers can be added to a single workflow and each trigger can independently enroll contacts.

No. Many triggers support filters, but not all. Filter availability depends on the trigger type.

Yes. Filters allow narrowing triggers to specific forms, tags, pipeline stages, pages, and more.