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 the Workflows app from the left sidebar (or Apps) to create and manage workflows.

Each workflow has two parts:

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

Saving and enabling: Workflows started with Create with Buzz begin Disabled. Preparing a draft does not run the workflow. To activate it, switch Disabled to Enabled before saving, or save it disabled and choose Enable workflow from the workflow’s three-dot menu later.

Use these controls while building:

You can also choose Build manually when creating a workflow. In the main Workflows editor, Show Buzz is available for new and existing workflows you can edit. Buzz’s changes are applied to the saved workflow when you select Save workflow.

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 an email and Post to Slack require a paid plan.

In a Create new 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 as follower operation or the normal following behavior associated with assigning someone to an action.

For new Slack automations, use the native Workflows app. Add a Post to Slack 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. In a workflow, you can give Buzz a job such as:

Give the job a title and write a clear prompt about what Buzz should do.

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

2. Deadline digest

Use Give Buzz a job → Deadline digest to email users based on how close actions are to their due dates, supporting proactive follow-up.

Use Workflow Manager for a workspace-wide view of workflow runs.

Each run shows its timestamp, status, and who (or what) triggered it. Use Configure filters for status, date range, and workflow. Note: the runs list typically shows Completed and Failed runs (skipped runs may not appear).

Workflows is available as a Hive app. Activity (active workflows and execution runs) is limited by subscription type. Some operations — including Send an email and Post to Slack — 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 workflow 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. You can also select View runs from the main editor.

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.

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

Yes. In Workflows, choose Button is 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.