Skip to main content
Your inbox and calendar are where commitments hide. Connect them and Hive notices the email that has been waiting on you, the client who has gone quiet, and the meeting that needs a follow-up — and prepares the next step for your approval or takes it, as your account’s Read, Draft or Act level allows.
In Ask and Signals, your account’s Read, Draft or Act level decides whether Hive only tells you what it found, prepares the action for your one-click approval, or takes it and tells you what it did. New accounts start on Act. Act never skips Hive’s safety checks: an action Hive cannot undo — sending, replying to or forwarding an email, or creating, changing or cancelling a meeting, for example — still comes to you as an approval card. Agents and workflows follow the same level for the actions selected for them (straight away on Act, after approval on Draft, never on Read), and even on Act an email or invitation whose recipient did not come from the agent’s instructions, the workflow’s own steps or words you typed in Hive waits for your approval. To pause a workflow for a person, add an Approval step. See Accounts and autonomy. Hive will never turn a request for a draft into a sent email.
Hive’s direct reads of these apps work in Ask, in workflow Hive agent steps and as Read from an app workflow steps. Each one is listed in Reads in workflows.

First sync

Hive starts reading a new Gmail or Outlook mailbox as soon as you connect it, instead of waiting for the hourly sync. It reads up to a year of mail; for Gmail, that first read stops at the newest 5,000 messages. A large mailbox can take several runs; on Ask, Getting your data ready shows progress, and after the first catch-up new mail arrives on the hourly sync. That year of mail is for Ask and the Business Brain: Signals raises nothing from mail dated more than 4 weeks ago. See How Signals reads your accounts.

Email signals

For Gmail and Outlook, Hive runs two built-in mail detectors:
  • Awaiting reply — the last message in a thread came from someone else, and you have not answered. Mail nobody expects an answer to is skipped: no-reply and notification senders (including no_reply@ and alerts-notifications@), automated shop and account senders such as auto-confirm@, shipment-tracking@, order-update@, account-update@ and store-news@, service desks such as support@, customerservice@ and members@, mail sent from a mailing platform’s address (such as news.example.com or em.example.co.uk), mail its own headers mark as a mailing list or automatic message (on any of that sender’s messages in the thread, not only the latest), mail sent through an email service such as Amazon SES, SendGrid, Mailgun, Mailchimp or Postmark or from a bounce address, mail relayed for another organisation (a Sender at another company, or a carrier sending under the shop’s name from a notification address such as notify.carrier.example; a name alone that differs from the address is never enough, because it may be a nickname), newsletters or mailings with an unsubscribe link in their footer or an unsubscribe address in their headers, calendar invitations and RSVPs (answered in the calendar, not by email), and account notices such as receipts, statements, password and security alerts, welcome and order confirmations. Mail from info@, team@ or hello@ is still treated as a person, because small firms and investors write from those, and so is an address such as notify.example.com or claims.example.com unless the message’s headers also show it was machine-sent. Someone you correspond with is never skipped by these sender rules: anyone you have written to, or who answered you in the thread, is treated as a person whatever address they write from, unless it is a no-reply address. Automatic replies, such as an out-of-office message or a help desk’s “we received your request”, are never a wait, whoever sends them. A reply or forward in a thread is always treated as a conversation. Mail you wrote yourself is never a wait: a message from any mailbox you connected to Hive, or one Gmail or Outlook filed as sent from your mailbox (such as mail from an alias), counts as yours. Mail you were only copied on is skipped too: a thread none of your addresses wrote in or was a direct To recipient of, because you were on Cc or Bcc or it reached you through a group or forwarding address (see Mail you were only copied on). Personal and consumer mail is skipped as well, even from someone you have written to: a shop about an order or a parcel, an airline or travel company about a flight or booking, a utility about a bill or a meter reading, a doctor, dentist or clinic about an appointment or results, and a bank about a mortgage, loan or account. Hive reads the message’s own words for this, and keeps the signal when they show your firm’s work, such as a client’s claim, a contract or a purchase order. Mail about health, money, family or a personal legal matter is skipped only when it comes from a bank, an insurer, a clinic, a council or a similar institution, so a client who writes about their own custody, visa or mortgage still raises a signal. An open signal on mail that falls under these rules closes on its own. You get one new Awaiting reply per person: when the same person is waiting in several threads, or in several of your mailboxes, Hive opens a card for their longest wait only, and none while a card for them is already open.
  • Went quiet — you have followed up (written into the thread at least twice since their last message) and the other person has not replied for at least three days. Chasing a shop, an airline, a utility, a clinic or a bank about your own order, booking, bill or appointment is personal mail and raises no Went quiet.
