Skip to main content
Templates are ready-made workflows you copy and adapt. Open the Templates tab, or choose Create workflow → Start from a template on All workflows. It lists Hive’s built-in templates and the templates members of your workspace have saved. Search, or filter by category: Client ops, Finance, Growth, Operations and Support. Each card’s picture shows the steps the template creates.

Built-in templates

Template schedules use the Schedule trigger, which runs in UTC: 6:00 AM UTC is 7:00 AM in London during British Summer Time. To run at a local time, add a saved schedule in your timezone; it takes over from the trigger’s cadence. Every template is a normal draft once you use it: change the prompts, apps and schedule to fit. Sending a template’s starter brief unchanged on Describe also creates it, even when your workspace has no AI model configured.

Fee Reminder

Fee Reminder chases unpaid Xero invoices by email, and asks you once before any client hears from you.
  1. Overdue fee chase: a daily Schedule at 6:00 AM UTC.
  2. Find overdue invoices: an AI step reading your Xero organisation lists every unpaid sales invoice exactly 7, 14 or 21 days past its due date, with the invoice number, the contact’s name and email address, the amount due and how many days overdue it is, and counts them. An invoice whose contact has no email address is left out.
  3. Anything overdue?: a rule Condition on that count. A morning with nothing overdue stops here — no card, no email.
  4. Approve the reminders: one Approval for the whole list, showing how many clients will be emailed and the very invoices the next steps work through. You decide it in your Inbox under Needs you, because the step names no approvers and the workflow’s owner then decides. Reject ends the run; no decision within 7 days ends it as Expired.
  5. For each overdue fee: a Loop over the approved invoices, up to 50 a run.
  6. Send reminder: Outlook emails the billing contact a polite reminder naming the invoice, the amount and how overdue it is.
Once you approve, every email on that list goes out through your Outlook account with no further card, so read the list before you decide. The addresses come from Find overdue invoices, an AI step that only reads your Xero organisation and has no tools, so they count as the workflow’s own; see What agents and workflows do by themselves. The approval sits outside the loop because an approval cannot sit inside one.

Client records chaser

Client records chaser finds the clients you asked for records or information who have not sent them yet, and drafts a chaser to each for you to send. It is built for accounting practices waiting on bank statements, receipts, payroll details or VAT records, and it only needs Outlook.
  1. Weekly records check: a weekly Schedule, Mondays at 8:00 AM UTC.
  2. Find clients still waiting on records: an AI step reads your Outlook Sent folder, without changing anything, for messages sent between 5 and 90 days ago that asked a client for records, documents or information. It keeps a client only when your message was the last in the thread, is at least 5 days old, and the client has not sent what you asked for since. For each client it lists the contact’s email address, what is still missing, how many nudges you have already sent after the first request, how many days they have been waiting and a suggested chaser, and counts them. It lists at most 25 clients a week, longest waiting first; anyone left over is picked up the following Monday. Anyone with two or more nudges is marked call the client, and their draft opens with a line saying you will call. When your request gave the client a document request link, the chaser asks them to upload through that same link, copied exactly as it was.
  3. Anyone waiting?: a rule Condition on that count. A week with nobody waiting stops here, with no card and no draft.
  4. Approve the chaser drafts: one Approval for the whole list, in your Inbox under Needs you, showing the very clients the next steps work through. Reject ends the run.
  5. For each client waiting: a Loop over the approved list, up to 25 a run.
  6. Draft the chaser: Outlook’s Create draft puts a chaser addressed to the client in your Drafts folder.
Nothing is sent. Each chaser waits in your Outlook drafts for you to read, edit and send yourself, and the clients marked call the client are a reminder to phone them instead. The AI step works only from what is in your sent mail, so a request made by phone or from another mailbox is not found. The recipient and text of each draft come from what the AI step read in your mail threads, which can include replies other people wrote. Check each draft’s To address before you send it.

HubSpot templates with one approval

Email contacts to CRM and Weekly pipeline check do in bulk what Signals’ Not in your CRM and Deal slipping cards do one at a time. Each asks for a single Approval of the whole list before its loop writes anything, because an approval cannot sit inside a loop. Nothing is written to HubSpot until you approve; if you reject, the run stops. A day or week with nothing to do ends without asking you. The approval shows the very list the loop writes, and after you approve every entry on it is written, so read it before you do. Hive may suggest one of them once Signals keeps raising the same kind of card for you.

Email contacts to CRM

  1. Read the mail you sent: a Read from an app step reads up to 20 messages from your Gmail Sent folder since yesterday.
  2. Pick out the people you wrote to: an AI step lists the outside people on the To line, leaving out your own domain, shared inboxes such as info@ or billing@, and no-reply addresses.
  3. Check HubSpot for each person: HubSpot’s Find contacts by email lookup, reading only.
  4. List the people missing from HubSpot: only those HubSpot reports as not found. Anyone it found, called a possible match or could not verify is left out.
  5. Approve the new contacts: one approval showing exactly the entries the next step creates: each person’s address and, when known, first and last name.
  6. Create the contact for each person on the approved list, up to 25 a run.
HubSpot may count new contacts toward your marketing contacts.

Weekly pipeline check

  1. Read your open deals: up to 25 of your own open HubSpot deals, soonest close date first, the same deals Signals reads for you. When you use the template, Hive finds your HubSpot owner by the email address of your connected mailbox and fills it into Owner ids. If it cannot (no matching HubSpot user, or HubSpot refused the lookup), the builder’s next step asks you to enter your HubSpot owner id, and test runs and deploys are refused until you do. The step never reads every deal in the account. A copy someone else makes (a duplicate, a workspace template saved from your workflow, or an imported export) is set to their own HubSpot owner, never yours.
  2. Pick the slipping deals: an AI step picks the deals whose close date has passed or with no activity for 21 days, and proposes one fix for each: a new close date 14 days out, or a follow-up task due in 2 working days.
  3. Approve the fixes: one approval showing exactly the entries the next step writes: each deal, why it is slipping, its fix, and the new close date or the task.
  4. Update the close date or Add a follow-up task on each deal on the approved list.

