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 created | Fires only for actions created after the workflow is activated — not retroactively. |
Action updated | In the builder, you select which fields trigger it — it doesn't watch all fields. The default selection is status changed. Common triggers includes quick picks such as Status changed and Priority changed. When you apply an action template to an action, the workflow runs only for the fields that the template changes. |
Assignees changed | Covers both individual (people picker) and team assignee — team assignee is not a separate trigger row. |
Arrived in column / Status changed | Both use the same status field. Two picker rows are available for convenience — they're the same underlying trigger. |
Labels added | |
Button clicked | Must be the first trigger on the workflow. Cannot combine with Assignees changed or Action created. Can combine with status, labels, and others. |
Proof approval changed | Fires when a proof is approved, rejected, or changes are requested. |
Arrived in project | |
Project created | Standalone — cannot be combined with other triggers. |
Project 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 submitted | Standalone. Fires on a complete Form Submission — not when a form is opened or left in draft. |
API request received | 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 received (Hive chat) | Standalone. |
Slack message posted | Standalone. Requires Slack connected to your workspace. |
Salesforce record created or updated | Standalone. Requires Salesforce connected to your workspace. |
Run a workflow when priority changes
In Action updated, select Priority changed under Common triggers. This adds a priority rule next to the default Status changed rule. Remove the status rule if you only want priority changes to run the workflow.
To limit the rule to certain priorities, select Advanced and choose them in From previous value or To current value. A rule with priorities chosen there won't run when an action gets its first priority or loses it. Changing priority on many actions at once runs the workflow for each action.
Deleted priority levels: When a priority level is deleted, Hive counts this as a priority change on each action that had that level. A rule with no priorities in From previous value or To current value runs the workflow one time for each of these actions. Webhooks that watch priority also send an update for each action. A rule with priorities chosen in From previous value or To current value does not run when a priority level is deleted.
Set up Project updated field rules
Use Project 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 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 created | Standalone. |
Meeting updated | Standalone. To run only for some changes, add rules under Only run when these fields change. A rule can watch a calendar field, such as Start time, Title, or Attendees, or a meeting custom field. Without rules, it runs on any calendar change but not when a custom field is edited. When you mix calendar fields and custom fields, only Any rule matches is available, because these changes arrive as separate updates. |
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 cancelled | Standalone. |
Meeting marked no-show | Standalone. Requires Zoom CRM recordings connected — without it, this trigger won't fire. |
CRM records
Trigger | Notes |
Account 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 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 created | Standalone. |
Contact form submitted | Runs each time someone submits one of your contact forms, for new people and for people already in Hive CRM. Under Contact forms, select the forms to watch, or leave it empty to run for any contact form. Standalone. |
Person updated | Runs when a person custom field changes as your field change rules describe. See "Set up Person updated" below. Use it as the workflow’s only trigger. |
Opportunity created | Standalone. |
Opportunity updated | Runs when an opportunity update matches your field change rules. A rule can watch a built-in field, such as Stage, Amount, Owner, or Close date, or an opportunity custom field. Standalone — use it as the workflow’s only trigger. |
Set up Account updated
In the workflow builder, choose Account 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. Your account custom fields are under Custom fields, after the built-in fields. Custom fields use Changed, Is set, and Is cleared.
Both CRM account triggers require Hive CRM to be enabled. Use Account created and Account updated in the standard Workflows builder; they are separate from the CSM Hub account-field triggers below.
Set up Person updated
Opportunity updated and Person updated use the same rule editor as Account updated. Person updated watches person custom fields only. If your workspace has no person custom fields, the panel asks you to add one in CRM settings first.
In the workflow builder, choose Person updated under People.
Select Add field change rule.
Choose the person custom field and the type of change. Optionally, set From previous value or To current value.
To watch more fields, add more rules and choose All rules match or Any rule matches under Run when.
Select Save trigger, add your steps, then save the workflow.
Person updated runs when someone changes a person’s custom field in Hive CRM or through the API. It also runs when someone who is already in Hive CRM submits a contact form again and the form fills a custom field that was empty. A repeat submission does not replace a custom field that already has a value. Saves that leave all watched fields unchanged do not run the workflow.
See which fields changed in a run
Open the workflow, select the Runs tab, and select a run in Run history. When an Account updated, Opportunity updated, or Person updated run was started by a custom field change, the Changed fields box lists each changed custom field with its old and new value. For Meeting updated, the box also lists changed calendar fields, such as Start time.
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 added | Files app | Standalone. |
Table record created | Tables | Standalone. |
Table record updated | Tables | Standalone. |
Table field changed | Tables | Standalone. |
Timesheet 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 Assignees changed — 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 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 submitted
API request received
Email received
Message received (Hive chat)
Slack message posted
Salesforce record created or updated
Project created
Project updated
All meeting triggers (created, updated, completed, cancelled, no-show)
Person created / Contact form submitted
Opportunity created / updated
Account created / Account updated (Hive CRM)
Timesheet approved
File added
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)