Triggers and steps reference
Every trigger that can start an automation and every step it can take, grouped as the pickers group them, with what each one needs to be connected.
An automation is one trigger plus a graph of steps. This page lists both, in the groups the pickers use, so you can check whether the thing you want exists before you start building. Both pickers are searchable, and provider names are indexed as hidden keywords — typing a provider name finds its entries.
Before you start
Anything marked as needing a provider requires that integration connected under SettingsIntegrations. A step whose connection is not ready carries a readiness chip and blocks publishing until it is resolved.
Triggers
| Trigger | Needs |
|---|---|
| Email engagement | — |
| Email received (Gmail) | Gmail / Google Workspace |
| Email received (Microsoft 365) | Microsoft 365 |
| Email sent, flagged or moved (Microsoft 365) | Microsoft 365 |
Content and publishing
| Trigger | Needs |
|---|---|
| Content approval requested | — |
| Content approval overdue | — |
| Client content review completed | — |
| Website article is live | — |
| Post published | — |
| Publishing needs attention | — |
| Google review received | Google Business Profile |
CRM and leads
| Trigger | Needs |
|---|---|
| Lead created | — |
| Lead status changed | — |
| Lead assigned | — |
| Lead converted to client | — |
| Deal stage changed | — |
| Deal created | — |
| HubSpot deal stage changed | HubSpot |
| E-signature document completed | PandaDoc, DocuSign or Dropbox Sign |
| Visitor identified | LeadPost |
| External event | Make or Zapier |
| Webhook received | A webhook endpoint you minted |
Forms and bookings
| Trigger | Needs |
|---|---|
| Form submitted | — |
| Booking created | — |
| Booking status changed | — |
| Booking rescheduled | — |
| Booking attended | — |
| Booking no-show | — |
| External booking created / rescheduled / canceled | Calendly or Acuity Scheduling |
Client portal
| Trigger | Needs |
|---|---|
| Client message received | — |
| Revision requested | — |
| Client file uploaded | — |
| Client task completed | — |
Everything else
| Group | Triggers |
|---|---|
| Billing | Invoice paid; Invoice overdue; Subscription status changed; Subscription payment failed |
| Projects & tasks | Project status changed; External task completed; External task status changed — a linked Asana, ClickUp, Linear or Jira task |
| Meetings | Meeting notes ready — a recorded Fathom or Grain meeting; when its attendees match exactly one client, that client also gets an internal note |
| Messages & inbox | SMS received; Contact opted out of texts — a STOP reply in Messages; Social DM received; Instagram phrase received; Slack or Telegram message received — needs the channel enabled in Messages |
| Voice | Voice call outcome — the handoff from a completed AI call; Team call ended — a teammate's dial-pad call reaching completed, failed or canceled |
| Outreach | Outreach reply received; Smartlead reply received; Decision resolved |
| Schedule | Schedule — time-based rather than event-based |
Voice call outcome is the voice handoff
It is how a finished AI call becomes the start of everything else — route the lead, notify the team, book a follow-up. Pair it with the disposition on the call record.
The Schedule trigger
Time-based rather than event-based. It has two modes.
| Field | What it sets |
|---|---|
| Repeats | Which mode — at a time on given days, or every N minutes |
| At time | HH:MM, for the day-based mode |
| On days | Which days of the week |
| Every (minutes) | The interval, with a five-minute floor |
| Timezone | An IANA timezone name |
Steps
Flow
| Step | What it does |
|---|---|
| Condition | Branches on a field from the trigger record |
| Wait | Pauses the flow for a duration in minutes |
CRM
| Step | What it does |
|---|---|
| Route lead | Sends the lead down your routing rules |
| Update lead | Changes fields on the lead |
| Notify team | Internal notification |
| Add lead to pipeline | Puts it in a pipeline |
| Move deal stage | Advances the deal |
| Create task | Creates a task |
| Add visitor to CRM | Turns an identified visitor into a record |
| Stop if existing client | Ends the run when the contact is already a client |
Messaging
The right-hand column names the provider the step speaks to — where one is named, that provider has to be connected.
| Step | Provider |
|---|---|
| Send email | — |
| Send SMS / Text the lead | A connected texting line |
| Message the client in their portal | — |
| Email the client | — |
| Send announcement | — |
| Send Slack message / Slack direct message | Slack — agency workflows only |
| Send Teams notification | Microsoft Teams |
| Send Telegram message | Telegram |
| Send WhatsApp template | |
| Reply to Instagram DM | |
| Manage Microsoft email | Microsoft 365 |
| Reply to the Google review | Google Business Profile |
Voice and content
| Step | What it does |
|---|---|
| AI voice call | Enrols the triggering lead in a voice campaign. Needs a running campaign to enrol into |
| Create content draft | Creates a draft in the content pipeline |
| Request content approval | Sends it for approval |
Integrations
| Provider | Steps |
|---|---|
| Notion | Create Notion page |
| Airtable | Write Airtable record |
| HubSpot | Create or update deal; update stage; upsert contact |
| Pipedrive | Upsert person; create deal; move stage |
| Mailchimp | Add member; add or remove tags |
| Constant Contact | Add contact |
| Attio | Upsert person |
| Zoho CRM | Upsert lead |
| Salesforce | Create or update lead |
| Asana | Create task |
| ClickUp | Create task |
| Linear | Create Linear issue (in a chosen team) |
| Jira | Create Jira issue (in a chosen project) |
| Klaviyo | Add profile |
| HighLevel | Upsert contact (in the location bound on the Settings tile) |
| Google Sheets | Add row to Google Sheets |
| Google Calendar | Create calendar event |
| Apollo | Enroll in Apollo sequence |
| Smartlead | Enroll in Smartlead campaign |
| Zyan sequences | Enroll in sequence; enroll in SMS campaign |
| Make / Zapier | Send to Make or Zapier |
| Any HTTPS endpoint | Send webhook |
Outreach enrolments are created paused
Smartlead and Apollo enrolments are deliberately created in a paused state. Nothing sends until you activate them at the provider. This is a guard against an automation quietly starting an outreach sequence for everyone who fills in a form.
Connection readiness
Every trigger or step that needs a provider carries a chip. An unready step blocks publishing and names the reason in the tooltip on the Enable button. Each one also offers a Manage … link straight to the right settings tile — following it saves your draft and brings you back.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| A step you need is not in the palette | It is agency-only and this is a client workflow | Scope cannot change — rebuild as an agency workflow |
| The trigger you want is not listed | It may be named for the provider rather than the action | Search the picker by provider name — they are indexed as keywords |
| Enable is blocked by a step | Its integration is not connected | Use the step's Manage … link |
| The AI voice call step does nothing | There is no running voice campaign to enrol into | Create and start the campaign first |
| A Smartlead or Apollo enrolment never sends | Enrolments are created paused by design | Activate the sequence at the provider |
| A Schedule trigger rejects your interval | Interval mode has a five-minute floor | Use five minutes or more |