Investor templates

Three templates are written for venture capital and private equity investors. Each reads only your own connected Gmail (and Google Drive for the digest) and never sends an email; every approval asks you, the workflow’s owner. Hive suggests them automatically once you connect those apps, in investor workspaces where Hive has turned that on.
  • Weekly deal-flow digest reads the last 7 days of mail, picks the founder and deal-flow threads, and lists the ones still waiting on your reply, oldest first, with what each founder wants. It adds the new decks in your Google Drive and a suggested next step for each, and ends with one in-app card. Approving the card only closes it.
  • Founder follow-up drafts finds founder threads whose last message is from the founder, 3 or more days old, with no reply from you and no draft already waiting. A run with nobody waiting stops there. Otherwise you approve the whole list once, and Hive saves each reply as a draft in its Gmail thread for you to edit and send.
  • Portfolio update tracker checks each Monday whether it is the first Monday of the month, and stops if not: workflows have no monthly schedule. On the first Monday it collects last month’s investor updates, builds a table of revenue, burn, cash, runway and headcount where the updates state them, saves it as a PDF in your Library, and flags the companies with no update.

Readiness labels

Every template whose actions your role allows is listed, with a label for anything in the way:

Suggested when you connect a second app

Once a second app is connected, Hive may put one card in Needs you titled Hive suggests a workflow, for a built-in template whose apps are connected. Fee Reminder needs Outlook and Xero. Renewal Scout needs Outlook and HubSpot. Email contacts to CRM needs Gmail and HubSpot. Meeting to Tasks needs Outlook and Jira. Ticket Triage and Weekly pipeline check need only their own app, and wait until any second app is connected. When setup has classified the firm, Hive uses that too: an advisory firm is not offered Fee Reminder, and an accounting or law firm is not offered Meeting to Tasks. A firm Hive has not classified is treated as a general firm. The card is one per template. Opening it does not create the workflow. You set it up yourself, and it still needs your approval before it writes anything. A member below Operator is not offered one, and a template you already have is not offered again.

Use a template

1

Preview a template

Select a card to open its Template preview. Nothing is created yet. The preview lists every step the template creates — each marked Needs and the app’s name when you have not connected that app — and shows the prompt it was built from under The brief Hive used.
2

Use it

Select Use template, in the preview or on the card. Hive creates a new private draft and opens it in the builder. On a Not available yet template the button reads Open as draft, and the preview says above it: “This workspace can’t run every step of this template yet. Open it as a private draft to see its steps or adapt them.” It creates the same private draft, without the setup guide. While it does, the card reads Creating your workflow… and the other cards wait, so a second click cannot make a second copy. Starting a template needs the Operator role or higher.
3

Set up accounts

Where you have exactly one account for an app, Hive fills it in for you. If a step still needs an account, the Set up guide, titled with the workflow’s name, opens, with the workflow’s steps listed beside it. Its first page lists the apps, each marked Needs an account or Account connected. Select Continue to go to the first app that needs an account, then for each app either pick an account under Select connection or, if you have none, select Connect and the app’s name, for example Connect Outlook. The app’s sign-in opens while the guide stays open, and the account choice then appears in place. Connect Outlook in Integrations is the fallback: it opens Integrations already searched for that app.
4

Check which apps it uses

When you have exactly one account for every app the template uses, the guide doesn’t open. Instead, Apps this workflow uses appears beside the builder, listing each step that uses a mail app or CRM and its account, for example Using Gmail · ann@example.com. Select Change on a step to open the guide on that app and choose another, as below. Select the X to hide the card.
5

Use a different app, if you want

If you use a different app for the same job, for example Outlook instead of Gmail, or Salesforce instead of HubSpot, select Use Outlook instead (or the app you use) on that app’s page. Hive lists the steps that will do the same thing in the other app, and any step the other app cannot do, marked Not available, which stays on the first app. Nothing changes until you select Switch to and the app’s name. The guide then shows the new app so you can pick its account. Step names and AI instructions are not rewritten, so check them in the builder afterwards. You can switch the steps back the same way.
6

Finish, or finish later

The guide goes only to the apps that still need an account, passing over the ones already set up. On each app page the forward button says what it does:Back steps through every app page in order, including the ones the guide passed over. When every app is already set up, the first page offers Finish in place of Continue.If you choose Skip setup on the first page, or Finish later, the guide closes and the builder’s next step lists each step that still needs an account. Test runs and deploys are refused until every step has one.
7

Test, then deploy

Run a test and deploy when it behaves.

Save a workflow as a template

1

Open the workflow menu

Select Save as template in the workflow menu. You need Can edit on the workflow, and it must pass the same checks as a deploy. The workflow’s description pre-fills the template description, which you can change.
2

Name it

Enter a Template name and Template description, then Next.
3

Categorise it

Choose a Template category, add Template tags, then Create template.
Saving a template needs the Operator role or higher. The template appears on Templates for everyone in your workspace who can use its steps; each starts their own copy. The Share dialog shows whether a template has been made from the workflow and links to it. Each template says who made it: by Hive for a built-in, otherwise by the member who saved it. A template Hive set up in your workspace for you (see Suggested for your workspace) also reads by Hive, never a person’s name. A workspace template can be deleted only by the member who saved it. Built-in templates cannot be deleted.

Build a workflow

Customise the draft on the canvas.

Sharing

Give teammates access to a workflow itself.

Integrations catalog

The apps templates connect to.

Use cases

Ideas by team.