Start from a brief
1
Open the Describe tab
Open Workflows, then Describe (or Create workflow → Describe it).
2
Describe what should happen
Write what starts the workflow, what it should do and which apps it uses, for example “When a
signed engagement letter lands in DocuSign…”. Or pick a starter brief below the box. Select an
app under Your connected apps to build with it. While you have no app connected yet, a few
common apps appear under Connect an app: select one to connect it. If your description names
an app you have not connected, the note under the box offers Connect and the app’s name. See
Connect an app from Describe.
3
Generate the draft
Press Enter, or select the send button (Generate workflow). Shift+Enter starts a new
line instead. The
workflow assistant lays out the steps with your connected apps
and opens the new draft in the Builder. If a step’s app has more than one of your accounts,
the Set up guide asks which one to use.
Start from a template
Open Templates and select a card, or Preview it first and choose Use template. Hive makes a new private draft; the template itself is unchanged. If a step still needs an account, the Set up guide asks which account each app should use. A template labelled Connect and app names still makes a draft: the guide lets you connect those apps there and then, and test runs and deploys wait until you have. A template labelled Not available yet offers Open as draft instead: it makes a draft you can look through or adapt, without the guide, because this workspace can’t run every step of it yet. See Templates.Start blank
Choose Create workflow → Build step by step, or select New workflow in the builder header. The header shows no save chip until the draft is saved as a real workflow, the first time you add a step or describe it in the chat.Add steps
A workflow has one trigger, the first card, and any number of steps after it. To add a step:- select the + after the last card (it reads Add step while the workflow has one or two steps);
- hover a connection and select the + at its middle to insert a step between two cards;
- select the + on an open Yes or No path of a condition to add the step on that path (see Add a step on a branch); or
- select Add in the dock under the canvas to browse every step in a side panel.
Select a section’s chip to show only that section, and select it again to show all three. Each step
has a one-line description, such as “Let AI decide which way the workflow goes” for Condition
and “Go one way or another based on a rule, e.g. amount over 1,000” for If / else (rule).
Apps is filled from the apps you have connected: an app’s steps appear only once one of its
accounts is connected. With no app connected, Apps moves to the
bottom, suggests a few apps to connect, and links Connect an app; otherwise Connect another
app under the list opens Integrations. The Add step side panel lists the same steps under
the same three headings. Each app there is one row showing how many steps it offers; select the app
to open its list, and select it again to close it. Searching opens every app that has a matching
step. Below the list, Let Hive build it → Draft a workflow with Hive opens the
workflow assistant instead.
A workflow runs from exactly one trigger, so neither list offers a trigger once the workflow has
one. To change what starts it, change Trigger kind on the trigger card instead.
Search in everyday words
Search matches each step’s name, its description and everyday words for it, soif finds
If / else (rule) and Condition, repeat finds Loop, delay finds Wait, approve
finds Approval and summarise finds Hive agent. Every word you type must match, in any
order, so slack message finds Slack’s Post message. The closest matches come first. In the
picker, press Down to move from the search box into the list and Up and Down to move
between rows; Enter in the search box adds the top match.
When nothing matches, the picker offers Connect an app for “…”, which opens Integrations
already searched for what you typed: the step you want may be one an app offers once connected.
Actions on read-only accounts
A read changes nothing, so it is never marked; see Read from an app. An app whose every connected account is on the Read level is marked Read-only account beside its actions. You can still add them, but on Read — or under a Read only workspace ceiling — the step takes no action when the workflow runs and fails with the reason; on Draft each action waits for approval, and on Act it runs. Your workspace’s safety rails, such as the kill switch and spend caps, can still stop one, and an action whose recipient, channel, number or link came from a public form, an app event, an app’s records, an AI step or a web search waits for approval (see When an action waits for approval and What agents and workflows do by themselves). To have a person sign off before an action runs, add an Approval step before it.After you add a step
The step reference describes every type. A new step opens with its settings showing, and “Step added. Fill in its settings, then test it.” appears over the canvas. A warning chip on a card names any required field still empty. A step added after another starts filled in from what that step produces: an agent’s prompt lists the values to work on, an Output or Create PDF holds the previous step’s result, and a Loop runs over the one list the step before returns. A second step of the same kind is numbered, such as Wait 2. See New steps start filled in. To swap a step for a different one, choose Replace step from the card’s menu: the same picker opens, titled Replace step.Add a step on a branch
A rule condition’s paths are labelled Yes and No; an AI condition’s paths are its numbered conditions, plus Else. Each path with no step on it has its own + (“Add a step on the No path of …”), which adds the new step on that path. You can leave a path empty: a run that takes it ends there. Hover over or focus that + and its tip says so, for example No step on the No path — runs that take it end here. Adding after a loop, or after a step inside one, names where the step goes, for example “Continue from For each invoice — runs once per invoice”: a step inside a loop runs once for every item.Delete a step that others read
Deleting a step reconnects the cards around it. If a later step still reads its values, Hive says so as it deletes it, for example: Deleted “Look up client”. “Draft reply” still uses its values — press Undo to bring it back. Select Undo on the canvas controls to restore the step, or pick a new value in the step that read it.Step settings
Select a card to open its settings beside the canvas. They are headed by the step’s name, which you edit right there: it is required and up to 120 characters. If you clear it, the box says so, and leaving it puts the last name back. Renaming a step on the canvas (double-click its title, or Rename in its menu) stops at 120 characters too, and says so under the title. Under the name, a line says what kind of step it is and what it runs after, for example “Action · Zendesk, after For each ticket”, or that nothing leads into it yet. Then, from top to bottom:- Connection for a step that acts through one of your app accounts: an app step, and a step that sends a message, a direct message or an email. Choose Select connection to clear an account you set; an account a teammate set, which you cannot see, is kept when you save. See Choose the account a step uses.
- The app’s fields, then the step’s own settings, with what you most need first: an agent’s Prompt leads, and its Read-only data sources come after it. A Fields box appears only for settings no other control shows. Each step type’s settings are in the step reference.
- Error handling, with the step’s On error choice.
- Replace step swaps it for a different step, from the same picker as Add step.
- Duplicate adds a copy of it.
- Deactivate step keeps it on the canvas but skips it when the workflow runs; Activate step turns it back on. The trigger has no such switch.
- Open in a larger editor opens the step’s settings in a larger window, which also says what the step runs after, has its name as a Step title box, and has Disable step, Duplicate step and Delete step at its foot. People who can only view the workflow can open it too, read-only, with its buttons greyed out.
- Delete removes it.
Choose the account a step uses
A step that posts, sends or writes for you does it through one of your connected accounts, and you choose which one in its Connection setting:- A message step (
send_message) and a direct-message step (send_dm) post through Slack. - An email step (
send_email) sends through Gmail only. To send from Outlook, use Outlook’s own Send email step from the Apps section of Add step. - An app step acts through the app it names.
- Any other step that acts in an app works the same way: a refund or charge retry through Stripe, revoking access through Okta, or pausing a campaign through Google Ads.
{{…}} value, an @here, @channel,
@everyone or user-group ping in it shows as plain text too; see
Action.
A Slack Read channel history or Read thread step, under Read from an app, has the same
Channel picker: choose the Slack account, then search for the channel to read. It lists only
channels, never people.
A run uses the published version of the workflow, so after you change a step’s account,
deploy again for runs to use it.
Configure the trigger
Select the trigger card and choose one of five triggers: Manual, In-app form, Public form, Schedule or Connected app event. For a form, add a title and its fields. A Connected app event trigger needs an app you connected in Integrations first, and a plan that includes app events (Business or Team): during the trial and on Starter the picker says it is not included. See Triggers.Connect and arrange
- Drag a card to move it, drag empty canvas to pan. Hold Shift, Ctrl or Cmd to select several cards, then move or delete them together.
- Drag from a card’s connection port onto another card to connect them, or select the port and then the card. Hive refuses a connection that would create a cycle and says why.
- To remove a connection, hover it and select the small × beside its +. On a touch screen or in a narrow window, both buttons are larger and stay visible without hovering.
- A rule condition has Yes and No branches; an AI condition has one path per condition, plus Else when Force AI to select a path is off.
- Deleting a step reconnects the cards around it. The trigger cannot be deleted or duplicated.
- Undo, Redo, zoom, Fit canvas and Fullscreen sit on the canvas controls.
Pass values between steps
A step can use what earlier steps produced, such as a form answer or an agent’s draft. Write what an AI step should do in its prompt: the values a run fills in reach the AI as data, so an instruction inside a form answer or an earlier step’s answer is not followed (see Run data reaches the AI as data). In a prompt, message or app field, a value from an earlier step shows as a pill: the value’s name with its step’s mark, such as Company name. To add one, press @, select + Value in the field’s corner, or type{{:
- Values are grouped by step. Each shows its name and its type in plain words: Text, Number, Yes/no, List or Group.
- Keep typing to narrow the list. Use the arrow keys and Enter, or click, to insert a value; Enter takes the best match. Escape closes the list.
- Insert a value from an earlier step (N) under the field lists the same values, name first, and may put the most likely one first. In a one-line field, lists and groups sit apart under Lists and groups.
{{step.field}} placeholder, such as {{intake.company}}.
That is what an export contains, and how the
step reference names the values each step produces.
Settings that take a single value have a picker instead: Value to check on an If / else
(rule), List to go through on a Loop, Insert an earlier
result on an Approval and Replace with an earlier result on an Output. The pickers group
values under each step’s name, for example Invoice number · Text. Form fields are listed by
their label, and steps inside a loop are offered only within that loop.
If you rename or remove a field of an agent’s structured output that a later step reads, Hive names
that step, for example ““Create draft” uses this field. Update it there too.” Removing it asks once
more: Remove anyway or Keep it. See
Passing values between steps.
Saving
The builder saves the draft automatically a moment after each edit and shows the status in the header. If the workflow changed in another session, Hive keeps your local edits and asks: Reload latest or Keep editing.The workflow menu
Beside the workflow name:
An import always creates a new private draft. It keeps a step’s account choice only when that
account is one of your own connected accounts, so re-importing your own export keeps your choices.
Any other step is linked to your account only when you have exactly one connected account for its
app. Hive lists what it left open, such as steps where you still need to choose or connect an
account.
Next: test it
Run the draft from any card with Test run from here or Test run this step only. These buttons always start a test run, which never sends anything. When it behaves, deploy it.Related
Triggers and steps
Every step type and setting.
Test and deploy
Test runs, releases and rollback.
Workflow assistant
Draft and change workflows in chat.
Templates
Ready-made starting points.