ZyanDocs

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

Email

TriggerNeeds
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

TriggerNeeds
Content approval requested
Content approval overdue
Client content review completed
Website article is live
Post published
Publishing needs attention
Google review receivedGoogle Business Profile

CRM and leads

TriggerNeeds
Lead created
Lead status changed
Lead assigned
Deal stage changed
HubSpot deal stage changedHubSpot
E-signature document completedPandaDoc or DocuSign
Visitor identifiedLeadPost
External eventMake or Zapier
Webhook receivedA webhook endpoint you minted

Forms and bookings

TriggerNeeds
Form submitted
Booking created
Booking status changed
Booking rescheduled
Booking attended
Booking no-show
External booking created / rescheduled / canceledCalendly or Acuity Scheduling

Client portal

TriggerNeeds
Client message received
Revision requested
Client file uploaded
Client task completed

Everything else

GroupTriggers
BillingInvoice paid; Invoice overdue
Projects & tasksProject status changed
Messages & inboxSMS received; Social DM received; Instagram phrase received
VoiceVoice call outcome — the handoff from a completed AI call
OutreachOutreach reply received; Smartlead reply received; Decision resolved
ScheduleSchedule — 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.

FieldWhat it sets
RepeatsWhich mode — at a time on given days, or every N minutes
At timeHH:MM, for the day-based mode
On daysWhich days of the week
Every (minutes)The interval, with a five-minute floor
TimezoneAn IANA timezone name

Steps

Flow

StepWhat it does
ConditionBranches on a field from the trigger record
WaitPauses the flow for a duration in minutes

CRM

StepWhat it does
Route leadSends the lead down your routing rules
Update leadChanges fields on the lead
Notify teamInternal notification
Add lead to pipelinePuts it in a pipeline
Move deal stageAdvances the deal
Create taskCreates a task
Add visitor to CRMTurns an identified visitor into a record
Stop if existing clientEnds 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.

StepProvider
Send email
Send SMS / Text the leadA connected texting line
Message the client in their portal
Email the client
Send announcement
Send Slack message / Slack direct messageSlack — agency workflows only
Send Teams notificationMicrosoft Teams
Send Telegram messageTelegram
Send WhatsApp templateWhatsApp
Reply to Instagram DMInstagram
Manage Microsoft emailMicrosoft 365
Reply to the Google reviewGoogle Business Profile

Voice and content

StepWhat it does
AI voice callEnrols the triggering lead in a voice campaign. Needs a running campaign to enrol into
Create content draftCreates a draft in the content pipeline
Request content approvalSends it for approval

Integrations

ProviderSteps
NotionCreate Notion page
AirtableWrite Airtable record
HubSpotCreate or update deal; update stage; upsert contact
PipedriveUpsert person; create deal; move stage
MailchimpAdd member; add or remove tags
Constant ContactAdd contact
AttioUpsert person
Zoho CRMUpsert lead
AsanaCreate task
ClickUpCreate task
Google SheetsAdd row to Google Sheets
Google CalendarCreate calendar event
ApolloEnroll in Apollo sequence
SmartleadEnroll in Smartlead campaign
Zyan sequencesEnroll in sequence; enroll in SMS campaign
Make / ZapierSend to Make or Zapier
Any HTTPS endpointSend 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

SymptomCauseFix
A step you need is not in the paletteIt is agency-only and this is a client workflowScope cannot change — rebuild as an agency workflow
The trigger you want is not listedIt may be named for the provider rather than the actionSearch the picker by provider name — they are indexed as keywords
Enable is blocked by a stepIts integration is not connectedUse the step's Manage … link
The AI voice call step does nothingThere is no running voice campaign to enrol intoCreate and start the campaign first
A Smartlead or Apollo enrolment never sendsEnrolments are created paused by designActivate the sequence at the provider
A Schedule trigger rejects your intervalInterval mode has a five-minute floorUse five minutes or more