Where Signals keeps your matters, these detectors defer to what your matters show:
  • Quiet on concluded threads. Awaiting reply stays quiet on a thread Hive has filed under one of your matters as done or dormant, or as waiting on the other side, but only when Hive has read the thread as it stands now, read every message of the wait in full, none of those messages asks a question, and the wait is five messages or fewer. Went quiet stays quiet only on a done or dormant matter: it keeps chasing when the matter is waiting on the other side. Hive never raises a mail signal because of its own reading, and an open signal stays open until you or they reply, or you dismiss it.
  • One thread, one prepared mail. While a matter’s Reply owed or Follow-up due card on a thread still waits for you, Awaiting reply and Went quiet do not raise a second signal for that thread. Once you have approved, declined, snoozed or muted that card, or when the matter links more than one email thread, they raise as usual. When an Awaiting reply or Went quiet signal is already open, Hive files it under the matter instead of raising Reply owed or Follow-up due. On an Act account this means at most one reply is sent per thread.
  • Grouped under the matter. A mail signal on a thread one of your matters links shows under that matter.
Only your own matters are read for this. Hive can prepare a draft reply alongside the signal. Mail is stored as private to the mailbox owner, and mail signals carry no address, subject or excerpt in their summary. If you dismiss one thread, Hive quiets that thread — not every thread with that person. With a Max seat, a mail signal gets a real reply instead of a standard holding note: Hive reads the whole thread from your own mailbox, then writes a reply that answers what the other person asked, in line with what you already said and in the tone of your own messages in the thread. The reply goes in the same thread. Your mailbox’s Read, Draft or Act level decides what happens next; see Read, Draft or Act. A mail signal arrives as needs reply with no draft if its member has no credits left to prepare it (on Business), or, on an earlier plan, if it was raised for a member without a Max seat, or is past the seat’s fair use and neither the credit pool nor your Signals overage cap can cover it. With a seat, you can still choose Act on this to have Hive prepare the reply; on Business this uses your own credits, and on an earlier plan, above fair use, pool credits. See Signals fair use.

Your own mailbox only

Mail signals are raised for each member, only from that member’s own connected Gmail or Outlook account, and appear only to that member: never to other members, Owners and Admins included. Hive reads only mail it stored through your current connection.

People in your mail join your Brain

The senders of the mail Hive stores, and the people you write to, join your own Business Brain, with their address, their company’s domain and the date of your latest thread with them. Newsletters, automatic mail, no-reply senders and messages to more than 25 people are skipped. Only you see them, in the Hive app and in Ask. Disconnecting the mailbox removes them again, except the people and companies something else in your Brain also stands behind.

The messages a signal is about

Each Awaiting reply and Went quiet signal lists up to five of the exact messages it is about, for example “Their message · 3 Oct · Open in Gmail”. Only you see the list. Hive keeps only the message ids: no address, subject or excerpt, and nothing about them goes into notifications. The source link in the review panel opens the latest of them.
  • Gmail links open in the first Google account signed in to your browser.
  • Outlook message ids can change when a message is moved to another folder, so a moved message may not open.
On a matter, each item under Across your accounts shows Open in Gmail or Open in Outlook when Hive can make an exact link: Gmail threads and messages, and Outlook messages. An Outlook conversation opens at its newest message Hive stored. Systems of record, files and people get no link yet.

Seeing the conversation when you review a reply

When you review a reply or nudge Hive drafted for an email signal, the panel shows the latest five messages of the thread, with email addresses hidden (see Review and approve). Thread excerpts appear only in the mailbox owner’s own review panel, read from mail Hive already stores. No extra read from your provider and no AI processing are involved, and the panel is not available to AI clients over MCP.

When Hive judges a thread

Hive judges a thread only after a complete, recent sync of your mailbox, including Sent Items, has finished after the thread’s newest message, so a reply you have sent is taken into account. Until then it neither raises a signal nor clears one. Hive raises nothing for a mailbox, and its open mail signals read Can’t confirm — coverage incomplete, when:
  • an Outlook account has synced only its Inbox so far;
  • the mailbox sync is in error, for example because access was revoked or the provider’s change history expired;
  • the account is disconnected or needs reconnecting;
  • Hive could not read the stored mail for that mailbox on a pass.
