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 is carried out on the account selected for it, follows that account’s Read, Draft or Act level, and passes your workspace’s safety rails. Without an Approval step, a workflow on an Act account carries out its actions by itself, unless where an action sends came from a public form, an app event, an app’s records, an AI step or a web search: then it waits for approval (see What agents and workflows do by themselves). Open Workflows in the sidebar. It opens on All workflows, where each workflow shows its status and what it needs next. Workflows you pin appear under it. Agents you build for workflows to call live in Agent Studio, its own sidebar item just above.

How a workflow is organised

  • The trigger decides what starts a run. There are five: Manual (someone presses Run live now), In-app form, Public form, Schedule and Connected app event (an event from an app the workflow’s owner connected).
  • 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. A workflow name is at most 120 characters: the name fields stop there. If a draft goes over either graph limit, or its name over 120 characters, the save chip names the limit instead of saving. A workflow that has not been saved yet shows the same reason in a message. The draft saves again once it is back within the limits.
The triggers and steps reference lists every type and its settings.

The tabs

Beside the tabs, the Runs recorded chip counts the finished production runs of the workflows you can see, for example Runs recorded · 48. It is not a limit: workflows draw AI credits inside each workflow’s credit limits, and on Business each member’s workflow runs are in Settings → My usage. The chip is hidden on All workflows, which leads with where your workflows stand instead — see What the list says at the top — and, with the tabs, while a workflow is open. Owners and Admins see the workspace’s credits under Settings → Billing.

What the list says at the top

All workflows opens with one line: how many workflows you can see and how many are live, for example 6 workflows, none live. When some of them are waiting on an app account you have not connected, a second sentence names the one account that frees the most of them — Connecting Outlook unblocks 5. — with a Connect Outlook button that opens Integrations on that app. It is the only place the list offers that button. Each row still names the account it is waiting for, in its own words.

What each row tells you

Each row leads with the workflow’s name. Under it sits the workflow’s chain: its trigger, then one mark for every step, in the order a run walks them. A step that acts in a connected app wears that app’s logo; a step of Hive’s own — a form, a condition, an agent with no account pinned to it — is a plain mark. A step that cannot run yet is outlined in amber, where it sits in the chain, so you can see how far a run would get. A step you have disabled fades, because it is skipped rather than broken. Beside the chain, the row says what the workflow needs next. Where that is an account to connect, the sentence is a link that opens Integrations on it: A live or paused workflow is marked as such beside its name. A draft carries no mark: it is the state a workflow starts in, the line at the top of the list already counts them, and the row’s next step says what it is waiting for. At the quiet right-hand end, each row gives its owner, its run counts, and one date — when it last ran, or when it was last edited if it has never run. A workflow’s model cost appears there too, once it has one. The status filter above the list reads All, Draft, Live and Paused. Search matches a workflow’s name, trigger, description, status and owner. A workflow you started from Ask for something that happens every time (“every time HMRC emails, summarise and file it”) shows From Signals: and your words under its name. When you have any, Started from Ask beside the status filter lists only those. See Something that happens every time.

Create a workflow

Select Create workflow above the list. A workspace with no workflows yet shows the same choice straight away. Pick one of three ways to start: Import a workflow, under the cards, loads a workflow someone exported. The line under the cards, Trigger → Steps → Test run → Deploy, is the order every workflow follows. Creating a workflow needs the Operator role or higher; without it, only Start from a template stays open, so you can still browse.

Runs and cost in the list

All workflows counts the runs you can see: your own, or every member’s if you are a workspace admin. They sit at the quiet right-hand end of each row. So a workflow you have only test-run shows 0 · 3 test with a run date and a model cost.

Draft, live and paused

