Automation trigger
The event that starts an automated workflow or sequence. Triggers can be event-based (signup, purchase, link click), behavior-based (page visit, inactivity), date-based (anniversary, scheduled date), tag-based (tag added or removed), or webhook-based (external system event). The choice of trigger determines who enters the workflow and when. Without a trigger nothing happens; with the right trigger, the same workflow runs every time the matching event occurs.
Why the trigger choice matters
Most workflows that fail in production fail at the trigger. Three reasons the trigger is the most consequential decision in any automation.
It decides who enters
The trigger is the filter that defines the audience for the workflow. A trigger of "signup" enrolls everyone; a trigger of "purchase above $500" enrolls a different group entirely. Pick the wrong trigger and the audience is wrong from the start.
It locks in the moment of intent
A welcome email sent within one minute of signup catches intent at its peak. The same email sent the next day converts at half the rate. The trigger doesn't just decide who; it decides when, and timing in automation is often more important than copy.
It reduces unnecessary sends
A behavior-based trigger ("clicked the demo link") only fires for engaged contacts. A blanket broadcast goes to everyone, engaged or not. Precise triggers cut the unsubscribe rate and protect deliverability for the rest of the program.
The five trigger families
Every automation trigger falls into one of five categories. Pick the family first, then the specific event inside it.
-
Event triggers
The bread and butter: signup, purchase, refund, link click, form submission, course module completed, deal moved to a stage. Anything the contact (or the platform on their behalf) actively does. Most workflows start here.
-
Behavior triggers
Patterns over time rather than a single event. Visited the pricing page three times in seven days. Did not open any email in 60 days. Logged in five times in the first week. Behavior triggers handle the high-intent and low-intent edges that single events miss.
-
Date triggers
Calendar-based. A subscriber's birthday. The 14-day anniversary of their signup. The first Monday of every quarter. Useful for milestones (renewal nudges, anniversary thank-yous) and scheduled campaigns that run on the same date every year.
-
Tag triggers
The contact gained or lost a tag. Tag-based triggers turn the workflow system into a flexible event bus: any other workflow can apply a tag, and a different workflow can listen for it. This is how complex multi-stage journeys get built without one giant workflow.
-
Webhook and API triggers
An external system sends an event. A Stripe webhook fires on a refund, a Calendly webhook fires when a call is booked, a custom API fires on any business event you want. Webhook triggers let workflows respond to anything happening outside the platform.
What automation triggers look like in practice
Three real-world workflows, each anchored on a different trigger family.
Coach: discovery call booked
Trigger fires the moment a Calendly call is booked. Workflow sends a confirmation email, a 24-hour reminder, and a pre-call questionnaire. Show-up rate climbs from 64% to 86% because the trigger catches the prospect's intent at peak.
E-commerce: cart abandoned
Trigger fires when a contact adds to cart but does not complete checkout within one hour. The behavior trigger is more precise than a simple "added to cart" event because it filters out completed purchases. Recovery rate sits at 13% on the resulting three-email sequence.
SaaS: trial day 7
Trigger fires seven days after signup. Workflow sends a "halfway through your trial" email with a pricing nudge, then forks: trial users who logged in this week receive a feature highlight, others receive an onboarding rescue. Trial-to-paid conversion lifts from 11% to 16%.
Metrics that tell you if a trigger is healthy
Eight angles to monitor per trigger. Together they catch silent failures (triggers that stopped firing) and noisy ones (triggers that fire too often).
Trigger fire count
How many times the trigger fired in the last 24 hours / 7 days / 30 days. Sudden drops point to a broken event source.
Enrolment rate
Of contacts who hit the trigger, how many actually entered the workflow. Reveals how much exit criteria filter out.
False fire rate
Contacts who should not have triggered the workflow but did. Often caused by overly broad triggers or stale tags.
Time to first action
Seconds from trigger to the first action in the workflow. Sudden jumps point to platform queue delays.
Trigger source breakdown
For multi-trigger workflows, which trigger fired. Tells you which event sources are doing the most work.
Re-trigger rate
How often the same contact re-enters. High re-trigger means the cooldown or re-entry rule needs tightening.
Trigger latency
Delay between the real-world event and the trigger firing in the platform. Webhook integrations can drift here.
Trigger error rate
Failed trigger attempts (auth errors, malformed payloads). Above 1% deserves an immediate look.
Related glossary terms
Concepts that sit alongside automation triggers. Read each one before deciding the trigger for a new workflow.
How systeme.io handles automation triggers
Every common trigger ships built in: events, behavior, dates, tags, and webhooks. Combine them, cool them down, exit them on success. Included on the free plan up to 2,000 contacts.
Built-in trigger library
Signup, purchase, refund, tag added or removed, link click, form submission, page visit, course progress, deal stage change, and date triggers all ship as one-click options.
Multi-trigger workflows
Fire the same workflow on any of several triggers (signup OR purchase OR webinar registration all start the same welcome). One workflow, multiple entry points.
Re-entry and cooldown rules
Decide per workflow whether a contact can re-enter, and after how long. Stops accidental loops where a tag keeps re-firing the same sequence.
Inbound and outbound webhooks
External systems can trigger workflows in systeme.io; systeme.io can fire webhooks to external systems on any trigger. Two-way integration without writing custom glue code.
Tag-based event bus
Any workflow can apply a tag; any other workflow can listen for one. Complex multi-stage journeys compose out of small workflows instead of one giant canvas.
Trigger analytics
Fire counts, enrolment rates, and error counts per trigger appear in the same dashboard as the rest of the funnel. Catch a broken trigger before it affects thousands of contacts.
Frequently asked questions
Common questions about automation triggers, and how each one plays out inside systeme.io.
An automation trigger is the event that starts an automated workflow or sequence. The trigger fires, the workflow runs. Common triggers include a new signup, a purchase, a tag added, a link clicked, a page visited, a course module completed, a deal moved to a specific pipeline stage, or a scheduled date. Without a trigger nothing happens; with the right trigger, the workflow runs every time the matching event occurs across the entire contact database.
Five families cover almost every workflow. Event triggers: signup, purchase, refund, link click, form submission. Behavior triggers: visited a page, did not open in X days, completed a course module. Date triggers: today is the customer's birthday, today is 14 days after signup, a specific calendar date. Tag triggers: a tag was added, a tag was removed, the contact joined a segment. Webhook triggers: an external system (Stripe, Calendly, Zapier, custom API) sends an event. Start with event triggers and add the others as your workflows mature.
Yes, in most platforms. A multi-trigger workflow fires when any one of the triggers occurs. Useful when several different events should produce the same outcome (signup OR purchase OR webinar registration all start the same welcome sequence). The downside is debugging gets harder, so keep multi-triggered workflows small and well-named. If two triggers should produce meaningfully different behavior, build two separate workflows instead.
A trigger is the event that starts the workflow. A condition is a filter applied inside the workflow that decides who proceeds and who exits. Example: trigger = signup; condition = country is Canada. Everyone who signs up enters the workflow, but only Canadian signups continue past the condition. Triggers are about timing; conditions are about routing. A workflow has one or a few triggers and usually several conditions that branch the path.
Three settings handle most of the problem. One: re-entry rules. Decide whether a contact can re-enter the workflow after exiting. The default of "no re-entry" is usually right for welcome workflows. Two: cooldown periods. Set a minimum gap (e.g. 24 hours) between repeat fires for the same contact. Three: exit conditions. Add tags or events that automatically pull contacts out of the workflow once the goal is met, so subsequent fires have nothing to do.
systeme.io includes triggers for signup, purchase, refund, tag added or removed, link click, form submission, page visit, course progress, deal stage change, and scheduled dates. Workflows can fire on one trigger or a combination. Webhooks let external systems trigger workflows inside systeme.io, and outbound webhooks let a systeme.io trigger fire actions in other tools. Trigger analytics show how often each trigger fires and which workflows it kicks off, all inside the same dashboard as the rest of the funnel.
Pick the right trigger inside systeme.io
Built-in trigger library, multi-trigger workflows, webhooks in and out, re-entry rules, and trigger analytics built in. Free plan covers up to 2,000 contacts.
Start for free now