Workflows lets you automate repeatable work in Hive. Build a workflow with a When trigger and one or more Then operations so Hive can update actions, notify people, run Buzz jobs, and more — without manual follow-up.
Open App Library from the left sidebar, then open Workflows to create and manage workflows.
Creating a workflow
Each workflow has two parts:
When (trigger) — the event that starts the workflow
Then (operations) — the steps Hive runs after the trigger (and any conditions) match
Find your way around a workflow
Each saved workflow has three tabs:
Overview: read what the workflow does, with its details and recent runs.
Editor: change the trigger and steps.
Runs: see when the workflow ran and whether each run succeeded.
In the Editor, steps show as one numbered list under Then…. To add to the list, select + and choose one of these:
Add step: choose an operation, then set it up in the panel that opens.
Add if condition: add an If row with one blank step inside it. In the Conditions panel, select Add condition. Steps inside the If run only when its conditions match. With no conditions, the If always runs. An If cannot go inside another If.
To add another step inside an If, point to the line below its last step and select +.
Drag a step to move it, including into or out of an If. An If moves with the steps inside it.
Build a workflow with Buzz
With Buzz enabled in your workspace, you can describe a workflow and refine it alongside the visual editor.
Open Workflows and select Create workflow.
Choose Create with Buzz. In Describe your workflow, explain what should start the workflow and what should happen next. Include the project or other details Buzz needs. For example: “When an action’s status changes to Blocked, clear its start and due dates.” You can also start from one of the examples: Daily project brief, Triage new requests, or Email to task.
Select Create with Buzz to start. Buzz opens beside the workflow editor and prepares a draft. If Buzz needs more information, it asks you in the conversation. If the workflow needs a connection, such as Gmail or Outlook, Buzz helps you set it up there too.
Review the draft and send follow-up messages to request changes. You can also edit the trigger and steps manually once Buzz has finished or you have selected Stop Buzz.
Check the workflow’s name, projects, trigger, steps, and required settings. Select Save to save any changes you make after Buzz has finished.
For simple tasks, Buzz usually adds a Give Buzz a job step. For more complex requests, such as branching logic, several sources, or removing duplicates, Buzz may build and attach a snippet instead.
Saving and enabling: Workflows started with Create with Buzz begin Disabled. When Buzz finishes building a complete workflow, Hive saves it automatically, still disabled, and it appears in your Workflows library.
If you leave before Buzz has finished, the workflow is not saved. To keep your work, select Save before you leave. If Buzz is still working, select Stop Buzz first.
You can also ask Buzz to save, publish, or turn on the workflow. Before saving, Buzz summarizes the trigger, scope and steps. Asking Buzz to save keeps the workflow disabled. Asking it to publish or turn on saves and enables the workflow. Buzz confirms whether it is live or saved but off. Incomplete drafts must be corrected before they can be saved.
You can also save manually with Save. To activate it, choose Enabled in the status menu at the top of the page before saving. After the first save, choose Enabled in the status menu at the top of the page, or choose Status > Enabled in the workflow’s three-dot menu in the library. A change here applies right away. If you have unsaved changes, save or discard them first.
Use these controls while building:
Stop Buzz: Stop the current response so you can review or edit the draft.
Build with Buzz: Open or close the conversation panel. Your draft stays in the editor when you close it.
You can also choose Build manually when creating a workflow. In the main Workflows editor, Build with Buzz is available for new and existing workflows you can edit. For manual edits and changes to existing workflows, select Save to apply your changes.
When — common triggers
Examples of triggers you can use:
Assignees changed
Status changed
Action created
Action updated
Labels added
Button clicked
Arrived in column / Arrived in project
Proof approval changed
On a schedule
Form submitted
Email received
Message received / Slack message posted
API request received
Salesforce record created or updated
Project updated
Some triggers are feature-gated (for example meetings, CRM, tables, file library, or timesheets) and appear when those apps are enabled. Some triggers must be used alone and cannot be combined with other trigger types.
Then — common operations
Examples of operations you can run:
Create action / Add subactions / Duplicate action / Archive action
Set assignees / Set project / Set section / Set status / Set urgency
Add labels / Create label / Remove labels
Apply action template / Set due date / Clear dates
Add followers / Remove followers / Set sprint
Archive project / Create project from template / Create baseline
Send email / Send Slack message
Give Buzz a job / Send deadline digest / Run snippet / Generate creative draft
Enroll in sequence / Score action
Available operations depend on your plan and enabled apps. Send email and Send Slack message require a paid plan.
Set due date
A Set due date step changes the due date of the action.
Choose Today (date triggered), or choose Adjust due date by and enter a number of days. Hive counts the days from the day the workflow runs.
To set a time too, enter it in Due time (optional). Hive uses the workflow owner’s timezone. If you leave the time empty, Hive sets only the date.
By default, the step changes only actions that already have a due date. To also set a due date on actions without one, select Also set a due date on actions that don't have one.
Choose whether the workflow owner follows created actions
In a Create action operation, Follow actions created by this workflow controls whether the workflow owner is automatically added as a follower of the new action.
Open the workflow for editing and select its Create action operation.
Leave Follow actions created by this workflow selected to add the owner as a follower, or clear it to turn off this automatic following.
Select Save.
This option is on by default, including for existing workflows that have not changed the setting. It applies to actions created by that operation; it does not remove followers from previously created actions.
Turning it off does not override an explicit Add followers operation or the normal following behavior associated with assigning someone to an action.
Send Slack message
For new Slack automations, use the native Workflows app. Add a Send Slack message operation and choose a fixed channel or DM, Specific people, Triggering action assignees, or Dependent action assignees.
See Send Slack messages with App Workflows for setup, dynamic recipients, sending options, and troubleshooting. This operation requires a paid plan and a workflow that processes a Hive action.
Send email
Enter a subject and body (message).
Optionally link the related action in the email.
Type an email address, or use tokens such as Created by (useful for emailing the person who submitted a form), Assignee, Project members, Project owner or Followers. Project owner emails each owner of the action’s project who can see the action. If the project has no owner, the other recipients still get the email.
To email the people chosen in a User custom field on the action, select Action custom field in the recipient list and pick the field. Single- and multi-select User fields work. Only internal workspace members who can access the action get the email. If the field is empty, no email goes to it, and the workflow still runs.
Add action details to the subject or message
Click in the subject or message where the detail must go. In the Recipe data panel, choose a token. Hive puts in the value when it sends the email.
Subject and message: First name, Created by, Assignee, SimpleID (the action’s number), Action ID, Due date, Action Title, Project Name, Created date, Status, Action URL and Form submission URL.
Message only: Action Description (Rich Text).
For example, a subject with “Request #”, then SimpleID, then “ – ”, then Action Title becomes “Request #8465 – New laptop”.
The Recipe data panel does not list form answers or custom field values for the subject or message.
Personalize emails with first names
Use the First name token to personalize the subject or message for each recipient.
Open your Send email operation and add the recipients.
Select Send individual email to each recipient.
Click in the subject or body where you want the name to appear. In the Recipe data panel, choose First name.
Finish writing your email, then select Save when your changes are ready.
For example, adding the First name token after “Hi ” creates a greeting such as “Hi Ada,” or “Hi Grace,” in each recipient’s email.
Hive uses the first name available in the recipient’s details. If no first name is available, the token is replaced with a blank value. For example, “Hi ” followed by the token and a comma becomes “Hi ,”. Use a greeting without a name if recipient names may be missing.
Keep Send individual email to each recipient selected while using this token. If you turn it off, remove any First name tokens from the subject and body; otherwise, the email step will fail.
The body instructions above apply to messages you write in the email editor. When Use Buzz output from previous step is selected, Buzz’s response supplies the body instead.
Give Buzz a job
Buzz is Hive's AI assistant. Add a Give Buzz a job step and describe the result you want in What should Buzz do?. Then select Create AI workflow. Buzz builds, tests and publishes a snippet and connects it to the workflow.
Older Give Buzz a job steps keep their Job, Title and Prompt settings. To change one to a Buzz-built step, open it and select Convert to AI workflow.
In a workflow that runs On a schedule, you can also add Send deadline digest. See example 2.
Email drafts for the assignee: In a workflow triggered by an action, Buzz can create an email draft in the mailbox of that action’s assignee for them to review. This only works when the workflow owner created the triggering action or is an owner of its project. Otherwise, Buzz does not create the draft.
Manage workflows in the library
Open the Workflows app to see the library. Each row is a workflow or a folder.
Tabs
All workflows: all workflows that are not archived.
Created by me: the workflows that you created.
Favorites: the workflows that you marked with the star.
Archived: archived workflows only. Archived workflows do not run.
Folders
Folders show as rows above the workflows that are not in a folder. Select the arrow beside a folder to open or close it.
To make a folder, select the folder icon at the top right of the library.
To make a new workflow in a folder, select + on the folder row.
To put a workflow in a folder, choose Add to folder or Move to folder in its three-dot menu.
To rename or delete a folder, right-click the folder row or select its three-dot menu.
A folder with no workflows in the current tab does not show. To show it, turn on Show empty groups in Display.
Find workflows
Filter: filter by Status, Created by, Owner, Folder or Favorite. Select Clear to remove all filters.
Search: select the magnifying glass and type part of a workflow name.
Column headers: select a column header to sort, filter, group or hide by that column.
Display
Select Display to change how the library shows workflows:
Group by: Folder (the default), Status or No grouping.
Sort by: Created at, newest first, is the default. Select Add sort to sort by more than one column.
Show empty groups: show folders that have no workflows in the current view.
Columns: select a column to show or hide it. Status, Owner and Created at show by default.
To go back to the default display, select Reset. Your display choices go back to the defaults when you reload the page.
Change many workflows at once
Select the checkbox on each workflow row. To select all workflows in a folder, select the checkbox on the folder row. To select a range, select one checkbox, then hold Shift and select another.
In the bar at the bottom of the library, choose Status, Copy, Move to folder, Favorite, Archive or Delete.
Workspace admins also see Owner in the bar, but not when the selection includes a Hive-managed workflow.
The three-dot menu
To open a workflow’s menu, select its three-dot menu or right-click its row. The options depend on your permissions and the type of workflow.
Available options include:
Rename
Status: Enabled or Disabled
Owner: workspace admins only (see below)
Copy: the workflow URL, title, ID, or title as a link
Duplicate
Add to folder or Move to folder
Edit, or View if you have read-only access
Open in new tab
View runs
Favorite or Unfavorite
Archive or Unarchive
Delete: deleted workflows cannot be restored
Owner: a workspace admin can make themselves the owner of a workflow. Hive asks you to confirm first. If other items move with the workflow, the confirmation lists them. Select Transfer to continue. You can also select the owner’s name under Properties on the workflow’s Overview tab.
The same menu opens from the three-dot menu beside the title on a workflow’s page.
Archived workflows
Archived workflows do not run, and you cannot enable them. On an archived workflow, Status shows “Archived workflows don't run. Unarchive to enable.”
To use an archived workflow again:
Open the Archived tab.
Choose Unarchive in the workflow’s three-dot menu. The workflow moves back to All workflows.
Set Status to Enabled.
If you archive a workflow by mistake, select Undo in the message that shows.
Keyboard shortcuts
1 to 4: open a tab
F: open Filter
Shift+V: open Display
/: open the search
↑ / ↓ or J / K: move to a row
X: select or clear the row
Shift+↑ / Shift+↓: select more rows
Enter: open the workflow, or open or close the folder
Cmd+A (Mac) or Ctrl+A (Windows): select all
Esc: clear the selection
Option+Shift+F (Mac) or Alt+Shift+F (Windows): clear all filters
Workflow examples
Example 1: Clear the start and due dates when status becomes Blocked — Trigger: Status changed to Blocked. Operation: Clear dates.
Example 2: Email a list of actions that are due soon — Trigger: On a schedule. Operation: Send deadline digest. Choose the actions to track, how many days to look ahead or back, the recipients, and what Buzz must write.
Example 3: Email the person who submitted a form when the request is done — Trigger: Status changed to Completed. Operation: Send email. As the recipient, choose Created by, the person who submitted the form. Add the SimpleID and Action Title tokens to the subject so they know which request it is.
Workflow runs
To see runs for all workflows, select View runs (the clock icon) at the top right of the Workflows library. Choose a date range of up to 30 days and, if you want, one workflow. The chart shows successful and failed runs by day. Run history lists each run with its status, who triggered it and when.
FAQs
Is Workflows free for all plans?
Workflows is available as a Hive app. Activity (active workflows and execution runs) is limited by subscription type. Some operations — including Send email and Send Slack message — require a paid plan.
Can I make my Workflow private?
No. At this time, workflows are visible and accessible to workspace members.
Who can edit workflows?
The workflow’s creator, its owner, and workspace admins can edit a standard workflow. Other workspace members with access to Workflows can open it in read-only mode.
Some settings require the workflow owner. For example, only the owner can edit Salesforce triggers or add or replace a snippet.
How do I change who owns a workflow?
A workspace admin can make themselves the owner of a workflow. In the Workflows library, open the workflow’s three-dot menu, choose Owner, and select your name. Hive asks you to confirm and lists any other items that move with the workflow. Select Transfer. You can also select the owner’s name under Properties on the workflow’s Overview tab.
To change the owner of several workflows at once, select them in the library, then choose Owner in the bar at the bottom. The workflows must all have the same owner.
A workspace admin can only make themselves the owner, and other members cannot change the owner. To give a workflow to someone else, that person can take it over if they are a workspace admin. Otherwise, contact Hive support.
Why does a workflow open in read-only mode?
If you can view a workflow but do not have permission to edit it, you’ll see a Read-only workflow notice. You can scroll through the workflow to review its trigger and steps, but you cannot change its name, settings, or enabled status. Save and Run now are not available.
In the Workflows library, you can open the workflow by selecting its row or choosing View from its three-dot menu. To see its runs, select the Runs tab.
Hive-managed workflows also open read-only in the general workflow editor. Workspace admins can change them through their dedicated settings in the workflow library.
Why does a run show “Step skipped: Operation was skipped”?
Hive skipped the step because it had no action to work on, or because the workflow owner cannot edit the action's project.
An operation uses the action from the last Create action above it. If no Create action is above it, it uses the action that started the workflow. If the workflow started without an action, for example with Email received, operations above the Create action have no action and are skipped.
To change the new action, put Set project, Set assignees and similar operations below Create action. To change the action that started the workflow, put them above Create action.
The conditions on an If still check the action that started the workflow, not the action that Create action made.
A step with conditions that do not match is also skipped. The run then shows the unmet condition instead.
Why didn’t my workflow create an email draft for the assignee?
Buzz only drafts into an assignee’s mailbox when the workflow owner created the triggering action or is an owner of its project. Check who owns the workflow in the Owner column of the library, and transfer ownership if needed.
What happened to Workflow Buttons?
You can use the Button clicked trigger in Workflows. Automations made with the older Workflow Buttons app are not in the Workflows library. To change, turn off or delete one, open App Library, find Workflow Buttons and select Open. In Manage Workflow Buttons, set the automation to Disabled, or select Delete. The Workflow Buttons app shows only in workspaces created before Workflows was released.
Can a workflow button open a form?
Yes. In Workflows, choose Button clicked as the trigger and add the Open form operation. When someone clicks the button on an action card, Hive opens the selected form with details from that action prefilled where you have mapped them.
The workflow continues only after the person submits the form. Closing it without submitting does not run the remaining steps. If the form creates an action, you can configure that new action as a subaction of the action where the button was clicked.