A thread is held on its own, while the rest of the mailbox is judged as usual, when one of its messages failed to download or could not be read, or its dates are unclear (two messages at the same instant, or one dated in the future). Such a message never pushes newer mail out of what Hive reads. After you reconnect or re-authorise a mailbox, and after a first full scan that spans several hours, Hive waits for one more complete hourly sync before raising or clearing mail signals. A mail signal clears only after a sync that fully caught up with the provider, with no messages waiting to be retried, in the last two hours. In a large workspace, each hourly pass judges mailboxes in turn, least recently checked first, up to 100 per pass. It opens at most 8 new mail signals per mailbox and 200 per workspace on each pass, oldest wait first; the rest open on later passes, and a mailbox cut short goes first next time. Signals already open are re-checked on every pass. A signal on a mailbox the pass did not reach keeps its state while Hive has seen it in the last two hours; after that it reads Can’t confirm — coverage incomplete until the mailbox is read again.

Reminders

A mail signal keeps one Inbox card while it is open. Hive does not send a new card each time the number of days rises; a new card appears only when the severity rises or a reminder comes due:
  • Awaiting reply — one reminder 24 hours after Hive first flags it.
  • Went quiet — a nudge 12 hours after Hive flags it, and another 3 days after.
Each reminder replaces the earlier card for that signal and is sent once. No reminder is sent once the signal is resolved, dismissed, withdrawn, approved or denied, or while it is snoozed. Reminders are sent on Hive’s hourly pass, so one can arrive up to an hour after it falls due. Each pass works through the reminders that have come due, oldest first, several hundred at a time, so a large backlog — for example right after a first mailbox read — no longer trickles out at 50 an hour. If the signal stays held (snoozed, in cooldown, or being worked on) through five hourly passes, the reminder is dropped rather than sent late.

Mail Hive cannot read yet

Gmail and Outlook sometimes fail to return a message, or ask Hive to slow down. This is how Hive handles each case:
  • A failed read is never treated as a deletion. Hive keeps what it has already stored and tries the message again on later syncs.
  • When the provider asks Hive to slow down, Hive stops reading mail for that sync and carries on in the next one. Messages still waiting to be read keep their place and are not counted as failed attempts. For Outlook, this includes the check Hive makes to see whether a message was moved to Deleted Items.
  • After five failed attempts, Hive stops retrying a message. It keeps the last copy it read, or, if it never read one, keeps the message without its text. If more than 200 messages on one account are waiting, Hive stops retrying the oldest of them sooner.

Outlook mail you move to Junk Email or Deleted Items

When you move an Outlook message Hive has already stored to Junk Email, or to a folder inside Deleted Items, Hive notes the move on its next hourly sync. From then on, that message is left out of mail signals and of the stored mail Ask reads, such as a whole thread opened from a signal, and Ask’s search of your workspace no longer finds it. Hive keeps the stored copy and does not delete it. If you move the message back to your Inbox, it counts again from the next sync. A message moved to Deleted Items itself is removed from what Hive stores, as before. This applies to moves Hive sees from now on: Outlook mail moved to Junk Email before this change still counts until Hive syncs that message again. Gmail mail in Trash or Spam is already left out.

Ask about all your mailboxes

When you ask about your email in Ask without naming a mailbox, such as “read my sent emails”, “what’s in my inbox?” or “emails from Tom”, Hive searches every mailbox you have connected at once: each Gmail and each Outlook account. Each message in the answer is labelled with its mailbox, and the steps show one line per account, such as Checking Outlook (you@yourfirm.com).
  • Name a mailbox to narrow it. “In my Gmail” searches only your Gmail accounts, and naming an account by its address, such as “my you@yourfirm.com mail”, searches only that one.
  • One mailbox failing never hides the others. If one account cannot be read, for example because it needs reconnecting, Hive answers from the rest and says which mailbox it could not read. Its step shows as failed.
  • Only your own mailboxes. Hive searches only the accounts you connected yourself, never a colleague’s, Owners’ and Admins’ included. Pinning a mailbox with @Gmail or @Outlook still limits the chat to that provider.
  • Hive searches up to eight mailboxes in one go, each for up to 20 messages, and searches each provider at most five times for one question. A search that finds nothing does not count towards the five, so Hive can try a sender, their domain and another address in turn.
  • More results stay within reach. When a search finds more messages than fit in full, Hive lists further messages by subject, sender, date and id, as many as fit, so it can open the one you need instead of searching again. It says how many more it found beyond that list.
  • Mail you threw away stays out. A Gmail search or thread leaves out mail in Trash and Spam. An Outlook conversation, and an Outlook search of all folders, leave out Deleted Items and Junk Email. When a Gmail thread, an Outlook conversation or an Outlook search had messages there, Hive says how many it left out. Ask for that mail (“include my trash”, “search my junk folder”) and Hive reads it.

