In Ask (a chat with no agent picked) and Signals, each
account’s Read, Draft or Act level decides what Hive does with the actions below.
Even on Act, an action Hive cannot undo waits for a person to approve it, and that is almost
every action below: refunds, voids and deletions, but also new and emailed invoices and new or
edited contacts. Archiving a Xero contact is the exception, because Hive can undo it. An agent or a workflow carries out the actions selected for it
by itself on an Act account (on Draft each waits for approval, on Read none is
taken), and on Act waits for your approval only when where an action
sends did not come from you (see
What agents and workflows do by themselves).
An action on an existing record, such as a refund or sending or voiding an invoice, is not held
that way, so select money actions with care, or put an Approval step
before them in a workflow.
Xero
Connect: OAuth. Hive’s invoice signals need theaccounting.invoices.read permission; an older
connection granted accounting.transactions.read works too.
Hive reads: chart of accounts, profit and loss (income, costs and net profit for any period,
so Ask can chart them by month), balance sheet (as at a date, beside the
same date a year earlier), bank summary, invoices, overdue sales invoices (oldest due first, with
days overdue, an ageing bucket and the contact’s email address), paid sales invoices, one invoice
or bill with its line items and payments, contacts and bank transactions. Ask can also read the aged
receivables and aged payables report for one contact, every customer’s outstanding invoices and every
supplier’s outstanding bills (so it can age them by days overdue), unreconciled bank transactions
(oldest first, with a count per bank account), manual journals, the trial balance (for suspense and
uncategorised balances), draft invoices and bills, and a supplier’s past bills (to find the account
that supplier is usually coded to), and repeating invoices with their schedule, next date and total
(so Ask can say which will be raised next month and for how much). Ask also reads the budget summary
report (budget against actuals by account and month) and your budgets, and your tracking categories
with their options. The profit and loss can be split by one tracking category, one column per option
(revenue and direct costs by client, or by cost centre), or read for one option only.
Xero’s API does not give the bank-feed statement lines that are waiting to be matched, the UK VAT
return or its due date, and it cannot reconcile a bank line. Ask says so; for the VAT due date it reads
your HMRC VAT obligations when HMRC is connected.
The email address on an overdue invoice is the contact’s own email in Xero or, if that is blank, the
first of the contact’s people that Xero sends invoices to. A workflow that chases overdue invoices
can send each reminder to it. If your connection cannot read Xero contacts, the invoices are still
listed, without an email address.
Change notices: Xero tells Hive when an invoice or contact changes in your organisation. Xero
data itself is still read on the hourly run. Notices about organisations you have not connected
are ignored, and the notices can start a workflow: see
Connected app event.
Actions: create, update or archive a contact; add a note to a contact’s history
(Xero cannot remove a note once added); create a draft invoice; create a draft bill from a
supplier, coded to an account; email an invoice; void an authorised invoice; delete a draft invoice.
Signals: Invoice collection. Hive tracks each authorised invoice’s amount remaining,
due date (in your Xero organisation’s time zone, when Hive has permission to read your organisation settings), contact and status, and raises a signal when collection needs
attention. When the signal is first turned on, it opens one case for each invoice currently
awaiting payment, so nothing already overdue is missed.
On your matters: where Signals keeps your matters, it reads your Xero account as you,
read-only:
- Sales invoices, open ones oldest due first, up to about 200 per read, so the most overdue are always read. Each invoice is tracked by its own Xero id. An open invoice becomes overdue from 12:00 UTC the day after its due date, and Hive then decides whether to raise an Invoice to chase on its matter, within about a day, even if nothing about the invoice changed. In a ledger with more open invoices than one read covers, the furthest-off ones wait for a later read.
- Paid and voided invoices that changed since the last read, and the invoices your matters already link, by their id. An invoice paid in Xero with money received reads Paid on its matter. Voided, credited and other closed invoices end the chase without claiming payment.
- Bills you owe, as bills rather than mixed in with your sales invoices, open ones earliest due first. Bill reads are capped and say when they were cut short. A bill due can raise a Payment due with its amount on its matter; Hive never pays a bill.
- How late a customer usually pays: for customers with an overdue invoice on one of your matters, the last 12 months of their paid sales invoices, to learn a fact for your own Brain. See How late a customer usually pays.
Stripe
Connect: the managed connector. Hive no longer offers Stripe’s MCP server; an existing Stripe MCP connection keeps working. Hive reads: charges, invoices, customers, balance, payment intents, subscriptions and payouts. Ask can follow an invoice to the charge that paid it and to the payout it landed in, through the charge’s balance transaction, and read the balance transactions of a month (charges, fees, refunds and payouts), for example to turn them into a DATEV booking batch. Actions: issue a refund (always the highest-risk tier), create, update or delete a customer, create a draft invoice for one amount with a due date and description, finalise an invoice, send an invoice, retry payment of an invoice (charges the customer’s payment method on file), cancel a subscription at the end of its current period (the card shows the date it ends, which must be the one Stripe returned for that subscription; it keeps running and billing until then, nothing is cancelled now or refunded, and Undo keeps it running), create a payment link (the amount and name are on the card; Stripe makes the price for it, so no product or price needs to exist first), create a credit note on an invoice (the card shows the invoice, amount and reason, in the invoice’s own currency as Stripe read it; an open invoice’s amount due goes down, a paid one is credited to the customer’s Stripe balance, and nothing is refunded), delete a draft invoice, void an invoice. Send an invoice emails a finalized Stripe invoice to its customer; like voiding, it always waits for your approval and cannot be undone. Every Stripe invoice action, retrying a payment, cancelling a subscription, creating a payment link and creating a credit note are the highest-risk tier. To email a payment link, ask Hive to draft the email in the same request. Signals:- Automatic-collection invoices — invoices Stripe is charging automatically that need attention.
- Send-invoice overdue collection — emailed invoices past their due date.
- Disputes needing a response — card disputes with evidence due.
QuickBooks
Connect: OAuth. Hive reads: company info, customers, invoices (all of them, or one customer’s, so Ask can total what a customer was invoiced this year and what is still unpaid), vendors and bills, and record detail. Ask can also read the accounts receivable and accounts payable ageing reports, the profit and loss report (month by month, to compare a month with the one before), the balance sheet as at a date, bank account balances, items, the chart of accounts and expenses for a period. Bank-feed lines not yet added in QuickBooks are not available through its API; Ask says so. Actions: create or update a customer; create a vendor, with an email address; create an estimate for a customer, with an item, amount and expiry date (saved, not emailed); change an invoice’s due date, date or internal note (only those fields change, and QuickBooks refuses the change if the invoice was edited since Hive read it); void an invoice (it stays in QuickBooks, zeroed and marked Voided; QuickBooks refuses it if the invoice was edited since Hive read it); create a journal entry for a date, debiting one account and crediting another by the same amount, with a memo (the card shows each account’s name and id, both from the chart of accounts Hive read); create an invoice, with a due date, reference, line description, tax code, a message to the customer and an internal note; create a bill from a vendor, coded to an expense account, with the supplier invoice from an Outlook email attached to it (see Attach the invoice or receipt from an email); record a customer payment against an invoice; email an invoice or send a payment reminder (QuickBooks sends it to the billing email on the invoice, never another address); delete an invoice (permanent); deactivate a customer. Emailing an invoice, sending a reminder and voiding an invoice are the highest-risk tier. Starts workflows: a Connected app event trigger on QuickBooks starts when an invoice is created or changed, a payment is received, or a customer or bill is created, checked about every 15 minutes. Signals: no certified invoice-collection signal yet; Signals reads its invoices into your matters. On your matters, QuickBooks invoices and bills are read as you, read-only. QuickBooks has no invoice status of its own, so Hive works one out from the balance: an invoice or bill with a balance is still owed, and counts as overdue once its due date has passed. QuickBooks never shows Paid until Hive can read the linked payment. In Ask, you can list QuickBooks bills with their supplier, total, balance and due date.FreeAgent
Connect: OAuth. Hive reads: company details, bank accounts and balances, profit and loss (income, costs and net profit for any period, in your company’s currency, so Ask can chart them by month), bank transactions, tax and VAT dates, invoices, bills, expenses, contacts, users, projects, timeslips and categories. Ask can also read unbilled timeslips (to value work in progress by project and client at each task’s billing rate), timeslips in a date range (billable hours per person, against a target you give), a project’s budget against the time logged, the tax timeline (upcoming VAT, corporation tax and other dates with the amount due, where FreeAgent tracks them), recurring invoices with their agreed amounts, and one project’s timeslips and invoices, so Ask can show the hours logged, what is billed and what is still unbilled. “Show my FreeAgent projects” reads FreeAgent’s projects, never your Hive projects. When FreeAgent has no expenses, projects or timeslips, Ask says there are none and cites the read. “Show all my FreeAgent contacts” lists every contact, hidden ones included; a contact searched by name is found whatever its status, across several pages of contacts. “My VAT returns” lists each VAT return with its period, filing status and due date, and the amount due with its payment date and status. “Who in FreeAgent has not logged time last week?” reads your FreeAgent users (name, email and role) and compares them with the timeslips in that week. Actions: create and email an invoice, or create a draft invoice that stays in FreeAgent for you to review and send there; create and email an invoice that bills every unbilled timeslip on a project; send an invoice reminder (FreeAgent’s own invoice email to the contact on the invoice); explain a bank transaction as a category or as payment of an invoice; mark an invoice as paid from a bank account; create a bill, expense or timeslip, with the receipt from an Outlook email attached to an expense (see below); create, update or delete a contact; create a draft credit note for an invoice’s contact (not sent, and not yet allocated to the invoice); create a project for a contact, billed by the hour or day at a rate; change an invoice’s due date (FreeAgent sets the payment terms to the days from the invoice date, which must be the date FreeAgent returned for that invoice). An expense is claimed by a FreeAgent user Hive reads from your FreeAgent users (you, unless you name a colleague) and needs no bank account. The users, contacts, categories and projects Ask finds are what an expense, bill, invoice or timeslip card is built on, so Hive never asks you to paste back a record it has just shown you. “Which FreeAgent category is General Purchases?” lists your categories with their kind (admin expenses, cost of sales, income or general) and nominal code. Emailing an invoice or a reminder is the highest-risk tier. Starts workflows: a Connected app event trigger on FreeAgent starts when an invoice is created or paid, or a contact or bill is created, checked about every 15 minutes. Signals: none certified yet; ask about FreeAgent data in Ask Hive. On your matters, FreeAgent invoices are tracked by their own invoice id, so two invoices with the same reference stay separate. An invoice marked Paid in FreeAgent ends its chase and reads closed, never Paid, because FreeAgent does not say how much was received.Sage
Connect: OAuth. Sage 200 asks you to choose Sage 200 Standard Online or Sage 200 Professional / Extra Online; your site and company are found after sign-in. The signed-in user needs Sage 200 API access and Company Access. Hive reads: contacts, sales and purchase invoices, bank accounts. Ask and workflows read Sage Accounting customers and suppliers, sales invoices (one in full, with its lines and notes) and purchase invoices directly. Ask can also read bank transactions since a date, journals, ledger accounts, tax rates and which businesses the connection covers. A connection with several businesses is read for its lead business, except the bookkeeping status read: for each client business your Sage login reaches (up to 8, or the ones whose name you give), the number of unpaid sales invoices and unpaid purchase invoices and each bank account’s balance, in one answer. Sage’s API does not give unmatched bank-feed lines; Ask says so. Actions: create, update or delete a contact; create a sales invoice (saved in Sage, not emailed) or a purchase invoice, coded to a ledger account with a VAT rate, due date and reference, with the supplier invoice from an Outlook email attached to it (see below); record a customer payment against a sales invoice; create a sales quote with an expiry date; create a credit note against a sales invoice; void a sales invoice with a reason (Sage keeps it, voided, with the reason; a draft is deleted instead; the highest-risk tier). Quotes and credit notes are saved in Sage, not emailed, and a credit note refunds nothing. Starts workflows: a Connected app event trigger on Sage Accounting starts when a sales invoice is created or paid, or a purchase invoice is created, checked about every 15 minutes.FreshBooks, Zoho Books, Zoho Invoice, Exact Online, MYOB, Wave and Fortnox
Ask, agents and workflows can read and act in these accounting apps through your own connection. The approval cards and workflow triggers are rolling out to workspaces gradually. Connect: OAuth, as each app’s own user. Exact Online asks for your country’s site (for examplenl, be or co.uk); MYOB connects one company file. Hive reads only what that user can see.
Hive reads:
Actions: each waits for your approval on a card.
- Reminders go only to the customer’s own addresses. A FreshBooks, Zoho or Wave reminder goes to at most five addresses, each one a read of that client or invoice returned and, as for any email Hive sends, one you named in the chat or a contact already on your records. The card lists them. An email to a customer cannot be unsent, so these cards are the highest-risk tier.
- Recording a payment moves no money. It records money you have already received, applied to the one invoice the card names.
- Not offered: deleting or voiding invoices, and paying bills. MYOB has no draft invoices, so a MYOB invoice is created open (MYOB emails nothing) and is not changed afterwards. Exact Online has no reminder or payment call Hive can use, Fortnox emails invoices only through a request Hive does not send, and Wave’s API cannot change an invoice or apply a payment to one.
Twinfield connects, but Hive cannot read it or act in it yet: its API takes your sign-in
inside each request’s message body, which Hive’s guarded connection does not send.
Attach the invoice or receipt from an email
Ask Hive to create a QuickBooks bill, a Sage purchase invoice or a FreeAgent expense from the supplier invoice or receipt attached to an Outlook email, for example “Create a QuickBooks bill from the supplier invoice attached to the Outlook email from Paper Co, coding it to Office supplies.” Hive reads the email’s attachments from your own Outlook connection, and you get one approval card for the record and its file. The card shows the file name, its size and the email’s subject, next to the supplier, account and other details the record is created with.- Which files: PDF, JPEG or PNG file attachments, up to 10 MB (FreeAgent takes up to 5 MB). None of the three apps accepts HEIC photos, so Hive asks you to save one as a JPEG or PNG first. Links, Outlook items and other file types are refused.
- Checked before anything is created: when you approve, Hive reads the attachment again. If its name or size changed, the email’s subject no longer matches, or the file is not really a PDF, JPEG or PNG, nothing is created and the receipt says why.
- How it is attached: FreeAgent receives the receipt with the expense in one request. QuickBooks and Sage first create the bill or purchase invoice, then Hive uploads the file to it.
- If the attach fails: the bill or purchase invoice still exists. The receipt says it was created without the file, and Hive does not create it a second time. Attach the file in QuickBooks or Sage yourself.
Actions in Business Central, e-conomic, Tripletex and Avalara
Hive already reads these apps: see Apps Hive reads live. It can also make a small set of changes in them. None of these changes can be undone from Hive, so in Ask and Signals each one waits on an approval card for a member to approve, even on Act.- Only records Hive read. The company, customer or AvaTax company an action names must be one Hive read from your account in the same chat or run, so Hive never acts on a guessed id. That is why a workflow’s Action step offers only e-conomic and Tripletex customer creation: the other actions name a record, so they run from Ask and agents, which read it first.
- Drafts stay drafts. A Business Central sales invoice is saved unposted, with no lines. Add the lines and post it in Business Central. Hive never posts, approves, pays or sends an invoice in these apps.
- e-conomic needs the customer group, VAT zone and payment terms numbers your agreement uses. Hive takes them from an existing customer, or you give them.
- Permissions. These actions use the same connection as the reads, so the key, token or app registration must be allowed to write customers (and, in Business Central, sales invoices). If you connected with a read-only permission set, the app refuses the action. Give the connection write access, or reconnect with a key that has it.
Dynamics 365 Finance and Operations
Hive reads customers and sales orders live (see Apps Hive reads live) and can create a customer in a legal entity, after a member approves the card, even on Act. Give the legal entity (for exampleusmf), the customer’s name, and the customer group and sales currency an
existing customer uses; an address is optional. Finance and Operations numbers the new customer
account. Hive never creates orders, invoices or journals there.
The app registration Hive connects with must have a security role that can create customers. A
read-only role is refused.
NetSuite
Hive reads NetSuite customers and invoices: see Apps Hive reads live. It can also create, update or delete a customer, after a member approves the card: see Actions in billing, ERP and spend apps. Starts workflows: a Connected app event trigger on NetSuite starts when a customer or an invoice is created, checked about every 15 minutes. All of this works whichever way NetSuite was connected: OAuth, token-based (TBA) or client credentials. See One app, several sign-ins.Workflow triggers in billing and contract apps
A Connected app event trigger can also start a workflow from these apps. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it.Actions in billing, ERP and spend apps
Hive reads these apps live (see Apps Hive reads live) and can also make changes in them. Hive cannot undo any of these changes, so in Ask and Signals each one waits on an approval card for a member to approve, even on Act.- Hive never moves money. None of these actions charges a card, records or makes a payment, refunds, transfers or adds bank details. A Razorpay order is only something a customer can pay later, and a Brex vendor or Pennylane supplier is created without payment accounts.
- Drafts stay drafts. A Xero or Pennylane invoice is saved as a draft that nobody receives. Finalise it in the app; sending it is a separate action with its own approval.
- High-impact actions. A delete, a cancellation, a void, a pause or resume, or an invoice email is a high-impact action: the card says what changes and who receives the invoice, and nothing happens until a member approves it. Chargebee, Paddle and Maxio cancel at the end of the current term or billing period unless you ask for now (Paddle only), and a Zuora cancellation never invoices or collects. A Paddle resume continues the subscription’s current billing period rather than starting a new one, so it charges nothing now; Paddle refuses it once that period has ended.
- Only records Hive read. An update, delete, note, cancellation or invoice action names a record Hive read from your account in the same chat or run, so Hive never acts on a guessed id. A Xero action also names the Xero organisation Hive verified for the connection. A workflow’s Action step therefore offers only the creates that name no existing record. The other actions run from Ask and agents, which read the record first.
- Values your account already uses. A Cin7 Core customer needs the currency, payment term,
receivable and revenue accounts and tax rule an existing customer uses; Acumatica needs the
Default endpoint version your reads use (for example
24.200.001). Hive takes them from a read, or you give them. - Permissions. These actions use the same key, token or app as the reads, so it must be
allowed to write: for example a Chargebee full-access key, a Paddle key with the customer and
subscription write permissions, the Xero custom connection’s
accounting.contactsandaccounting.transactionsscopes, a Pennylane token withcustomers:allandcustomer_invoices:all, the NetSuite role’s customer permission, the SAP ConcurEXPRPTscope, or a Coupa client with the supplier write scope. A read-only key, role or scope is refused by the app: give the connection write access, or reconnect with one that has it.
Actions in Checkout.com and SAP Business One
Hive reads these apps live (see Apps Hive reads live) and can also make these changes. Each one waits on an approval card for a member to approve, even on Act.- No payment actions. Hive never captures, voids or refunds a Checkout.com payment, and never creates a payment link.
- Disputes take two steps. Saving evidence does not send it. Submitting the evidence, or accepting a dispute, is a high-impact action that cannot be changed afterwards: when you accept a dispute, you lose the disputed amount.
- Only records Hive read. A customer update or delete names a customer from a payment Hive read, and a dispute action names a dispute Hive read. A workflow’s Action step offers only the creates.
- SAP Business One creates only. Hive does not yet update partners, add activities or save draft documents in SAP Business One, because it cannot yet tie those changes to a record it read.
- Permissions. A Checkout.com secret key needs the scopes that let it write customers (Vault) and act on disputes. The SAP Business One user needs authorisation to create business partners.
DocuSign
Connect: OAuth. Hive reads: templates, envelopes and recipients. Actions: send an envelope from a template; send a SharePoint file for signature; void an envelope; resend an envelope, which emails a reminder to every recipient who has not signed yet; correct a signer’s email and resend, which changes the address of a signer Hive read on the envelope and has DocuSign email the envelope to the new address. Sending, resending and correcting are marked high-risk and always wait for your approval; the correction card shows the envelope id, the signer, the recipient id and the new address. Saving a completed envelope’s documents to SharePoint is not available yet. Send a SharePoint file for signature: “Create a DocuSign envelope from Engagement letter.pdf with signature fields for bob@client.com and send it” is one card. It shows the file and the SharePoint folder it is in, the signer and the email subject. When you approve, Hive reads the file from your own SharePoint connection, checks it is still that file in that folder, checks its contents really are a PDF or Word document (up to 10 MB), and sends the envelope with a signature field for the signer on the first page. DocuSign emails the signer at once, so the signer’s address is held to the same rule as any email recipient. Send a Library file for signature: the same card for a PDF or Word file in your Hive Library. A file attached to a chat can be sent once it is saved to the Library. Hive offers it only for a file your Library listing showed in the same chat, and when you approve it reads the file with your own Library access, checks its name and contents, and sends it as above.Workflow triggers in more finance, spend and contract apps
A Connected app event trigger can also start a workflow from these apps. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it.Workflow triggers in Coupa
A Connected app event trigger can also start a workflow from Coupa when an invoice is created, approved or disputed. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it. The events carry the invoice id and number, its status, supplier, total, currency and dates.Workflow triggers in fulfilment, studio, subscription and tax sandbox apps
A Connected app event trigger can also start a workflow from these apps. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it.
IDS Fulfillment and Mindbody note what is there on their first check and start nothing. The events
never carry a customer’s name, email, phone or address, appointment notes, payment details or
cancellation feedback.
Workflow triggers in venue booking and post-purchase survey apps
A Connected app event trigger can also start a workflow from these apps. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it.
The events carry ids, statuses, amounts, offerings and dates. They never carry a guest’s or
shopper’s name, email or phone, a booking’s notes, an invoice’s memo or a survey’s answers.
Workflow triggers in accounting and app-store billing apps
A Connected app event trigger can also start a workflow from these apps. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it.
The events carry ids, document numbers, statuses, amounts, app names, shop domains and dates. They
never carry a contact’s name, an invoice’s notes or a merchant’s contact details.
Workflow triggers in Dynamic Mockups
A Connected app event trigger can also start a workflow from Dynamic Mockups when a collection is created or updated, or a mockup template is added to My Templates. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it. The events carry ids, names and counts, never a template’s image links.Push events from proposal tools
Proposal and practice tools such as Ignition, Go Proposal or Figsflow often lack an API Hive can connect to. Point a Zapier or Make automation at an incoming webhook and sendproposal.created, proposal.won and client.created events — Hive turns them into
Brain facts and signals.
Actions in fund accounting, agent card, expense, payroll and MSP apps
Hive reads these apps live (see Apps Hive reads live) and can also make changes in them. Hive cannot undo any of these changes, so each one waits on an approval card for a member to approve, even on Act.- High-impact actions are in bold. They post to the ledger, let a card spend or stop it, change what a client is billed, cancel or delete, so their cards are marked high-risk and say what will happen.
- Hive never moves money. It never funds a wallet or a user, transfers between wallets, runs or approves a payroll, or reimburses anyone: marking a Rydoo expense reimbursed only records a payment you made. An Agentcard top-up raises the card’s limit from your company balance, and Hive sends it with a one-time key so a retry never tops up twice.
- Balanced ledger documents. A MIP document’s lines must balance (debits equal credits), each line names its GL account and other segments, and dates are MM/DD/YYYY.
- Payroll stays out of reach. In Check, Hive works only with employer companies and workplaces. It never touches employees, contractors, pay, bank accounts or payrolls.
- Only records Hive read. An action on an existing session, document, card, expense, company, workplace, contact or subscription names one Hive read from your account in the same chat or run. A workflow’s Action step therefore offers only the creates that name no existing record (a MIP session, a Rydoo project, a Check company or a Pax8 company); the others run from Ask and agents. A new or replaced Pax8 contact email is checked like an email recipient. Replacing a Pax8 contact replaces its primary roles (Admin, Billing, Technical) too, so the card lists the roles it keeps, and says when it will have none.
- Not offered. Hive never places a Pax8 order (each product needs its own provisioning details), sets up Check bank accounts or onboarding, rejects a Rydoo expense, creates a Rydoo user or trip, or simulates an Agentcard charge.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to write: a MIP user with General Ledger, Accounts Payable and Accounts Receivable entry rights, an Agentcard company credential, a Rydoo API client with write access, a Check API key, and a Pax8 partner credential that can manage companies and subscriptions. A read-only key or role is refused by the app.
- Not yet available. Yokoy actions are under Actions in ERP, personal finance, spend, commerce, booking and ad measurement apps.
Actions in ERP, personal finance, spend, commerce, booking and ad measurement apps
Hive reads these apps live (see Apps Hive reads live) and can also make these changes from Ask, agents and a workflow’s Action step. Hive cannot undo any of them, so each one waits on an approval card for a member to approve, even on Act.- High-impact actions are in bold. They delete or cancel, ship goods, message a driver company, or can have Mindbody email your clients, so their cards are marked high-risk and say what will happen. An ONLOGIST cancellation can carry ONLOGIST’s cancellation fee.
- Hive never moves money. No payment, payout or refund is offered. Hive never cancels a SHOPLINE order (a cancellation can refund the customer’s payment), never gives a Sage Intacct vendor bank or payment details, and a Finta budget move only changes planned amounts.
- Quiet by default. A Mindbody reschedule, class cancellation or teacher change emails clients or staff only if you ask.
- Only records Hive read. An action on an existing customer, account, category, budget, cost object, product, order, transfer, mockup, appointment, class or campaign names one Hive read from your account in the same chat or run. A workflow’s Action step therefore offers only the creates that name no existing record; the others run from Ask and agents. IDS Fulfillment shipments, items and lot statuses use the SKU and lot codes you name, because its reads do not return record ids. A new or changed Sage Intacct customer or vendor contact email is checked like an email recipient.
- Not offered. Hive never posts invoices, bills or journal entries in Sage Intacct, creates Yokoy suppliers or users, uploads a Dynamic Mockups Photoshop file, or changes Mindbody client records, bookings or sales.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to write: a Sage Intacct web services user with create, edit and delete permission on Accounts Receivable, Accounts Payable and General Ledger, a Yokoy API client with write access, and a Mindbody staff user token that can manage the schedule. A read-only credential is refused by the app.
- Not available. Rock Gym Pro’s, ShopWorks ManageOrders’ and Kno Commerce’s APIs offer no changes Hive could make, and Zigpoll’s connection is read-only, so Hive only reads it. Gainsight Customer Communities actions are under Actions in apps Hive used to only read. Hive does not yet act in ROLLER, Syncore or BrightCrowd, whose write APIs could not be checked against a published reference.
Actions in Odoo, ePost KLARA and Anrok
Hive reads these apps live (see Apps Hive reads live) and can also make these changes from Ask, agents and a workflow’s Use a connected app step. Each one waits on an approval card for a member to approve, even on Act.- High-impact actions are in bold. They delete, cancel or void, confirm an order (which creates its deliveries), deliver an invoice to a customer by email, eBill or post, or change the tax Anrok reports, so their cards are marked high-risk and say what will happen.
- Quiet by default. An Odoo note is internal and reaches no follower, an Odoo cancellation emails nobody, and an Odoo invoice stays a draft: Hive never posts it.
- Only records Hive read. An action on an existing contact, order, invoice, customer, article or transaction names one Hive read from your account in the same chat or run. A workflow’s Use a connected app step therefore offers only the creates that name no existing record; the others run from Ask and agents. A new or changed Odoo contact email, and a KLARA customer or contact email, is checked like an email recipient.
- Not offered. Hive never posts an Odoo invoice or registers a payment, writes Odoo users or access rights, books KLARA journal entries or payslip items, creates KLARA invoices, or uploads Anrok exemption certificates.
- Permissions. These actions use the same key as the reads, so its user must be allowed to write: an Odoo user with Contacts, Sales and Invoicing rights, and a KLARA company user with the FINANCE permission. A read-only key is refused by the app.
Actions in apps Hive used to only read
Hive already read these apps live (see Apps Hive reads live). It can now also make these changes from Ask and agents. Each one waits on an approval card for a member to approve, even on Act. These approval cards are rolling out to workspaces gradually.- High-impact actions are in bold. A rejection goes back to whoever submitted the item, an out-of-stock item disappears from ordering, a maintenance window silences a device’s alerts, and pausing or resuming a campaign changes who gets email, so their cards are marked high-risk and say what will happen.
- Only records Hive read. Every action names a record Hive read from your account in the same chat or run: a company, contact, transaction or attribute, a menu item, an item waiting for approval and its rejection reason, an idea and its status, a Wise profile, a workspace and dataset, a Tableau site, workbook or data source, a document or control, an alert or device, or a campaign. So none of these is offered as a workflow’s Use a connected app step; they run from Ask and agents.
- Not offered. No money moves: Hive never creates a Wise transfer, recipient or balance move, and never creates an Embat payment or payment order or adds bank details to a contact. Hive never approves a Fieldglass item, because approving one commits your firm’s spend. Hive never deletes anything here, never creates a Toast order, never reboots a NinjaOne device, runs a script or installs patches, never stops a Smartlead campaign for good, and never starts a new campaign.
- Permissions. These actions use the same connection as the reads, so it must be allowed to write: Toast’s stock:write scope, a Fieldglass integration user who can act on approvals, a Gainsight Communities API client with write scope, a Power BI sign-in with Dataset.ReadWrite.All, a Tableau user who can refresh the content, Vanta’s write scope, a Drata key with Create Control Note permission, a NinjaOne API client with the management scope, and an Instantly key with campaigns:update. A read-only connection is refused by the app, and Hive tells you so.
- Not yet available. Hive does not yet act in SAP S/4HANA Cloud (its OData writes need a session-bound security token Hive cannot carry between requests), Oracle Fusion Cloud HCM (its position and job records change by effective date, through keys its reads do not return) or UKG Ready (no published write Hive could check), so it only reads them.
More actions from the use-case checklist
These approval cards cover rows of the use-case checklist that Hive’s connected apps could already support. Each waits on an approval card for a member to approve, even on Act.- High-impact actions are in bold. A subscription bills a customer, a refund returns money, a GDPR delete cannot be undone, a tag or archive changes who gets campaigns, and a group gives access, so their cards are marked high-risk and say what will happen.
- Only records Hive read. Every action names a record Hive read from your account in the same chat or run: a customer and a price, an order and its payment, a contact, a draft document, an audience and its segment or subscriber, a list, a recycle-bin item, or a group and a user. So none of these is offered as a workflow’s Use a connected app step; they run from Ask and agents. Creating a document library names nothing, so a workflow can do that too.
- Mailchimp never subscribes anyone. A segment or tag only groups people already in the audience: Mailchimp ignores any other address. Hive still never sends, test-sends or schedules a campaign, and does not add subscribers. See Campaign drafts in Mailchimp and Brevo.
- New reads. Ask can now read a Stripe account’s recurring prices, a Shopify order’s payment transactions, a Mailchimp campaign’s report (opens, clicks, bounces and unsubscribes), an audience’s month-by-month growth, its segments and tags, and one subscriber by exact email address, the SharePoint root site’s recycle bin, and, with Microsoft client credentials, one user by sign-in name with their groups and manager, accounts created since a date and disabled accounts. Each reads only the named fields: no phone numbers, addresses or job details.
- Permissions. These actions use the same connection as the reads, so it must be allowed to write: a Shopify app with write_orders, a Microsoft app registration with GroupMember.ReadWrite.All (and User.Read.All for the user reads), and a SharePoint Entra app with Sites.Manage.All to create a library or a column. A read-only connection is refused by the app, and Hive tells you so.
- Not yet available. Hive does not yet add a subscriber to a Mailchimp audience: adding someone to a marketing list needs their consent, and that choice is waiting on a policy decision.
Ideas
- “Which Xero invoices over £5,000 are more than 30 days overdue?”
- A workflow that runs daily, finds overdue invoices and emails each client a polite reminder, like the Fee Reminder template. That template pauses at an Approval showing the whole list, and sends every reminder on it once you approve.
- A weekly summary of Stripe disputes and their evidence deadlines.
Related
Finance and collections
How finance teams use Hive.
Integrations catalog
Every provider at a glance.