Skip to main content
A workflow is a repeatable process Hive runs for you: one trigger, then a chain of steps. A step can ask an AI agent to draft or research, branch on a condition, loop over a list, wait, act in a connected app, or save a PDF to your Library. Every action a workflow takes passes the same approval and safety policy as anything else Hive does. Open Workflows in the sidebar. Workflows you pin appear under it.

​
How a workflow is organised

  • The trigger decides what starts a run: someone pressing Run, a form submission (in-app or public) or a schedule.
  • Steps do the work and pass values to each other with placeholders such as {{trigger.email}}.
  • A graph holds up to 50 cards and 100 connections. It has exactly one trigger, no cycles and no unreachable steps.
The triggers and steps reference lists every type and its settings.

​
The tabs

Beside the tabs, the Pulse chip shows how many workflow runs your workspace has used this billing period against its allowance, for example Pulse · 320 / 2,500 runs. If the allowance cannot be read, it shows the total runs recorded instead.

​
Draft, live and paused

A workflow is always in one of three states: Editing never touches what is live. The builder autosaves your draft; Deploy turns it into an immutable release such as 1.2.0, and Past versions lets you re-activate an earlier one. See Test and deploy.

​
Test runs and production runs

  • A test run runs the current draft. Models run for real, but every action is recorded as what it would have done and never sent.
  • A production run runs the live release. It starts from Run now on a live manual workflow, a schedule, a form submission, or a teammate running a workflow shared with them. Actions go through your workspace’s approvals.
Past runs, in the dock under the canvas, lists both, labelled Test or Production.

​
The builder at a glance

  • Header: the workflow name and menu, save status, Form link (for a live public form), Fill in form (for a live in-app form), Run now (for a live manual workflow), Deploy and Share.
  • Canvas: cards for the trigger and each step. Each card has Run workflow from here and Run this node only, and a menu to duplicate, comment or deactivate it.
  • Dock: Add step, Past runs, settings and help.
  • Chat: the workflow assistant, which proposes changes you apply or dismiss.

​
Who can do what

A workflow is private to the member who created it until they share it with named teammates as Can view, Can run or Can edit. There is no workspace-wide sharing. Running any workflow needs the Operator role or higher. See Sharing.
New to workflows? Start with a built-in template such as Fee Reminder or Ticket Triage, test it, then change it to fit.

Build a workflow

Your first workflow, step by step.

Triggers and steps

The complete step reference.

Test and deploy

Test runs, releases and versions.

Templates

Start from a ready-made workflow.