A workflow is always in one of three states: Editing never touches what is live. Changes saved from Ask or through the API stay in the draft too, so a live workflow’s schedules, forms, app events and Run live now keep using the deployed release until you deploy again, and a paused workflow stays paused. This holds for every workflow deployed with a current release, which is every workflow you deploy now. An older deployment that has no current release (it went live before Hive kept a ready-to-run copy of each release) runs whatever its draft says, so a change that alters what a run does takes it back to Draft instead; deploy it again to put it live with a release. Renames, descriptions and moving steps on the canvas never change its status. Hive describes a live or paused workflow by its deployed release, because that is what runs, in Brain → Automations, Ask, the accounts Run live now asks you to choose, the steps named on the Audit page and Settings → Scheduled. The builder, and the steps on the workflow’s row in your Workflows list, show your draft. The builder autosaves your draft; Deploy turns it into a release: a frozen copy of the workflow with a version number such as 1.2.0. “Release” and “version” mean the same thing in Hive. Past versions lets you re-activate an earlier one. You pause and resume a live workflow with Pause or Resume in the builder header, or from the Live status section of the Deploy dialog. See Test and deploy. While your draft has changes that are not deployed, people who can manage the workflow see Draft differs from live beside the Live or Paused pill. Schedules, forms, app events and Run live now keep using the deployed release until you deploy again. That includes the connected account a step uses: switching a step to another account changes the draft, and live runs keep using the account the release was deployed with. If the workflow changes somewhere else while you have it open (in another tab, by another editor, or by an AI client through the MCP server), the builder stops autosaving and a bar says it changed in another session instead of overwriting the newer version. The bar names the steps that differ. Select Reload latest to discard your edits and load the newer version, or Keep mine (replaces the other version) to send your draft over it.

Test runs and production runs

Test run in the builder header, and Test run from here and Test run this step only on each card, always start a test run of your draft: nothing is sent to other apps. Run live now in the builder header starts a production run of the live release once you confirm it.
  • 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 live now on a live manual, scheduled or in-app form workflow, a schedule, a form submission, an event from a connected app, or a teammate running a workflow shared with them. Before Run live now, Run with my accounts or a schedule’s Run now starts one, a confirmation lists the actions it takes in other apps. Actions are carried out within your workspace’s safety rails, and one whose recipient, channel, number or link came from somewhere the workflow does not trust waits for approval (see When an action waits for approval). See Run live now.
Past runs, in the dock under the canvas, lists both, labelled Test or Production.

The builder at a glance

  • Header: one row with Workflows (back to the list), the workflow name, its status and save chip, the next step, and its buttons — see The builder header.
  • Next step: a button in the header that says what to do next, or how many things are left to set up. Select it for the action that moves the workflow on and the setup checklist — see The next step.
  • Canvas: cards for the trigger and each step — see The canvas.
  • Step settings: select a card to edit it. The step’s name heads its settings, with what kind of step it is and what it runs after under it; its connection and fields follow, then Error handling. The ⋯ menu beside the name holds Replace step, Duplicate, Deactivate step, Open in a larger editor and Delete. See Step settings.
  • Dock: Add (the step library, headed Add step), Past runs and Settings. Beside it sit undo and redo, zoom, Fit canvas, Auto-arrange and Help.
  • Chat: the workflow assistant, which proposes changes you apply or dismiss. Where your workspace allows it, pick the model it drafts on from the model picker in the chat (Which model drafts).
While a workflow is open, Hive’s sidebar folds to its icons so the canvas has the room. Open it again and it stays open on workflow pages until you close the browser tab, without changing how the sidebar opens anywhere else. Hover over or focus a button to see a short tip saying what it does; on a touch screen, tap it. A greyed-out control’s tip says why it is unavailable. Where a setting needs a longer explanation, select the (i) button beside its label to read it; select it again, click elsewhere or press Escape to close it. On a phone, the header puts the workflow name on its own line with its buttons below it, and the dock shows Add, Past runs and Settings as icons. On a phone or touch screen, when the canvas is zoomed out below 50%, tapping anywhere on a card selects it and opens its settings; the card’s own small buttons work again once you zoom in.

The builder header

The header is one row: Workflows, which takes you back to the list, then the workflow’s name, its status, the save chip and the next step, then its buttons. Deploy is the header’s one main button: it makes your draft the version that runs. The other buttons sit beside it as quieter ones.

The canvas