Gmail

Connect: OAuth. Hive reads: your profile, labels, and inbox, unread and search results as message metadata and snippets, in all mail or one folder or label. Agents and Ask can open one message, or a whole thread (up to its 25 newest messages), with the body text and attachment names and sizes. A thread leaves out messages in Trash or Spam unless you ask for them. Attachments: ask for an attachment by name (“get Invoice-Q3.pdf from the Q3 invoice email”) and Hive reads its text into the chat: PDF, Word, Excel, CSV and plain text, up to 10 MB. Hive can also save a message’s attachments (up to 10 MB each) into a Google Drive, Dropbox, OneDrive or SharePoint folder on one card: see Upload files from Hive, chats and email. Saving a Gmail attachment to the Library is not available yet. Actions: send, reply in a thread, forward, create a draft (up to 20,000 characters), change labels, create or rename a label, delete a label, trash and untrash, and send an email with Google Drive files attached.
  • Forward: “forward the Q3 accounts email to the partner with the note FYI” sends your note, then the original message quoted (from, date, subject, to and its text), with its attachments, up to 5 MB together. The card shows the recipients, your note and the original subject, and is marked high-risk like every send. Each recipient must be someone you named in the chat or a contact on your records. A larger message is forwarded from Gmail itself.
  • Labels: create a label, nested under an existing one (“Clients/Acme/Invoices”), or rename one of your own labels. Gmail’s built-in labels (Inbox, Starred) cannot be renamed. Renaming a parent label does not rename the labels nested under it.
  • List your labels: “which Gmail labels do I have?” lists each label with its type (yours or Gmail’s own) and how many messages, and unread messages, it holds, your own labels first. Name a label in a change (“label this email Clients/Acme”) and Hive finds its id itself; you are never asked for a label id.
Delete a label: “Delete the Gmail label “Clients/Old client” (emails stay)” is one approval card at the highest risk tier, naming the label and its id from your labels. Gmail removes the label from its emails; the emails themselves stay in your mailbox. Only labels you made can be deleted, never Gmail’s own (Inbox, Starred and the like). Deleting a label needs the same Gmail permission as changing labels. Send a Google Drive file: “Email the engagement letter in my Drive to jane@acme.com with the subject ‘Your engagement letter’” is one approval card at the highest risk tier. It shows the recipients, subject, body and each file. When you approve, Hive reads each file from your own Google Drive connection, checks it still has the name the card shows, and sends one email with the files attached. Google Docs, Sheets and Slides go as PDFs. Up to 5 files and 3 MB together; for anything larger, share the file instead. The recipients must be people you named in the chat or contacts already on your records. When you ask for an email from Gmail with a file attached, the card is always this Gmail one, never an Outlook email; if Hive cannot find the file in your Google Drive it says so and prepares no email, rather than one without the file. New mail as it arrives: where Hive’s real-time Gmail is on, Hive asks Gmail to tell it when new mail reaches your inbox, renews that request on its own once a day overnight UK time, and cancels it when you disconnect. Hive then reads the new mail within about a minute instead of waiting for the hourly sync. Without it, the hourly sync reads your mail as before. A reply in a thread stays in that Gmail thread, for you and for the person you are answering. For mail Hive stored before this was added, the reply still files into your own thread but may appear as a new conversation for the recipient. Subjects and names in mail Hive sends or drafts in Gmail keep accented letters, symbols such as £, € and –, and emoji exactly as written. Changing a message’s labels in Gmail — archiving it, starring it or marking it read, for example — does not make Hive process the message again. Hive notes the change and keeps the copy it already holds; it processes a message again only when the message itself changes. When one change touches many messages at once — a bulk label change, a filter applied to a large folder, or moving many messages to Trash or Spam — Hive works through that change 25 messages per sync step until it has read every message it touched. Messages moved to Trash or Spam are removed from Hive as it reaches them. A message it already holds is not processed again unless it changed. On a large change this can take several hourly syncs; mail that arrives meanwhile is read as soon as it finishes.

Outlook

