Before you start
- You need the Operator role or higher to create and run workflows. See Roles and permissions.
- The agent step needs an AI model, and the builder’s next step is where it says so: select the next step in the builder header. If it says Testing needs an AI model, which this workspace doesn’t have — ask an admin, your workspace cannot run agent steps yet: test runs and deploys are refused. If its setup checklist lists This workspace has no AI model set up, so its AI steps return placeholder text, the workflow runs, but the recap is placeholder text rather than a real answer.
- Test runs are real runs: the agent’s model calls use your AI credits (on an earlier plan, the workspace’s pool), and count toward the workflow’s monthly credit limit. They do not count as workflow runs.
1. Start a blank workflow
Open Workflows. On All workflows, select Create workflow, then Build step by step. (The same choice offers Describe it, Start from a template and Import a workflow.) The builder opens with one card already on the canvas: the workflow’s trigger, labelled Trigger · Manual, with its settings open beside it. Every workflow starts from exactly one trigger, so you choose what kind it is rather than adding one. Until you add a step, the next step in the header offers Add first step or Describe it to Hive. The workflow saves itself with its first step, and from then on the save chip in the header reads Saved after each change.2. Make the trigger a form
1
Choose the trigger kind
The trigger card is selected and its settings are open beside the canvas. Under Trigger, set
Trigger kind to In-app form (“A signed-in teammate submits it”). The card’s label
changes to Trigger · In-app form.
2
Name the form
A new form takes the workflow’s name as its title, or “Workflow form” while the workflow is
unnamed. Set Form title to
Meeting finished. This is the heading your teammates see when
they fill it in.3
Set up the fields
The form starts with one field, Field 1, shown as a short row. Select the row to open it,
change its Label to
Meeting title and leave its Type as Short text. Under Add a
field, select Other field; the new field opens straight away. Change its Label to
Transcript and set its Type to Long text. Leave Required on for both. A dot on a
row marks a required field, and the ⋯ menu beside it moves or removes the field.field_1 and the second field_2. An open field shows its key as Reference name; select
the (i) beside it for how later steps read it. You rarely need to type these: Hive fills them
in or lists them by label for you.
3. Add the agent
1
Add a Hive agent
Select Add in the dock to open the Add step list, and choose Hive agent under
AI. Each step you add from the dock is appended to the end of the workflow and connected to
the step before it. (You can also use the Add step button after the trigger on the canvas.)
2
Write the prompt
The Prompt starts with a general instruction followed by the form’s values, one per line,
because Hive fills a new step in from the step before it. Replace the instruction and keep the
value lines, for example:In the prompt, the two values show as pills, Meeting title and Transcript; the text
above is what the prompt holds behind them.
3
Insert a value if you need one
If you removed a value line, place your cursor in the prompt and press @ to pick Meeting
title or Transcript from the list of earlier values, or open Insert a value from an
earlier step under the prompt and select one there.
{{hive-agent.text}}.
4. File the recap as a PDF
1
Add a Create PDF step
Select Add and choose Create PDF under Logic & tools.
2
Title the document
Set Document title to
Meeting recap: and then insert Meeting title with Insert a
value from an earlier step, giving Meeting recap: followed by a Meeting title pill. The
title stays on one line; it names the file and heads its first page.3
Check the body
Document body already holds the agent’s Answer, as a pill, because the step was added
after the agent. The body is Markdown, so the agent’s headings and bullets carry into the PDF.
4
Choose a folder
Leave Folder on Library (no folder), or pick one of your Library folders.
5. Record a notification
Select Add and choose Internal notification under Logic & tools. Set Channel to a name your team uses, such asmeetings; it only labels the note, and no connected channel is needed. In
Message, type Recap filed in the Library: , then press @ and pick The PDF’s file name
under Create PDF. Behind the pill, the message holds:
6. Test the draft
Every test run is a test of the draft, and nothing is sent to other apps. You do not need to deploy first.1
Open the Test tab
Select Test run in the builder header (or Try the form under the next step there).
Because a form starts this workflow, the form’s Test tab opens so you can enter sample
answers.
2
Choose Full flow
The scope menu at the top shows Full flow, which runs every step. (Trigger only checks
just the form.)
3
Fill in sample values
With Fill form selected, type a meeting title and paste a short transcript.
4
Run it
Select Test run full flow. When the agent finishes, its card’s Output tab shows what the agent
returned, with the recap in its
text field.7. Read the run in Past runs
Select Past runs in the dock and choose your run. The summary line reads Started, followed by the time, Test, the duration and the run’s cost in GBP. Below it, each step has its own row with its status, a detail line and its cost:- a row for the trigger, the form that started the run;
- the Hive agent and Create PDF rows show that they completed, and the agent’s row opens with the start of its answer;
- the Internal notification row reads Not sent: this was a test run, with a Would have sent box showing the note it would have recorded.
8. Deploy
Deploying makes a numbered release of the draft and puts it live.1
Open Deploy
Select Deploy in the builder header (or under the next step there, which now says Ready
to go live).
2
Check the version
New version: shows the number the release will get. Patch is chosen for you, so a first
deploy becomes
v0.0.1. To pick Minor or Major instead, open Version number.3
Describe and confirm
Optionally enter a Deploy description, such as
First release; left empty, a first deploy
is recorded as “First version”. Then select Confirm deploy.9. Run it for real
1
Fill in the live form
Select Run live now in the builder header, or Fill in form on the workflow’s row in
All workflows. The Meeting finished form opens, marked as a live run.
2
Submit
Enter a real meeting title and transcript, then select Submit form. This is a production run
of the live release, and it runs as you. The form shows the run’s progress as soon as it
starts, and says when it has finished or which step failed.
3
Open the run
Select Open in Past runs. The summary line now reads Production, and every row shows
that its step completed.
10. Open the PDF in the Library
Open Library in the sidebar. The new PDF, named after your Document title, is at the top of Recent files (or in the folder you picked). Select it to open the recap. See Library.Add a connected app
Once the workflow works, you can make it act in your own apps. For example, add an Outlook step that drafts the recap as an email.1
Connect your account
Connect your Outlook account in Integrations. See
Connect an app. Each person connects their own account. A run you start
with Fill in form uses your accounts; a saved schedule’s run uses the accounts of the
member who created it, and a public-form run uses the workflow owner’s.
2
Add a recipient field
Select the trigger card and, in its settings, select Email under Add a field. Then
select the new row and change its Label to
Send recap to.3
Add the Outlook step
Select Add and, under Apps, choose Outlook: create draft message. The + on the
canvas opens the same Add step list. An app’s steps appear only once you have connected it;
with no app connected, Apps offers Connect an app instead.
4
Fill in the fields
Under Connection, choose your Outlook account if Hive has not chosen it already. Set
Subject to
Meeting recap: followed by the Meeting title value, Body to the
agent’s Answer, and To Recipients to the new Send recap to field
({{trigger.email}} behind its pill). Press @ in a field, or select + Value, to pick
each value. To Recipients is a list field: it takes one entry per line, and Insert a
value from an earlier step under it adds Send recap to on a line of its own.5
Check the body length
Outlook drafts are plain text, so the agent’s Markdown headings and bullets appear as raw
#
and - characters. Body takes at most 4,000 characters, and a longer recap fails the step.
For long meetings, ask the agent for a shorter recap (under 4,000 characters), or point readers
to the PDF by name, such as Full recap in the Hive Library: followed by The PDF’s file
name.- In a test run the step is held back, like every action in a test: nothing reaches Outlook, and Past runs shows Not sent: this was a test run with the draft it Would have sent.
- In a production run the draft is created in Outlook straight away when your Outlook account is on Act, and the step records it. On Draft it waits for your approval first, and on Read it is not created. The workspace’s kill switch and action limits can still stop it; the step then says why the draft was not created.
- When a teammate uses Fill in form, the run is theirs: each app step must use their own connected account. If they have not connected Outlook, the run is refused and asks them to choose their own account. See Share and reuse.
This step follows your Outlook account’s Read, Draft or Act level, the same level Ask
and Signals use, with any workspace ceiling on Outlook applied. If the account is on Read, or a
Read only ceiling caps Outlook, the step fails with “Not run: the account is set to Read, so
Hive only reports what it found”. Set the account to Act for the draft to be created straight
away, or to Draft to approve each one. See
Accounts and autonomy.
Related
Build a workflow
Every way to start, add and connect steps.
Triggers and steps
The complete step reference.
Test and deploy
Test runs, releases and rollback.
Schedules and public forms
Start runs automatically or from outside Hive.