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.

Tip: Workflows has a new design. To go back to the earlier design for now, open the Workflows app and select the flask icon beside the Workflows title. Your choice is saved in that browser.

Each workflow has two parts:

Each saved workflow has three tabs:

In the Editor, steps show as one numbered list under Then…. To add to the list, select + and choose one of these:

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.

With Buzz enabled in your workspace, you can describe a workflow and refine it alongside the visual editor.

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 Enable workflow in the three-dot menu. A change here applies right away. If you have unsaved changes, save or discard them first.

Use these controls while building:

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.

Examples of triggers you can use:

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.

Examples of operations you can run:

Available operations depend on your plan and enabled apps. Send email and Send Slack message require a paid plan.

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.

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.

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.

Use the First name token to personalize the subject or message for each recipient.

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.

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.

The options in a workflow’s three-dot menu depend on your permissions and the type of workflow. Available options include:

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.

To see runs for all workflows, select View runs at the top 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.

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.

No. At this time, workflows are visible and accessible to workspace members.

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.

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.

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.

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, and transfer ownership if needed.

You can use the Button clicked trigger in Workflows. Existing buttons continue to be stored and edited in the Workflow Buttons app.

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.