This is the complete list of triggers available in the Workflows builder. Use it to find which trigger fits your automation, understand what app or plan is required, and know which triggers can't be combined with others.
Standalone triggers can't be stacked — they must be the only trigger on a workflow. If you try to combine a standalone trigger with another, the workflow won't save. These are marked below.
Always available (Workflows app on)
These triggers are available to all workspaces with the Workflows app enabled.
Trigger | Notes |
Action is created | Fires only for actions created after the workflow is activated — not retroactively. |
Action is updated | In the builder, you select which fields trigger it — it doesn't watch all fields. The default selection is status changed. |
Assignee changes | Covers both individual (people picker) and team assignee — team assignee is not a separate trigger row. |
Arrives in column / Status changes | Both use the same status field. Two picker rows are available for convenience — they're the same underlying trigger. |
Label is added |
|
Button is clicked | Must be the first trigger on the workflow. Cannot combine with Assignee changes or Action is created. Can combine with status, labels, and others. |
Proof approval status changes | Fires when a proof is approved, rejected, or changes are requested. |
Arrives in project |
|
Project is created | Standalone — cannot be combined with other triggers. |
Project is updated | Standalone — cannot be combined with other triggers. |
On a schedule | Standalone. Uses the workflow creator's timezone. In interval (minutes) mode, the interval must be a multiple of 15. Daily, weekly, and monthly schedules don't have this restriction. |
Form is submitted | Standalone. Fires on a complete Form Submission — not when a form is opened or left in draft. |
API Request | Standalone. Trigger payload is visible in run logs. |
Email received | Standalone. You select a connected inbox (Gmail or Outlook) — not a free-floating mail trigger. |
Message is received (Hive chat) | Standalone. |
Slack message is sent | Standalone. Requires Slack connected to your workspace. |
Salesforce event | Standalone. Requires Salesforce connected to your workspace. |
Hive CRM triggers (CRM on)
These triggers are only available when Hive CRM is enabled on your workspace.
Meetings
Trigger | Notes |
Meeting is created | Standalone. |
Meeting is updated | Standalone. |
Meeting completed | Standalone. Default: fires when the transcript is available. The builder includes a checkbox — "Only run when a transcript is available" — which is on by default. Uncheck it to fire at the scheduled end time regardless of whether a transcript has landed. Existing workflows using the legacy Meeting ended trigger are rewritten to Meeting completed (transcript checkbox unchecked) the first time they're opened and saved. |
Meeting is cancelled | Standalone. |
Meeting is a no-show | Standalone. Requires Zoom CRM recordings connected — without it, this trigger won't fire. |
CRM records
Trigger | Notes |
Person is created in CRM | Standalone. |
Opportunity is created | Standalone. |
Opportunity is updated | Standalone. |
Account triggers
The following account field changes can trigger a workflow. In standard Workflows, these behave like standalone triggers — one account field per workflow. CSM Hub Account Workflows is a separate surface for account-level automations.
ARR
Renewal date
Health score
Last contacted
Owner
Lifecycle stage
Linked workspace
Product event count
Other app-gated triggers
Trigger | Requires | Notes |
File is added to File Library | Files app | Standalone. |
Table record is created | Tables | Standalone. |
Table record is updated | Tables | Standalone. |
Table field changes | Tables | Standalone. |
Timesheet is approved | Timesheets | Standalone. |
Older triggers not shown in the picker
These triggers aren't available in the picker for new workflows, but existing workflows that use them continue to run.
Trigger | What it is |
Team assignee | Covered by Assignee changes — team assignee is part of that trigger, not a separate row. Old workflows using it as a standalone trigger still run. |
Project health / portfolio status | Not offered for new workflows. Existing workflows using it still run. |
Quick reference: standalone triggers
The following triggers cannot be combined with any other trigger on the same workflow. Each must be the sole trigger. Button is clicked is intentionally excluded — it must be the first trigger but can combine with others, so it doesn't follow the standalone rule.
On a schedule
Form is submitted
API Request
Email received
Message is received (Hive chat)
Slack message is sent
Salesforce event
Project is created
Project is updated
All meeting triggers (created, updated, completed, cancelled, no-show)
Person is created in CRM
Opportunity is created / updated
Timesheet is approved
File is added to File Library
All Table triggers (record created, record updated, field changes)
Account field triggers (ARR, renewal date, health score, last contacted, owner, lifecycle stage, linked workspace, product event count)