A workflow opens at a readable zoom (75% or more on a computer), with the trigger at the left. Pan to see the rest, or select Fit canvas to see the whole graph at once. Phones and tablets open on the whole graph. A step’s name holds the same size on screen as you zoom out, rather than shrinking with the canvas, so it stays readable; past 100% it grows with everything else. A long name is cut with an ellipsis when the card has no room for it — the step’s settings always show it in full. A card shows its step’s first setting, and every tool an agent carries; select the card to see the rest in its settings. Below about 65% zoom each card shows an overview — its icon, the kind of step it is and its name — and a warning triangle where a step needs attention. Its first setting and its Input / Output tabs come back as soon as you zoom past that, so Fit canvas gives you the shape of the whole workflow and the detail is one zoom away. On a phone the whole of a six-step workflow is about a seventh of its full size, which is too small for any step’s name to be read. The step’s icon is drawn larger to make up for it, so you can still tell a Zendesk action from an agent or a loop and tap the one you want: tapping a card at that size opens its settings full screen. Pinch to zoom in when you want to read the canvas itself. A tablet shows both the names and the icons.
  • A short line above each card’s name says what kind of step it is, for example Trigger · Schedule, Agent or Action · Zendesk. A new workflow starts with a Trigger · Manual card; change its Trigger kind to start it from a form, a schedule or an app event instead.
  • Each card has Test run from here and Test run this step only, and a step menu with Rename, Deactivate step, Replace step and more.
  • The + after the last step is always visible. While a workflow has one or two steps it reads Add step. Hover over a connection between two steps to show a + that inserts a step there.
  • A step that can’t run where it would go is greyed out in the step library, the + menu and the Replace step picker, with the reason and what to do instead. For example, an Approval is greyed out inside a loop: move it before or after the loop.
  • A rule condition’s two paths are labelled Yes and No; an AI condition’s paths keep their numbered conditions and Else. Each path with no step after it has its own +, which adds a step on that path. Hover over it, or focus it, and its tip says what happens meanwhile, for example No step on the No path — runs that take it end here.
  • Steps inside a loop sit on a tinted backdrop labelled Repeats for each and the loop’s name for each item. They run once for every item in the list.
  • To connect two steps, drag from a card’s connection dot to another step, or click the dot and then click the step.
Help in the dock opens Workflow help. It links to four guides — Workflow builder (this page), Build a workflow (the Build your first workflow tutorial), Triggers and steps and Test and deploy — then lists Shortcuts & gestures: These act on the canvas when it has focus; keys pressed inside a step’s menu stay in that menu and never change or remove steps. In a step’s ⋯ menu and its run options menu, the arrow keys, Home and End move between the items, and Esc closes the menu and returns you to the button that opened it. Under them, three terms are explained: Test run tries your draft and sends nothing to other apps, Run live now runs the deployed version for real, and Deploy makes your draft the version that runs.

The next step

The next step button in the builder header always answers “what now?”. While the setup checklist has something left to do, it counts it, for example 3 things to set up; otherwise it says where the workflow stands. Select it to open, over the canvas, what it says, the button that moves the workflow on, and the setup checklist. It never opens by itself, so the canvas keeps its full height. It checks, in this order, and shows the first that applies: If you can view the workflow but not edit it, the next step still says where it stands but offers no editing action.

Setup checklist

While anything needs doing, the next step’s panel lists five areas, each marked done, to fix, or worth a look (something to check that does not stop the workflow running), and its button counts the areas not done yet:
  • Accounts connected
  • Steps connected to the flow
  • Every step filled in
  • Values from earlier steps found
  • Every step can run in this workspace
Under each area, every problem has Fix, which opens the step on the setting to change, or Show, which selects the step on the canvas. A connected-app trigger on an app you have not connected is listed too, for example “Connect Slack so “New message” can start this workflow.” Steps connected to the flow also lists a step placed where it can’t run, such as an approval inside a loop, with Show. If Hive refuses a test run or a deploy, the reason stays in a row under the header in plain words, with Show step to open the step it concerns, until you dismiss it.

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. Creating a workflow (including from a template or an import), running one and creating a schedule need the Operator role or higher and a Basic, Pro or Max seat. Deploying or pausing needs Can edit on the workflow. See Sharing and Roles and permissions.
New to workflows? Start with a built-in template such as Fee Reminder or Ticket Triage, test it, then change it to fit.

Your first workflow

Build a meeting recap workflow, step by step.

Build a workflow

Describe a workflow, add steps and set them up.

Triggers and steps

The complete step reference.

Test and deploy

Test runs, releases and versions.

Templates

Start from a ready-made workflow.