Connect: OAuth (Microsoft Graph mail and calendar). Hive reads: your profile, mail folders and their subfolders with unread and total counts, messages (searched in every folder but Deleted Items and Junk Email, or in one: Inbox, Sent Items, Drafts, Archive, Deleted Items, Junk Email or a folder id), whole conversations (without Deleted Items and Junk Email unless you ask), a message’s attachments (each one’s name, type and size — never its contents), calendars, calendar view, one event with its attendees and your own response, free/busy and people lookup. Hive’s Outlook source tracks calendar events — start and end, time zones, all-day, cancellations and subject. Mail folders: “show me my mail folders with unread and total counts” lists each top-level folder with its unread and total messages and how many subfolders it has, each followed by its own subfolders (Inbox, then the folders you made inside it). Hive reads two levels at a time: when a folder has subfolders below that, Hive says which folder has them, and “show the folders inside Clients” lists them. Name a folder in a change (“move this email to Clients”, “move the folder Clients into Archive”, “rename the folder Receipts”) and Hive takes the folder’s id from this list itself, and for a folder move also the folder it sits in now, so the move can be undone: you are never asked for a folder id. A workflow can read the same list with a Read from an app step (List mail folders). Live updates: when you connect Outlook, Hive asks Microsoft to notify it whenever a message in your mailbox or an event in your calendar is created, changed or deleted. A notice names the message or event and nothing else, so Hive then re-reads your mailbox, usually within a minute, instead of waiting for the hourly run. Calendar changes are still read on the hourly run. Hive renews the notifications once a day, overnight UK time, well before they expire. If setting them up or renewing them fails, Hive tries again at the next overnight renewal; until then the hourly run keeps your mailbox current. When you disconnect Outlook, Hive turns them off. An Outlook account connected before live updates were available gets them automatically, without a reconnect, within a day of live updates being switched on. The same notices can start a workflow: see Connected app event. Actions: send, reply, forward, create a draft (up to 20,000 characters), move, mark as read and delete a message; flag a message for follow-up on a date, or clear its flag, and add a category on the same card; set a message’s categories; add one category to up to 50 emails a search found, on one card; delete a draft (Delete draft message, for an unsent draft Hive read from your Drafts folder); create a mail folder (at the top level or inside another), rename one, move one into another folder, or create a folder with its subfolders in one approval; delete a folder you made, with everything in it; change a draft’s subject or add people in cc; accept, tentatively accept or decline an invitation, with a note to the organiser, or propose a new time instead; create, update, cancel or delete a meeting, make a new meeting a Teams meeting, or make it repeat; create a calendar. A meeting with no attendees sends no invitation and its card says so; as with Google Calendar, Hive is rolling out a check that never prepares a meeting that starts in the past (see Google Calendar). Hive can also save a message’s attachments, or a whole email thread, into a Google Drive, Dropbox, OneDrive or SharePoint folder: see Upload files from Hive, chats and email. Replies from an alias: an Outlook.com or Microsoft 365 account often receives and sends mail on an address other than the one it signs in with. Hive replies in those threads too: it treats every address your mailbox has sent from as yours, so it never sends the reply to you, and Outlook sends it from your account. Large attachments: “show me Outlook emails with attachments over 10 MB from the last 6 months” searches for mail of at least that size, then reads each message’s attachments and lists only the messages carrying an attachment that large, with each file’s name and size. It checks up to 20 messages per question; narrow the dates or the sender for more. Several emails at once: “add the category Acme to every Outlook email from acme.com in the last 30 days” searches first, then shows one card listing each email’s subject and id. When you approve, Hive re-reads each email, keeps the categories it already has and skips one that already has Acme. If an email’s subject changed since the search, nothing is changed. “Move these 3 emails to FYI”, “mark them as read” or “flag them for follow-up” gives one card per email, each naming the email by its subject and the folder by its name. Hive uses each email’s exact id from the search, so a long result list no longer stops every card. If one email can no longer be matched, only that one is left out; the others still get their cards. A move to Archive, Inbox, Junk Email or Deleted Items needs nothing more; for any other folder Hive first reads your mail folders, and uses the folder in the mailbox the email is in. Moves, read marks, flags and categories can be undone from the Audit log, and their cards say so. Undoing a move puts the email back in the folder it came from. These cards work from any Outlook search, opened email or conversation Hive read in the chat, so you never need to give Hive an email’s id; each result shows the email’s id and folder for reference. Flag or reminder: “flag the ones that can wait for follow-up on 12 November” puts an Outlook follow-up flag, due that day, on each of those emails: a card per email, not a scheduled task. Ask “remind me on 12 November to check them” when you want Hive to come back to you instead. A flag card leaves an email’s categories as they are; it changes them only when you ask for a category, and Hive clears an email’s categories only when you ask it to. Invitations: “accept the Board meeting on Tuesday and decline the supplier lunch with the note ‘travelling’” gives one card per invitation, each naming the event and its id. A proposed new time goes with a decline or a tentative accept, as Outlook sends it, and the organiser is told. Emails with files attached: Hive can send an email, or save a draft, with files from your own OneDrive or SharePoint attached, such as a management pack or a proposal it has just created. The card shows where each file lives (the site, library and folder, or only the site for an Office link that does not show the folder), so a file with the same name from another site stands out. Hive reads each file from your own connection when you approve, checks it is still the file in the place the card names, and attaches up to 5 files and 3 MB in all. For a larger file, ask for a view-only sharing link instead. A file from the Hive Library or from a chat cannot be attached yet. A send is always a card you approve; a draft is saved in your Drafts folder and nothing is sent. When you ask for a file to be attached (“email Ana the proposal from my OneDrive as an attachment”), the card always lists it under Attached. If Hive cannot find the file in your own OneDrive or SharePoint, it prepares no email at all and tells you, rather than a card that would send the email without the file. Replying to everyone, or to an automated sender: “reply all” goes to everyone on the message you answer: its sender, the other people it was sent to (shown as Also to) and the people copied (shown as Cc), never you. When you ask Hive to reply to an automated message, such as a deployment alert, the reply goes to its sender’s address when the message has no Reply-To; an address no mail reaches, such as noreply@, is still refused. Folders with several mailboxes: with more than one Outlook account connected, every mailbox has its own Inbox. Name the mailbox (“in my mailbox qa@example.com, create TEST-2026-11 under Inbox”) and Hive uses that mailbox’s folder without asking again which Inbox you meant. A rename runs on the mailbox the folder was read from. Folders under Inbox: “create the folder Clients inside Inbox” makes a card straight away: Hive does not need to look up the Inbox first. The same goes for Archive, Drafts, Sent Items, Deleted Items and Junk Email. With more than one mailbox connected, the card asks which mailbox to use. Folders in one approval: “Create the folder Acme with Contracts, Invoices and Correspondence under Clients” is one card. Hive creates the parent folder first and then each subfolder inside it, up to 3 levels below it and 40 folders in all. A folder that already exists is reused, so running the card again is safe. To move emails into a folder that does not exist yet, approve the folder card first; Hive then proposes the moves. Deleting a folder: “Delete the Outlook folder Old matters and everything in it” is a card that shows how many emails and subfolders the folder holds. Hive checks the folder again when you approve and stops if it now holds more than the card showed. The folder goes to Deleted Items, so you can restore it from there. Inbox, Sent Items, Drafts, Deleted Items, Junk Email, Archive and Outlook’s other own folders are never deleted. Changing a draft: “Change the subject of my Outlook draft Engagement letter to Engagement letter v2 and add ana@client.com in cc” is one card. Hive opens the draft again when you approve and stops if it has been sent or its subject has changed. The people already in cc stay; each new address follows the same rule as an email Hive sends. Nothing is sent, and undo puts the subject and cc back as they were. Repeating meetings: “Create a weekly Outlook meeting Team WIP every Monday at 9:00 with Ana and Ben, as a Teams meeting” is one card that shows the rule in words, for example “Every week on Monday, from 2026-11-16, with no end date (Europe/London time)”. A meeting can repeat daily, weekly on chosen days, monthly or yearly (on a date, or on a day such as the first Monday), with no end, until a date, or a set number of times. Hive keeps the meeting’s time in your time zone, so 9:00 stays 9:00 when the clocks change. One meeting of a series: “move Tuesday’s stand-up to 10:00” changes only that occurrence. Hive finds it in your calendar for that day and names it on the card with its date, for example “Daily stand-up (2026-11-10)”; the rest of the series stays as it is. Cancelling or deleting one occurrence works the same way. Each meeting in an Outlook calendar answer carries its own id, so Hive never asks you for an occurrence’s id. What Hive cannot do in Outlook: Microsoft does not let apps block a sender, so Hive says so when you ask; it can move the sender’s emails to Junk Email, which does not block them. Hive cannot create inbox rules yet, because its Outlook connection is not allowed to change mailbox settings; it can move or categorise the matching emails now instead. To delete or change an existing email or meeting, name it, for example “delete my Outlook email with the subject Q3 invoice” or “delete the meeting Weekly sync on Wednesday”. When exactly one item Hive read has that subject or title, Hive picks it; when more than one does, it asks which. Deleting an Outlook email moves it to Deleted Items. Hive never deletes an email permanently, so an email already in Deleted Items stays there. A new email or draft Hive writes for you can be up to 20,000 characters long, in Outlook and Gmail alike and with or without attached files. A reply in a Gmail thread can be up to 10,000. A reply in an Outlook thread, and the note Hive adds when it forwards an Outlook message, can be up to 4,000 characters. Emails, drafts and replies Hive writes for you are plain text. Formatting the AI might add, such as bold, headings or bullet symbols, is removed before the card is prepared: a list becomes lines starting with a dash, and a link becomes its text with the address after it in brackets. The approval card shows exactly the text that will go out, so what you approve is what the recipient reads. If you edit the text on the card, Hive sends your words exactly as you typed them.

