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.
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. |
Set up Project is updated field rules
Use Project is updated to run a workflow when a selected project field changes. Use it as the workflow’s only trigger.
Create or edit a workflow and choose Project is updated.
Select Add field rule.
Choose the project status or a project custom field to watch.
Optionally narrow the new value using the controls for that field type, described below.
Configure the workflow’s operations, then save and enable it when ready.
Status, select, user, and project fields: Use Changes to to choose target values. Leave it empty to run on any change to that field.
Text, number, and date fields: The rule watches for a change to the field. Use Only when new value is to require a specific new value, or leave it blank to accept any change.
For example, watch a text custom field called Client name and enter Acme under Only when new value is. The rule matches when Client name changes to Acme. Updating another project field while Client name remains Acme does not match this rule.
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 |
Account is created | Runs when a new account is created in Hive CRM while the workflow is enabled. Enabling the workflow does not run it for existing accounts. Standalone — use it as the workflow’s only trigger. |
Account is updated | Runs when an account update matches your selected field change rules. Standalone — use it as the workflow’s only trigger. You can add multiple field change rules within this trigger. |
Person is created in CRM | Standalone. |
Opportunity is created | Standalone. |
Opportunity is updated | Standalone. |
Set up Account is updated
In the workflow builder, choose Account is updated. The default rule watches for a change to Lifecycle stage, with All rules match selected.
Choose the account field to watch and the type of change that should run your workflow.
For Changed, you can narrow the rule with From previous value and To current value. Leave these blank to accept any previous or current value.
Select Add field change rule to watch another field. Under Run when, choose All rules match to require every rule to match the same account update, or Any rule matches to run when at least one rule matches.
Choose from these change types:
Changed: The field’s value changes, including being filled in or cleared.
Is set: An empty field receives a value. You can specify a To current value to match.
Is cleared: A field with a value becomes empty. You can specify a From previous value to match.
Greater than: The field changes and its new value is above your Threshold. Available for ARR, Potential ARR, Health score, and Relationship score.
Greater than example: With a threshold of 100, a change from 150 to 200 matches because the new value is above 100. Saving the same value again does not match. Updates that leave all watched fields unchanged do not run the workflow.
Available fields: Owner, Type, Status, Lifecycle stage, Health score, Relationship score, ARR, Potential ARR, Renewal date, Subscription start date, Segment, Industry, Region, Territory, Linked workspace, and Parent account.
Both CRM account triggers require Hive CRM to be enabled. Use Account is created and Account is updated in the standard Workflows builder; they are separate from the CSM Hub account-field triggers below.
CSM Hub account-field triggers
These triggers use CSM Hub account fields and are separate from the Hive CRM account triggers above. In standard Workflows, use one of these account-field triggers per workflow. CSM Hub Account Workflows provides a separate place to manage 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
Account is created / Account is updated (Hive CRM)
Timesheet is approved
File is added to File Library
All Table triggers (record created, record updated, field changes)
CSM Hub account-field triggers (ARR, renewal date, health score, last contacted, owner, lifecycle stage, linked workspace, product event count)