What the AF is a trigger — the first domino in every automation
If you're new to automation, there's a conceptual shift that makes everything else click. It's this: automations don't run continuously. They don't sit there doing things all the time. They wait for something to happen — and that "something" is the trigger.
The trigger is the event that starts an automation. Everything else in the workflow — the actions, the notifications, the document generation, the data updates — those all happen because a trigger fired.
A trigger is an event that starts an automation. "When X happens, do Y" — the trigger is X. Every automation has one.
Common triggers in small business automation
- Form submitted — someone fills out a contact form, an intake form, a safety report, a job application
- Record created or updated — a new lead added to CRM, a deal moved to a new pipeline stage, a field updated on an account record
- Document signed — an estimate, a contract, an NDA gets a signature in Zoho Sign or DocuSign
- Payment received — an invoice is marked paid in your accounting system
- Email received — a specific type of email arrives in a monitored inbox
- Date or time — every Monday at 8am, on the 15th of every month, 30 days before a contract renewal
- Scheduled interval — every hour, every day, every week
Why trigger selection matters
The trigger determines when the automation runs — and picking the wrong trigger can cause problems. An automation that fires too early will use incomplete data. One that fires too late misses the window for the action to be useful. One that fires on the wrong event will do the right thing at the wrong time.
A classic example: you want to send a welcome email when someone becomes a customer. The wrong trigger is "when a lead is created in CRM" — that fires when they first contact you, not when they become a customer. The right trigger is "when a deal is moved to Closed Won" or "when a signed contract is received." Same goal, very different timing.
Triggers and conditions
Most automation platforms let you add conditions to a trigger — essentially, "only fire this automation IF certain things are true." For example: "when a form is submitted AND the project type is Commercial AND the value is over $10,000." The trigger is the form submission; the conditions filter which submissions actually start the workflow.
This is where automation logic starts to get interesting — and where it starts to really match the nuances of how a business actually works.
More plain-English business tech
No jargon. No sales pitch. Just the stuff you actually need to know.
See all posts →