Admin approval for Microsoft 365

Many Microsoft 365 organisations let only an administrator approve a new app. If Microsoft’s sign-in window says you need an admin’s approval (Microsoft calls it Need admin approval), you cannot finish connecting Outlook or OneDrive yourself:
1

Ask your Microsoft 365 administrator to approve Hive

They approve it for your organisation in Microsoft’s own admin tools. If your organisation has admin consent requests turned on, Microsoft’s window lets you send them a request directly.
2

Retry

Once it is approved, choose Retry in setup’s Connect your work step, or Connect on the app in Integrations.
In setup, Hive shows this hint whenever a Microsoft 365 approval is cancelled or fails, because Microsoft’s window gives Hive no reason it can pass on. See If connecting fails for the other messages.

Google Calendar

Connect: OAuth. Hive reads: upcoming events and single events on your primary calendar, your list of calendars, and free/busy for the people you name. Actions: create, update, delete and move meetings; create and delete calendars.
  • Google Meet: ask for a Meet link and the invitation gets one; the card says so.
  • A Meet link on an existing event: “Create a Google Meet link for “Acme kick-off” and add it to the calendar event” is one approval card on the event you named. Hive reads the event again before it writes and refuses if it already has a video conference (Meet, Zoom or another), so none is ever replaced. Google sends the attendees the update, and the receipt shows the link.
  • Repeating events: ask for a monthly meeting “on the 3rd working day at 10:00” and Hive builds the repeat rule itself: every month, on the third of Monday to Friday. Weekly, monthly (a day of the month, the last day, or the Nth of chosen weekdays), daily and yearly repeats work, every N weeks or months, a number of times or until a date. The card says the rule in words (“Every month on the 3rd working day (Mon–Fri), 12 times”) with the rule itself and the time zone it repeats in. Hive refuses a first date the rule does not fall on, so Google never adds a stray first meeting.
  • All-day events: a deadline (“31 January”) is created as an all-day event, on one day or across several.
  • Reminders: ask for reminders such as “14 days before” or “7 days before”, by email or as a notification, up to five per event and up to four weeks ahead.
  • A message to attendees: Google Calendar has no message field on an update, so when you move a meeting “and tell them …”, Hive adds your message after the event’s existing description (it reads the event first, so the agenda and dial-in details are kept) and Google emails every attendee the update. The card shows the whole new description and the message, and says how it is sent.
  • Attendees: every address on a meeting card must be one you typed in the chat or a contact on your records, like the people Hive emails.
  • Holds with no attendees: a meeting with nobody invited (a hold in your own calendar) sends no invitation, and its card says No invitations (no attendees).
  • Times you can trust: Hive never prepares a meeting card, new or moved, whose start has already passed. When your message names when you want the meeting (“tomorrow”, “next week”, “on Friday”), a card outside that is not prepared either, and Hive asks you which time you want. A time you mention about something else (“I’m out today”) does not count. If the answer in Ask gives a meeting a different day than every card, Hive removes that sentence and lists the cards’ real times. This is rolling out to workspaces gradually.
Changes as they happen: when you connect, Hive asks Google to tell it whenever an event on your primary calendar changes. Hive renews that request on its own, checking once a day overnight UK time, and cancels it when you disconnect. A workflow with a Connected app event trigger on Google Calendar then starts within about a minute of the change. Google’s notice says only that the calendar changed, so Hive reads what changed and starts the workflow with Calendar event created, Calendar event changed or Calendar event cancelled (see Apps Hive checks for changes).

Slack (connector)

Connect: OAuth. Hive reads: the public and private channels you are in, channel history, threads and identity. Agents and Ask list your channels and read a channel’s latest messages and a thread’s replies. Hive does not search Slack messages by words: Slack only allows that with a personal user token, and Hive’s Slack app connects as a bot. Hive tracks channel metadata — name, created, archived, private and externally shared. When Ask reads Slack, it can only call Slack’s read methods: channels, channel history, threads, the channels you are in, people and identity. Slack accepts posts and other changes through the same kind of request as a read, so any other Slack request the model writes while reading is refused before it is sent, and nothing is posted. Signals read Slack messages as they arrive, but only messages a person wrote. Posts by bots and apps (Hive’s own included), edits, deletions and joins are skipped. Files shared and replies also sent to the channel are still read. Actions: post a message, reply in a thread, update or delete a message, add a reaction, and schedule a message.
  • Scheduled messages: ask “schedule a Slack message in #general for Monday 9:00 saying …” and the card shows the channel by name and id and the time in your own time zone. Slack sends it at that time; it must be in the future and at most 120 days ahead. Hive cannot undo a scheduled message: delete it from Slack’s scheduled messages before it goes out.
Messages Hive posts to Slack show no link previews: Slack does not fetch or expand the links in them, whether Ask, an approved action, an agent or a workflow posted them.

Microsoft Teams (connector)

Connect: OAuth. Hive reads: teams, channels, chats and who is in them, chat and channel messages, and the replies to a channel post, when you ask. Hive also reads your chat list in the background: each chat’s type, when it started and when it was last updated. The connection needs Chat.ReadBasic, Chat.Read or Chat.ReadWrite for that. See When background reads are off. Actions: send a channel message, reply, send a chat message, create a channel; start a new one-to-one or group chat and send its first message; edit or delete a chat message you wrote. New chats: to message someone you have no chat with yet, Hive starts the chat and sends the message on one card. It finds each person in the members of your existing Teams chats, so the card shows the name and Microsoft id of everyone it adds; you are added yourself. A one-to-one chat with someone you already chat with is reused. A group chat can have a topic. Editing and deleting your messages: “edit my Teams message in Acme year end that starts ‘Please send’ to say …” reads that chat’s messages, and the card names the chat and the message id. When you approve, Hive checks the message is yours and refuses one someone else wrote. A delete is a higher-risk card and can be undone. Only chat messages can be edited or deleted: channel messages cannot, because the Teams connection does not have permission to change them. Hive cannot list or upload files in a channel’s Files tab through the Teams connection either; use SharePoint, where each team’s files are stored. Catch up and mentions: ask “what did I miss in Teams yesterday?” or “show me the Teams messages that mention me from the last 7 days” and Hive reads your most recently active chats (up to 10) and the channels you name or are active in (up to 5), 20 messages each, and keeps the messages since that date that @mention you, plus your one-to-one chats for a catch-up. Each message shows who it mentions. Hive says how many chats and channels it read, and tells you when it reached one of those limits. Ask it to reply and each reply is a card you approve. Meeting transcripts are not read. Starts workflows: a Connected app event trigger on Microsoft Teams starts when someone else sends a message in one of your chats, checked about every 15 minutes.
The Slack and Teams connectors let Hive read and post. They are separate from the Slack and Teams channels, which let your team ask Hive questions by @mention or DM. See Slack and Teams.

Actions in scheduling, event and meeting apps

Hive reads these apps live (see Support, phone and meetings) and can also make these changes. Each one waits on an approval card for a member to approve, even on Act.
  • High-impact actions. Cancelling, rescheduling or relocating a Cal.com booking (Cal.com emails the attendees), moving or deleting a YouCanBook.me booking, adding Luma guests, changing a guest’s status, sending Luma invites, and any delete need the stronger approval.
  • No refunds, no surprise emails. Hive never refunds a Luma guest and never cancels a Luma event. Luma guests are added without an email unless you ask for one, a status change does not email the guest, and editing a Luma event does not email its guests. A new Luma event is private unless you choose otherwise. A new Zoom meeting invites nobody.
  • Addresses checked like email recipients. Each Luma guest you add or invite, and a Zoom meeting’s host, must be in your workspace directory, typed by you, or set by the workflow. The approval card names each address and says where it came from.
  • Only records Hive read. A change to a booking, schedule, booking page, customer, appointment, event, guest or meeting names one Hive read from your account in the same chat or run. A workflow’s Action step therefore offers only the creates. The other actions run from Ask and agents.
  • Permissions. These actions use the same key or app as the reads, so it must be allowed to write. A Zoom server-to-server app also needs meeting:write:admin and recording:write:admin. A read-only key or scope is refused by the app.

Ideas

  • The Email Keeper workflow template reads new Outlook mail every hour, flags anything unusual for a human and drafts the rest of the replies.
  • “Which clients have I not replied to this week?”
  • “Find a free hour with the finance team next Tuesday and draft the invite.”

Triage signals

Act on, snooze or dismiss.

Accounting and client services

How client-facing firms use Hive.