In Ask and Signals, the account’s Read, Draft or Act level decides whether
Hive only tells you what it found, prepares the action for your approval or takes it; new
accounts start on Act. See Accounts and autonomy.
Agents and workflows follow the same level: on Act they carry out the actions you select for
them by themselves, and on Draft each waits for approval. Even on Act, an action waits
for your approval when where it sends did not come from you; a reply on the conversation or
ticket it answers is not held
that way — see
What agents and workflows do by themselves.
Even on Act, Ask and Signals hold an action Hive cannot undo for your approval, and of the
actions below only closing or reopening an Intercom conversation and adding Zendesk tags can be
undone. Deletions are permanent in the provider, and Hive flags them as irreversible.
HubSpot
Connect: OAuth. Hive reads: deals (including search), one deal with its pipeline’s stages, one deal’s full timeline, deal owners (every owner by name, email and owner id, or one looked up by email to find your own owner id) and contacts, a contact’s engagement (when they were last contacted, emailed and replied, the next activity, and how many emails, calls, meetings, notes and tasks are logged), contacts, companies, one contact (by id or email) or company with its associated records, tasks, ticket search, properties and property groups, and pipelines.-
Deal search can also narrow to deals with given owners, to open deals only, to deals
changed since a date, to deals created since a date, to deals that entered their current stage
since a date (what moved this week), or to deals with no logged activity since a date (deals
never worked on included), and can sort by soonest close date. Each deal also shows whether it is
closed, when it was created, when notes were last logged on it, its next activity, when it
entered its current stage, and its currency. Ask for more deal properties by their internal name
and each deal shows them too: for example
dealsourceto group deals by source, orhs_date_entered_<stage id>andhs_date_exited_<stage id>to see how long a deal spent in a stage. A search takes at most six filters at once. When a filtered search finds nothing, Hive says no deal matched that filter, never that you have no deals. A deal with no stage set counts as open, and Hive says its stage is unknown rather than treating it as closed. - Search HubSpot for a name with no object named (“Search HubSpot for Acme”) searches contacts, companies and deals together. A contact or company search with no words lists the most recently changed ones.
- Records by a date property lists deals or companies whose date property, such as a renewal or fee review date, falls between two days, soonest first: “Which HubSpot deals or companies have a renewal or fee review date in the next 90 days?” Hive reads your properties to find the field by its internal name, then reads that property again and searches only if it is a date field of that object; a text field that sounds like a date is refused with a note. A window is at most a year.
- Companies by service bought answers “Which HubSpot companies buy bookkeeping from us but not payroll?”: the companies with a deal carrying a line item named for the first service and none for the second, at any deal stage. Hive follows line items to their deals and deals to their companies, at most 100 at each step, and says when a step reached that cap. A cap on the first service means the list may be incomplete; a cap on the second service means some companies listed may already buy it, so check each one before acting on it.
- Search tasks lists your HubSpot tasks, soonest due first: open ones by default, or completed or all of them, narrowed by due date, owner, type (call, email or to-do) or words in the subject. Each task shows its due date, whether it is overdue, its status, type, priority, owner and notes, and the contacts, deals and companies it is on, by name. “Show me my open tasks due today and overdue” is one read.
- Deal timeline shows one deal’s history, newest first: every stage change with the stage it left, and the deal’s notes, emails, meetings, calls and tasks with their text. It shows 25 items at a time; ask for older ones and Hive reads the next page back.
- List owners needs an email address and returns only the owner whose email matches it exactly, so looking up your own owner id never returns someone else’s.
-
Find contacts by email checks up to 100 email addresses at once and gives each one a status:
- found: a contact has the address as its email or one of its additional emails;
- possible match: no contact has the address, but one has the same first and last name as the name the address came with;
- not found: Hive searched for the address in full and found no contact;
- unverified: Hive checked only the main email field. In one lookup Hive searches additional emails for at most 5 addresses.
- List deal contacts returns the contacts on up to 100 deals, with their email addresses (additional ones included).
- Logged notes and emails shows the notes, emails, meetings and calls logged on one contact (by email or id), newest first, with their text; each is cut to 2,000 characters.
- Filter contacts finds contacts whose job title contains a word, whose primary company is in an industry, that have no associated company or no owner, or that are in a lifecycle stage.
- Filter companies finds companies with no owner or no associated contact, optionally in one industry.
- List members lists the contacts in one HubSpot list, up to 100 at a time, with name, email, company, job title and owner, one row each, ready to paste into a sheet.
-
Win rate and deal size by source: ask for deals closed this year with the
dealsourceproperty and Hive works out the win rate and average deal size per source from that read.
dealsource property unless you name your own source property, which the card
then shows next to Deal source. The owner, stage, pipeline and other deal fields cannot be used
as the source property.
Create a company takes a name, domain, industry, phone, number of employees, city and an owner
Hive read from your HubSpot owners, and can link a contact Hive read, so “associate Ada with Beta
LLP, creating the company with the domain beta.example if it does not exist” is one card when
Hive’s read finds no such company. Creating or updating a company can also set any other company
property your HubSpot has, read first like a contact’s or a deal’s.
Merge contacts folds a duplicate contact into the one you keep: HubSpot moves the duplicate’s
activity onto the kept contact and removes the duplicate, and it cannot be undone, so the card is a
high-risk one. Duplicates often share a name, so the card names each contact by its email address
and HubSpot id, both from the same contact Hive read.
Set one property on many contacts sets a single contact property, read from your contact
properties, to one value on up to 100 contacts Hive read, for example every member of a list. The
card lists every contact id it changes. The owner, email address and name are refused: use their
own actions.
Set a parent company makes one company Hive read the parent of another. Add a line item
adds a product to a deal with its quantity and unit price, linked to the product in your product
library when Hive found it there. Name a currency (“price 50 GBP”) and the card shows it and the
line item uses it; otherwise the line item takes the deal’s own currency. Rename a list gives a list Hive read a new name.
Update a deal stage can carry a closed lost reason, so “move the deal to Closed lost because
there is no budget” is one card. “Move the HubSpot deal 123 to Contract sent”, “Set the Acme deal
stage to Closed won”, “Close the Acme deal as won” and “Mark it won” all prepare this card.
Associate records links a contact and a company, a contact and a deal, or a deal and a
company, and can make the company the primary company of the contact or the deal; the old primary
company stays associated without the label. Remove an association unlinks two records; neither
is deleted. To move a contact to a new company, Hive prepares both cards: associate the new company
as primary, and remove the old one.
Log a call records a call on a contact, company or deal, with its notes, outcome (Busy,
Connected, Left live message, Left voicemail, No answer or Wrong number), direction and length.
Log a meeting records a meeting with its start and end, outcome, notes and the HubSpot contacts
who attended; HubSpot sends no invitation. Each attendee the card names is the contact the meeting
is linked to: an attendee whose name and record do not match is refused. Log an email records an email you sent or received
on a contact, company or deal, with its subject and text and no email addresses; nothing is sent.
Naming a contact by its email address (“move the HubSpot contact ada@example.com to Acme”) is a
HubSpot change, not an email: Hive never asks which mailbox to send from.
Several changes in one message, such as “create a contact for the sender, a company from their
domain and a deal, and log the email on the contact”, are separate approval cards: the contact
(with its new company), then the deal. An email is logged only on a contact that already exists,
so approve the contact’s card first, then ask Hive to log the email on it. When Hive cannot
prepare the whole message at once, it says which cards to ask for instead.
Create a note adds a note to a deal or a contact Hive read; the card shows the deal or contact
it is attached to, and the note is dated when it is created unless you give a time.
Create a task adds a HubSpot task with a subject and a due date, and optionally notes, a
type (CALL, EMAIL or TODO), a priority (LOW, MEDIUM or HIGH), an owner, and a contact
and a deal to link it to. The card names the contact and deal; if you name a deal Hive has not read
yet, it searches HubSpot for it first instead of asking you for its id. Update a task marks a task Hive read as complete (or not started),
moves its due date, or replaces its notes, for example with the outcome when you complete it. Set
owner reassigns one deal, contact, company or ticket to a HubSpot owner. Whenever Ask or an agent sets an
owner, on a new contact, a task or an existing record, the owner must be one it read from your
HubSpot owners, and an existing record must be one it read, so a name that matches someone else is
refused rather than guessed. A contact can be named by its email (“Set the owner of the HubSpot
contact ada@example.com to Nina”). The approval card shows the record and the owner by name.
Add a dropdown option adds one choice to an existing dropdown property, such as a new deal
source. HubSpot replaces a property’s whole list of choices when it changes, so Hive reads the
property first and the card keeps every existing choice, hidden ones included; if the choice
already exists, Hive prepares no card. The card names the object (contacts, companies, deals or
tickets) whose property changes, and Hive changes it only on the object it read the property from.
Create an active list makes a list of contacts that keeps itself up to date: contacts whose
company is in the industries and countries you name. The industries are the values of your
company Industry property, which Hive reads first. Create an active list by property or
stage makes one of contacts where a contact property you name equals a value, that are in the
lifecycle stages you name, or that are associated with a deal in the deal stages you name; every
filter you give must match. Hive reads the contact properties or the deal pipelines first. Create
a list makes a static list you add contacts to. A list that does not exist yet is created first:
approve it, then ask Hive to add the contacts, because HubSpot only gives the list its id once it
exists. Add a dropdown option reads the property’s current options itself and keeps them on the
card; it never asks you which options exist or how many there are.
The deals, contacts, companies and owners Hive finds with its HubSpot searches are what a card is
built on, so Hive never asks you for an id it has just shown you.
Merge companies merges a duplicate company into the one you keep. Company names repeat between
duplicates, so the card names each company by its name and domain, both from the same company
Hive read; HubSpot moves the duplicate’s activity and associations to the company kept. A merge
cannot be undone, so the card is high-risk.
Create a quote makes a HubSpot quote for a deal from its line items, valid until the date you
give, on a quote template Hive read from your templates. One card creates the quote as a draft
on the deal and template, then copies every line item of the deal onto it (at most 50; the deal’s
own line items stay as they are). Hive never publishes or sends the quote: do that in HubSpot. If
the line items cannot be copied, the receipt says the draft quote exists without them.
Delete a task, delete a ticket and delete a list each name a record Hive read, by its
subject or name, and are high-risk. HubSpot keeps a deleted task or ticket in its recycling bin. A
deleted list’s contacts are kept, and HubSpot can restore the list for 90 days: the card says so,
and its undo restores it. Remove contacts from a list takes contacts out of a static list; each
contact is named by its email, from the same contact record as its id, and the contacts themselves
are kept. An active list manages its own members, so Hive refuses to remove anyone from one and
says why.
Create a ticket opens a HubSpot ticket, for example from an onboarding or support workflow. It
takes a subject and, optionally, a description (content), a priority (LOW, MEDIUM or
HIGH), a HubSpot contact to link it to, and a pipeline and pipelineStage given as HubSpot
internal ids. Leave both out and the ticket opens in HubSpot’s built-in Support pipeline (0) at its
first stage, New (1). A stage on its own is a stage of that Support pipeline. A custom pipeline
needs its stage too: its stage ids differ from portal to portal, so Hive refuses the step rather than
guess one. Find the ids in your HubSpot ticket pipeline settings. Move a ticket puts a ticket
Hive read into another stage of its pipeline, a stage Hive read from your ticket pipelines. Creating
or moving tickets needs a HubSpot connection that may write tickets; if HubSpot refuses the write,
reconnect HubSpot and grant ticket access.
Change events: when HubSpot tells Hive that a deal, contact, company or ticket in your
connected portal was created, changed or deleted, Hive does not read the event’s content. It reads
your HubSpot deals again through your connection, sooner than the hourly run where it can, and the
hourly run picks the change up at the latest. Events from portals you have not connected are
ignored, and an event Hive cannot verify is ignored too. The events can start a workflow, carrying the record’s id
and the changed property’s name but never its value: see
Connected app event.
Signals: every hour Hive reads your HubSpot deals into your matters and
raises a signal when one needs you — a deal gone quiet, for example. Deal lifecycle is a
separate pilot signal, off by default. When it is enabled for your workspace, Hive watches deals
in your default pipeline — created date, stage and last update — and raises a signal when a
deal stalls. Deals in custom pipelines are not watched by this signal yet.
In Ask: ask Hive to draft re-engagement emails for slipping or overdue deals, for example
“Draft re-engagement emails for the overdue HubSpot deals”. Hive counts only what it read live
from your connected HubSpot account as deal material, including the contacts’ email addresses it
drafts to. When you name HubSpot or pin a HubSpot connection, Hive reads HubSpot before it drafts;
a deal the Business Brain remembers — even a fact learned from HubSpot —
never stands in for that read. Hive reads the deals first and then, when they carry no email
addresses, the contacts on them. When those reads do not give Hive an address to write to, it
prepares no re-engagement emails and does not draft from anything else it knows. Asked to
draft, Hive writes the emails as drafts in your Gmail or Outlook (the one you name, or the only
one connected; with both connected it asks which) and never sends them; asked to send, it lines
up sends for your approval. What it replies:
- No matching deals. HubSpot answers, but no deals match: Hive says it could not find matching HubSpot deals in the selected account.
- The deal read fails. HubSpot is disconnected, or the read times out or errors: Hive says it could not read HubSpot deals, never that there are none. One exception: when you pinned a HubSpot connection, Hive first reads it for your request as a whole, and a read at that stage that times out or errors ends the request as Ask failed.
- HubSpot refuses the deal read. The request ends as Ask failed.
- The contact read fails. Hive says it found the HubSpot deals but does not yet have contact emails on them.
- HubSpot refuses the contact read, for example because the connection may read deals but not contacts. The request ends as Ask failed.
Salesforce
Connect: OAuth. Hive reads: SOQL and SOSL queries, record detail, field metadata, users and the current user. Find people by email checks up to 100 email addresses against your contacts, then against your unconverted leads, and returns each match’s name, company and record id, or not found. When Salesforce returns too many rows for Hive to be sure, the address is unverified instead. List opportunities also shows when each opportunity’s stage last changed, and can narrow to opportunities whose stage has not moved since a date. Opportunity stage history lists the stage changes since a date, newest first, with the stage each opportunity moved from, so “what moved this week” is one read. When there is more history in that window than one read covers, Hive says the older changes were not listed. Actions: create, update or delete (permanent) contacts, opportunities and tasks; create a lead or an account; add a note to a record; log a meeting (an event). A task can be on an opportunity or account, be with a contact or lead, and be assigned to a user, each one Hive read from Salesforce, so the card names the record and the person. Set its kind to Call with the status Completed to log a call. Create a lead takes a name, company, email, phone, title, website, lead source and description. Log a meeting records an event with its start and end on an opportunity or account Hive read, with optional notes, location, contact and assignee; no invitation is sent. Update an opportunity can also set its next step and its amount. Create an account takes a name, website (a bare domain getshttps://), phone,
industry and description. Add a note creates a Salesforce note and links it to an account,
opportunity, contact or lead Hive read; the card shows the record’s name and id. If the note is
created but the link fails, Hive says so and the note stays in Salesforce, unlinked.
Starts workflows: a Connected app event trigger on Salesforce starts when a lead or an opportunity is created, or an opportunity is won, checked about every 15 minutes.
A Salesforce connection made with client credentials or a JWT bearer connected app works
against the org that connected app belongs to and has its own actions, run as its integration user:
see Create, update and delete in more CRM apps.
Its Connected app event trigger starts on the same events as the OAuth connection’s.
Zendesk
Connect: OAuth. Hive reads: ticket search, recent tickets, ticket detail, agents and groups, and each ticket’s metrics: when the customer and the agent last updated it and how long the customer has waited, so “which open tickets have had no agent reply for more than 24 hours” is one read. Actions: reply to the customer on a ticket, add an internal note, create a ticket, assign it to an agent or a group, update status, change priority, add tags, add an email CC to a ticket, create an end user, delete a ticket (permanent). Starts workflows: a Connected app event trigger on Zendesk starts when a ticket is created, changed or solved, checked about every 15 minutes. Reply posts a public comment on the ticket, which Zendesk emails to the requester. Internal note posts a private comment that only your agents see. Changing the status (to pending or solved, for example) is a separate action, so a reply never closes a ticket on its own. See Replies and notes in Intercom and Zendesk. Add a CC copies someone on a ticket Hive read; Zendesk emails them the ticket’s public replies from then on, so their address is held to the same rule as any email recipient. Create an end user adds a customer (never an agent) with their name and email; Zendesk sends them no welcome or verification email, and the card says so. The built-in Ticket Triage workflow template reads new Zendesk tickets every hour, tags each with its urgency and alerts your team to anything urgent. See Workflow templates.Intercom
Connect: OAuth. Hive reads: conversation search and detail, admins, teams and contacts, when you ask. Hive also reads open conversations in the background: when each was created, its priority, state and last update. Background reads cover Intercom workspaces in the US, EU and Australia regions. See When background reads are off. Actions: reply to the customer in a conversation, add an internal note, assign, close or reopen a conversation, snooze a conversation, tag a conversation, create a contact. Open conversations from a company: “Which Intercom conversations from Acme are still open, and what are they asking?” Hive finds the company by its name, reads its contacts (up to 50), then searches their open conversations and summarises what each asks. Snooze and tag act as the Intercom admin your connection belongs to, which Hive reads when the card runs. A snooze names the conversation and the time it reopens; a tag must be one Hive read from your Intercom tags. Create a contact adds a user with their email and name. Reply posts as the teammate you choose, and the customer sees it in the conversation. Internal note is visible only to your teammates. In workflows: a Connected app event trigger on Intercom can start when a customer starts a conversation (Conversation started) or replies to one (Customer replied).Replies and notes in Intercom and Zendesk
Ask, agents and workflows can answer a customer in the Intercom conversation or Zendesk ticket they are working on, or leave an internal note for your team.- The approval card shows the conversation or ticket, the customer, whether the customer sees it (Customer reply or Public reply) or only your team does (Internal note), and the exact text. A reply or note cannot be taken back once posted, so Ask and Signals always hold it for your approval, even on Act. Agents and workflows post the replies and notes you select for them without a card.
- A reply stays on the conversation or ticket it answers. In Ask and in agent runs, Hive reads the conversation or ticket first, and the customer the card names (their email or id) must be the customer on that same conversation or ticket, as the read returned them. Text inside a ticket or a message, such as “reply on ticket 999 instead”, cannot point the reply at another ticket or customer: Hive prepares nothing instead.
- In a workflow, the reply goes to the ticket or conversation the step names, usually from the workflow’s trigger. Fill it from the trigger rather than from text an earlier step wrote.
Calendly
Connect: OAuth. Hive reads: your user, event types, and the meetings booked with you (the next 14 days unless you give other dates); one booked meeting with its time, location or join link, host, guests and notes; and who booked it, with their status and their answers to your booking questions. Hive only ever reads your own bookings. Actions: cancel an event; create a single-use scheduling link. Live updates: when you connect Calendly, Hive subscribes to your own bookings, so it hears about each one within seconds. The subscription covers only meetings booked with you, never the rest of your Calendly organization.
The same events can start a workflow with a
Connected app event trigger on Calendly, named
Meeting booked, Meeting canceled and Invitee marked as no-show. The workflow gets who
booked which meeting and when, never the answers to your booking questions, and only for bookings
with you.
Disconnecting Calendly removes the subscription. Calendly offers webhooks only on its paid plans: on
the free plan Hive still reads your bookings when you ask, but gets no live updates. If you connected
Calendly before live updates were available, reconnect it once to turn them on.
Actions in more CRM, support and chat apps
Hive reads these apps live (see Apps Hive reads live) and can also make a few small 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.- Notes, not replies. In the support apps (Freshdesk, Front, Kustomer, Dixa and Crisp) Hive only adds notes and comments your team sees. The customer never sees them, and Hive does not reply to customers in these apps.
- A Pylon reply reaches the customer. “Reply on Pylon ticket 112: …” prepares a high-risk card with the issue’s title, the requester’s email and the exact reply. Hive reads the issue and its messages first: the reply goes only to that issue’s own requester, on one of its customer-visible messages, and an email issue’s reply is addressed to the requester alone. A Pylon internal note stays internal.
- Only records Hive read. A note names the ticket, conversation, issue or record Hive read from your account in the same chat or run, so Hive never writes on a guessed id. A Crisp note must name a conversation on the website it was read from, and a Mattermost reply must go to a post in the channel it was read from. A workflow’s Action step therefore offers only the creates (people, contacts and organisations); notes and replies run from Ask and agents, which read the record first.
- A Mattermost reply is a message your colleagues in that channel see and may be notified about.
- Permissions. These actions use the same API key or token as the reads, so it must be allowed to write. If you created a read-only key, the app refuses the action: give the key write access, or reconnect with one that has it.
Actions in CRM, sales and marketing apps
Hive also reads these apps live (see CRM and call recording, Prospecting and market data and Marketing, forms and reviews) and can make a few small 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. A note, comment, update or call change names the contact, deal, lead, company, account or call Hive read from your account in the same chat or run, so Hive never writes on a guessed id. A workflow’s Action step therefore offers only the creates that name no existing record: contacts, accounts, leads and profiles. A Zero company names the workspace Hive read, so it runs from Ask and agents.
- Apollo keeps one contact per email address: creating a contact that already exists returns the existing one instead of a duplicate. An update changes only the fields you name.
- CallRail. The note replaces the call’s current note; tags are added to the ones the call already has. Hive never marks a call as spam, because CallRail cannot undo that.
- Marketing apps never send. In Klaviyo, Mailjet and SendGrid Hive only stores a contact. It does not subscribe anyone, change consent, add them to a list or start a campaign, so no automation is triggered. In SendGrid an email address that already exists is updated with the names you give.
- Permissions. These actions use the same API key as the reads, so it must be allowed to
write. A Klaviyo private key needs
profiles:write, a Lightfield keyaccounts:createandnotes:create, and a SendGrid key access to Marketing contacts. A read-only key is refused by the app: give it write access, or reconnect with one that has it.
HR and recruiting apps
Hive reads HiBob (see Apps Hive reads live) but does not change anything in it yet. In these recruiting and HR apps it can also act, each time after a member approves the card:
The candidate, application, job or project an action names must be one Hive read from your
account in the same chat or run, and a workflow’s Action step offers only
Factorial’s project create. A Lever note can be limited to people with Lever’s
sensitive-information access, and Hive never notifies its followers. Hive never moves, rejects,
archives or contacts a candidate, and stores an applicant’s email address without writing to
them.
Hive can also change these HR, recruiting and learning apps, each after a member approves the
card, even on Act:
- Only records Hive read. An update, a delete, or adding a candidate to a job or project names a record Hive read from your account in the same chat or run. A workflow’s Action step therefore offers only the creates that name nothing existing, such as a new employee, person, department, candidate, leave type or course.
- Personio managers and custom attributes. A manager is an employee Hive read, and a custom attribute is one your Personio API credential lists under its employee attributes (Hive reads that list first and sets nothing else), so to give a new hire a manager or a team, Hive creates the employee and then updates them once Personio has them. Hive finds a person by exact work email, or in Personio API v2 by exact first and last name, and reads their position, department, team, manager, office and start date from their employment. It does not read or change absences or time off for this.
- Nobody is emailed by Hive. A Sage HR employee is created without the welcome email and an applicant without the thank-you email, and a Teamtailor candidate added to a job is marked as sourced with notifications off. Check any automations your team set up in Teamtailor or your HR app, which can still react to a new record.
- Deletes need the stronger approval. Deleting a Humaans job role, a Rippling work location, a Timetastic leave type or department, or a TalentLMS course or group is a high-impact action: the card says what is deleted. Deleting a TalentLMS course loses its learners’ progress.
- Not offered yet. Time off, absences, salaries, documents and users need ids Hive does not read from these apps, so Hive does not book leave, change pay or upload documents in them.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to
write. A Humaans token needs
private:write, a Rippling tokendepartments.read-writeandwork-locations.read-write, a Teamtailor key Admin access with read-write, and a Personio credential write access to employees. A read-only key is refused by the app: give it write access, or reconnect with one that has it.
Zendesk with an API token, Gorgias and Aircall
Hive reads these apps live (see Support, phone and meetings) and can also change them after a member approves the card:- Approval every time. None of these can be undone from Hive, so each waits on an approval card, even on Act. Actions in bold are marked high-risk: a Zendesk reply is emailed to the requester the card names, and a deletion removes the record (Zendesk keeps deleted tickets restorable for 30 days; Gorgias and Aircall do not).
- Only records Hive read. A note, reply, status, tag, comment or deletion names the ticket, contact or call Hive read from your account in the same chat or run. A workflow’s Action step offers only the creates: Zendesk tickets, Gorgias customers and Aircall contacts.
- Aircall contacts are shared with every user in your Aircall company.
- Permissions. These actions use the same API key or token as the reads, so it must be allowed to write.
Create, update and delete in more CRM apps
Hive reads these apps live (see CRM and call recording and Marketing, forms and reviews) and can also create, update and delete records 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.- Only records Hive read. An update, delete, note, comment or task names a record Hive read from your account in the same chat or run, so Hive never writes to a guessed id. A workflow’s Action step therefore offers only the creates that name no existing record, such as a new account, company, person or lead. The other actions run from Ask and agents, which read the record first.
- Deletes need the stronger approval. A delete, creating a Marketo lead or adding one to a list is a high-impact action: the card says what changes and nothing happens until a member approves it. Salesforce moves a deleted account to its recycle bin and Twenty keeps deleted records restorable, but the other apps delete for good. Removing an Affinity list row leaves the organisation or person itself in place.
- Names and amounts. A Twenty update that changes a name gives both the first and last name, and an amount always comes with its currency. A Streak note update replaces the box’s notes. An Affinity person update replaces the person’s email list.
- Marketo. Hive never sends a Marketo email or schedules a campaign. Creating a lead, or adding one to a static list, can still start a smart campaign your team set up to listen for it, so check your triggers before you approve. Because such a campaign can email the new lead, the approval card treats its address like an email recipient: it names the address and says where it came from, such as typed by you or written by Hive, so you can check it before you approve. Creating a lead never changes one that already has the email address: change an existing lead with an update, which names a lead Hive read.
- Permissions. These actions use the same connection as the reads, so it must be allowed to
write. The Salesforce integration user needs edit access to accounts, contacts, opportunities,
cases and tasks. A Twenty key needs a role that can edit records, a Sellsy API access the
matching
.writescopes (such ascompanies.write), and the Marketo API user a role with Read-Write Lead. 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 commerce, subscription, returns and review apps
Hive reads these apps live (see Apps Hive reads live and Marketing, forms and reviews) and can also make these changes. Each one waits on an approval card for a member to approve, even on Act.- No refunds. A Shopify or Shopware cancellation refunds nothing and emails nobody, a WooCommerce status change cannot mark an order refunded, and an Adobe Commerce cancellation only works on an order that has not been invoiced. Hive does not cancel VTEX orders (a VTEX cancellation refunds the payment) or process Loop returns (processing issues the refund or exchange). A WooCommerce status change can send WooCommerce’s own order email (for example Completed order) to that order’s customer if your store has it turned on, so it needs the stronger approval. Order notes and comments stay private to the shop, a new Shopify customer gets no account invite, and a new commercetools customer has no password.
- Drafts stay drafts. A Shopify draft order, and a new Shopify or WooCommerce product, is saved as a draft that no shopper sees.
- Shopify prices are per variant. Changing a product’s price sets each variant you name (all of them, unless you say) to the new price in one update. The card shows each variant’s old and new price, the old one as Hive read it; Undo puts the old prices back. Compare-at prices and stock are left alone.
- High-impact actions. A delete, a cancellation, a Recharge or Stay AI reactivation or billing date change, resuming a Stay AI subscription, closing a Loop return, and a public review reply need the stronger approval. A reactivation never charges now; charges resume on the next scheduled date. Hive does not place an immediate Stay AI order. A Judge.me reply does not email the reviewer.
- Only records Hive read. An action on an order, product, customer, subscription, return or review names one Hive read from your account in the same chat or run. A commercetools change also sends the version that read returned, so the app refuses it if the record changed since. A workflow’s Action step therefore offers only the creates. The other actions run from Ask and agents.
- Permissions. These actions use the same token or key as the reads, so it must be allowed to
write: for example the Shopify
write_orders,write_customers,write_productsandwrite_draft_ordersaccess scopes, a WooCommerce key with Read/Write permission, a commercetools client withmanage_customers,manage_ordersandmanage_products, or a Trustpilot business user who can reply to reviews. A read-only key or scope is refused by the app.
Actions in call, shipping, marketing, form and analytics 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. Each one waits on an approval card for a member to approve, even on Act.- No postage, calls or broadcasts. Hive never buys a shipping label, voids one, adds carrier funds, places a CloudTalk call or SMS, or sends a Braze campaign to a whole segment. An EasyPost shipment only fetches rates, and a ShipStation order marked shipped notifies neither the customer nor the store.
- Nothing sent quietly. A new beehiiv subscriber gets no welcome email, a Listrak subscription sends no double opt-in email, and a Swoogo registrant gets no confirmation email. A new Typefully draft stays a draft until you approve a separate publish card. The address of a new beehiiv subscriber, Listrak list member, Swoogo registrant or Gong meeting invitee is checked like an email recipient: it must be in your workspace directory, typed by you, or set by the workflow.
- High-impact actions. A delete, a cancellation, a Braze send, a Gong meeting (Gong may send it to the invitees), a new beehiiv subscriber or automation enrolment, a new Listrak list member, a new Swoogo registrant, publishing a Typefully draft or replacing its text (a scheduled draft publishes the new text), and a Fillout submission (the form’s own notifications and integrations run) need the stronger approval.
- Only records Hive read. An action on a call, conversation, contact, task, shipment, order, list, campaign, subscriber, draft, registrant, form, submission or survey names one Hive read from your account in the same chat or run. A workflow’s Action step therefore offers only the actions that name no existing record (such as a new contact, tag, address or event type); the others run from Ask and agents.
- Permissions. These actions use the same key or token as the reads, so it must be allowed to
write. For example, a Jotform key needs Full Access, a Braze REST key needs
campaigns.trigger.sendandcanvas.trigger.send, a beehiiv key needs the matching:writescopes, and a Swoogo or Listrak client needs write access to the records it changes. A read-only key is refused by the app. - Not yet available. Hive does not yet act in Ordinal (its write API could not be checked against a published reference), or in SurveyMonkey (Hive’s connection asks for read access only). Cyberimpact actions are under Actions in insurance CRM, wealth, email marketing, knowledge base and ecommerce analytics apps.
Actions in commerce, CRM, meeting, phone-agent, form and feedback 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. Each one waits on an approval card for a member to approve, even on Act.- No refunds, calls or new accounts. Hive never refunds an order or a transaction, cancels a Back Market order (that refunds the buyer), places an AgentLine call or text, buys a phone number, or creates a ThriveCart affiliate or course student. It never changes a ThriveCart customer’s sign-in email, sets an AgentLine agent’s owner phone or transfer number, shares a Bliro call by link, or sends a SureContact campaign or email.
- Nothing sent quietly. Your SureContact automations may email a contact, so the address of a new SureContact contact, or a contact’s changed address, is checked like an email recipient: it must be in your workspace directory, typed by you, or set by the workflow.
- High-impact actions. A delete, a ThriveCart subscription cancellation, pause or resume, a Back Market order marked shipped (the buyer is told), a new SureContact contact, list member or automation start, a change to what an AgentLine agent says, moving a number to another agent, hanging up a call and releasing a number need the stronger approval.
- Only records Hive read. An action on an order, listing, care folder, subscription, affiliate, company, contact, property, work ticket, deal, task, note, meeting, call, agent, number, project, form, submission or response names one Hive read from your account in the same chat or run. To make that possible Hive now also reads ThriveCart affiliates, Sellercloud’s customer service statuses, and SureContact tags, lists and automations. A workflow’s Action step therefore offers only the actions that name no existing record (such as a new company, contact, tag, project or agent); the others run from Ask and agents.
- Permissions. These actions use the same key or token as the reads, so it must be allowed to write: for example a SureContact key with the write and delete abilities, a Sellercloud user with edit rights on orders, or an Aspire API user whose role can edit companies, contacts and opportunities. A read-only key is refused by the app.
- Not yet available. Hive does not yet act in TapClicks (its write API could not be checked against a published reference), Zigpoll (Hive’s connection uses a read-only key), or Facebook (Hive’s connection asks for read permissions only). PostHog’s actions are listed under PostHog.
Actions in email, WhatsApp and SMS marketing 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. Each one waits on an approval card for a member to approve, even on Act.- High-impact actions are in bold. They send email, WhatsApp or SMS that cannot be recalled, add people to a list campaigns go to, stop an automation, or delete, so their cards are marked high-risk and say what will happen. A Postscript custom event can start a flow that texts the subscriber.
- Only people Hive read. A message goes only to a Chatarmin contact or Postscript subscriber Hive read from your account in the same chat or run, and a new Emarsys contact’s or list member’s address is checked like an email recipient: it must be in your workspace directory, typed by you, or set by the workflow.
- No consent Hive was not given. A new Chatarmin contact is recorded with no marketing consent, and a change can only clear consent or opt the contact out. Hive never subscribes a phone number to Postscript SMS.
- Not offered. Hive never deletes an Emarsys contact (Emarsys finds a contact only through a lookup Hive does not send), launches a campaign to a broadcast list, creates an Emarsys administrator or key, uploads Chatarmin voucher codes, or sets a webhook.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to write: an Emarsys API credential with contact, contact list, email campaign and automation write access, a Chatarmin API key and a Postscript shop API key. A read-only credential is refused by the app.
- Not yet available. Hive does not yet act in Redtail CRM, whose write API could not be checked against a published reference. AgencyZoom actions are under Actions in insurance CRM, wealth, email marketing, knowledge base and ecommerce analytics apps. Chili Piper actions are under Actions in print-shop and meeting scheduling apps. Avoma, Clari Copilot, Jiminny and Attention actions are under Actions in meeting recorder, call intelligence and support apps.
Actions in meeting recorder, call intelligence and support 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. Each one waits on an approval card for a member to approve, even on Act.- High-impact actions are in bold. They record other people in a meeting, post where other people see it, reply to a customer, or delete, so their cards are marked high-risk and say what will happen.
- Bots join only the meeting you name. A Recall.ai or Glyphic bot joins a meeting link you type, or a Recall.ai calendar event Hive read from your account. A bot’s chat message goes to a bot Hive read.
- Only records Hive read. An action on an existing meeting, conversation, label, team, scorecard, group, record, tag or article 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. An Atlas reply is sent as the conversation’s assigned agent. A new or changed Atlas customer email and a Momentum meeting host are checked like an email recipient.
- Quiet by default. An imported Jiminny call emails its host only if you ask, a Momentum import runs summaries and AI signals only if you ask, and an Attention label change does not re-run CRM intelligence unless you ask.
- Not offered. Hive never creates API keys, webhooks, users or SCIM users in these apps, uploads a recording file, runs their AI assistants on your behalf, or deletes a Demodesk recording (Demodesk names a recording by a token Hive does not treat as a record id).
- Permissions. These actions use the same key as the reads, so it must be allowed to write. Attention’s scorecard changes need an organisation-level key, and a Demodesk group or company vocabulary change needs a company admin’s key. A read-only key is refused by the app.
Workflow triggers in more support, CRM, meeting and form 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 feedback, subscription, booking, social publishing and affiliate apps
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, show something on a public Canny board or changelog, change when or whether a Skio customer is charged, or stop a post that was due to go out, so their cards are marked high-risk and say what will happen.
- Quiet by default. A Canny status change or comment never emails voters, and a Skio cancellation never emails the customer, unless you ask. A Canny changelog entry is created as a draft that notifies nobody.
- Only records Hive read. An action on an existing post, board, category, tag, changelog entry, user, subscription, label, idea or business unit names one Hive read from your account in the same chat or run, so a Canny post or vote is made as a user a post read returned. 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.
- Not offered. Hive never charges a Skio customer at once (ship now), sets a payment method or creates a subscription; never writes Canny users or companies or merges posts; never writes Ordinal post text (Ordinal publishes no request format for it); and never changes Everflow offers, partners, payouts or conversions.
- Not yet available. Hive does not yet act in Prive, Fairing, Redtail CRM, ROLLER, Syncore, BrightCrowd or TapClicks: their write APIs could not be checked against a published reference or offer no changes Hive could make. SAP Fieldglass rejections are under Actions in apps Hive used to only read. Pushpay ChMS, Konnektive and EvaluAgent actions are under Actions in dashboard, contact-centre QA, payroll, ecommerce CRM, church and customer data apps. Addepar, Triple Whale, AgencyZoom and Cyberimpact actions are under Actions in insurance CRM, wealth, email marketing, knowledge base and ecommerce analytics apps; Holded, Grain and Yotpo actions are under Actions in accounting, staffing, learning, meeting recorder, file sharing and reviews apps.
Actions in print-shop and meeting scheduling apps
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, and a deleted Chili Piper meeting type stops every scheduling link that uses it, so their cards are marked high-risk and say what will happen. Setting a meeting type inactive is the reversible alternative.
- Recipients checked. ShopVox emails quotes, proofs and invoices to a company’s contacts, so a new contact’s email address is held to your workspace’s send rules and named on the card.
- Only records Hive read. An action on an existing company, sales order, workspace or meeting type 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.
- Not offered. Hive never records a ShopVox payment, changes a sales order’s prices, taxes or state, or uploads a signature. It never cancels a booked Chili Piper meeting or marks a no-show (Chili Piper publishes no request format for them), sends or attaches a reminder, or changes users, teams, routers or scheduling links.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to write: a ShopVox login on a plan with API write access, and a Chili Piper Edge API key with the meeting-type create, modify and remove permissions. A read-only credential is refused by the app.
- Not yet available. Hive does not yet act in SAP S/4HANA Cloud (its OData writes need a per-session CSRF token, which a single approved request cannot carry), Medallia (its Query API is read-only), Modjo (its only writes upload third-party call recordings or manage users) or TapClicks, whose write APIs could not be checked against a published reference. Shopify Partner actions are under Actions in Shopify Partner. Addepar, Cyberimpact and Triple Whale actions are under Actions in insurance CRM, wealth, email marketing, knowledge base and ecommerce analytics apps.
Actions in insurance CRM, wealth, email marketing, knowledge base and ecommerce analytics apps
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 decide a lead, email someone (a Cyberimpact opt-in or a scheduled mailing to every subscriber in its groups), stop someone receiving mail, erase data, or delete, so their cards are marked high-risk and say what will happen.
- Only records Hive read. An action on an existing customer, lead, producer, pipeline, entity, group, contact, mailing, template, article, category or card 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 actions that name no existing record (such as an Addepar entity or group, a Cyberimpact group or template, an Elevio category or card, or any Triple Whale record); the others run from Ask and agents.
- Who is emailed. A Cyberimpact contact receives every mailing sent to its groups, and an opt-in emails a confirmation request at once; an AgencyZoom lead can start your agency’s drip emails. These addresses must come from your records, your own request or the workflow’s data, never from text Hive read.
- Not offered. Hive never changes an AgencyZoom policy, quote, opportunity, driver, vehicle or file, or deletes an email or text thread; never writes Addepar transactions, positions, fees, users or roles; never creates a Cyberimpact API token or runs a batch import; and never runs a Triple Whale SQL query or bulk order import.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to write: an AgencyZoom login acts with that user’s role (the agency owner can do everything), an Addepar API key needs write access to entities and groups, a Cyberimpact token needs write access to members, groups, mailings and templates, an Elevio key acts as its user, and a Triple Whale key needs the Data-In scopes. A read-only credential is refused by the app.
Actions in Shopify Partner
Hive reads Shopify Partner live (see Apps Hive reads live) and can also make the two changes the Partner API offers, from Ask and agents. Each one waits on an approval card for a member to approve, even on Act.- High-impact actions are in bold. Both change what a merchant is billed and cannot be taken back, so their cards are marked high-risk and show the app, the shop, the amount or when the cancellation lands, and whether it is a test credit or prorated.
- Only apps and shops Hive read. Each action names an app and a shop Hive read from your Partner account in the same chat or run: Hive lists an app’s shops, with their ids, from the app’s install and charge events, and reads a shop’s active subscription before a cancellation. A workflow’s Use a connected app step therefore does not offer them; they run from Ask and agents.
- Not offered. The Partner API has no other writes: Hive never changes an app’s pricing, a theme, a payout or a referral.
- Permissions. These actions use the same Partner API client as the reads. A credit needs the View financials permission, and the shop and subscription reads need Manage apps.
Workflow triggers in marketing, community, event, form and recruiting 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.
A Basin event names the form, never what was submitted or who sent it. A Luma guest and a Circle
author carry a name, never an email.
Workflow triggers in field-service, construction and call-notes 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, names, numbers, amounts, statuses and dates. They never carry an address, a
contact’s details, a call’s participants or transcript, or an invoice’s description.
Workflow triggers in marketing, commerce and shipping 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, names, statuses, totals, dates, carriers and tracking. They never carry a
customer’s name, email or address, a campaign’s recipients or content, or a post’s copy.
Workflow triggers in team chat, WhatsApp marketing and meeting scheduling 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.
A Mattermost message carries a preview of its first 500 characters, never your own messages or
system messages. Chili Piper events name the host, never the guest’s or host’s email. Chatarmin
events carry the campaign’s reach and cost, never its recipients.
Workflow triggers in CRM, feedback, booking, meeting-notes and checkout 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, names, stages, statuses, amounts and dates. They never carry a contact’s,
customer’s, buyer’s or assignee’s name, email, phone or address, or a feedback response.
Workflow triggers in subscription, returns, order and 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, names, statuses, totals and dates. They never carry a customer’s or
respondent’s name, email or address, a survey answer, or a cancellation reason.
Workflow triggers in ERP, contact-centre quality, survey and shipping 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 document numbers, party numbers, ids, statuses, scores, totals, carriers and
dates. They never carry a customer’s name, email or address, an evaluator’s notes or a survey
answer.
Workflow triggers in commerce CRM, adviser CRM, call-recording and staffing 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, titles, subjects and dates. They never carry a buyer’s
name, email or address, an activity’s description, location or attendees, a recording’s
participants, or the name or email of whoever made an approval item.
Workflow triggers in design and publishing 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, titles, design types, page counts, dates and a published post’s public link.
They never carry a design’s edit or view link, or a post’s excerpt.
Workflow triggers in community, reviews, memory book and learning 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, titles, names, categories, statuses and dates. They never carry a member’s
name or email, a topic’s body, a book’s pages or a group’s join key.
Workflow triggers in Facebook (system user)
A Connected app event trigger can also start a workflow from a Facebook system-user connection when the system user gains a Page or an ad account, or an ad account’s status changes (for example to disabled or closed). Hive checks the workflow owner’s own connection about every 15 minutes and only reads it. The events carry ids, names, a Page’s category and an ad account’s currency and status, never a Page access token.Pipedrive, Attio, Close and Zoho CRM
Hive reads these CRMs live on the member’s own connection, acts in them on an approval card, and starts workflows when deals, leads and contacts change. The approval cards and workflow triggers are rolling out to workspaces gradually. Reads. Ask and agents can read deals, opportunities and leads (most recently changed first, or filtered by pipeline, stage, status, owner or a date), search records by name, email or phone, open one record, and read people, contacts and companies, notes, tasks and activities, pipelines and their stages, and the users a record can be given to. The full list for each app is on Apps Hive reads live. Actions. Each one waits on an approval card for a member to approve, even on Act:- Only records Hive read. An action on an existing deal, lead, stage, status or owner names one Hive read from your account in the same chat or run, so a workflow step offers only the creates that name no existing record (a new deal, person, organization, contact, account or lead).
- Attio comments are yours. An Attio comment is posted as the member who connected Attio, never as a colleague.
- Nothing is sent to your contacts. Adding a person or contact stores their details in the CRM; Hive emails nobody. Hive does not send email or sequences from Close or Pipedrive.
- No Zoho CRM automation. Every Zoho CRM change Hive makes is sent with Zoho’s own setting that runs no workflow rule, approval process or blueprint, so none of their emails or field updates fire from a Hive change.
- Close tells the assignee. Close emails the person a new task is assigned to, as it does for any task. Opportunity values are in your Close organization’s currency.
- Not offered. Hive does not delete records or merge any but Pipedrive people, edit in bulk, upload files or create Zoho CRM leads (a new lead can start a campaign that emails it).
- Permissions. Reads need read access to deals, contacts and settings; actions need write access to the same areas. A change the connection may not make is refused by the app, and Hive shows what it answered.
Outreach, Salesloft and Copper
Hive reads these sales tools live on the member’s own connection, acts in them on an approval card, and starts workflows when prospects, people, accounts and opportunities change. The approval cards and workflow triggers are rolling out to workspaces gradually. Copper connects with its API key and the email of the user who made it; Copper’s OAuth sign-in still connects only. Reads. Ask and agents can read Outreach prospects, accounts and opportunities (most recently changed first, or filtered by stage, owner, account, email or a date), one record, prospect and opportunity stages, tasks, sequences and which sequences a prospect is in, and calls; Salesloft people and accounts (by stage, owner, email or a date), one record, person and account stages, notes, tasks, cadences and calls; and Copper people, companies, opportunities, leads and tasks (most recently changed first, or by name), one record, its related records and activities, pipelines and their stages, users, loss reasons and activity types. The full list for each app is on Apps Hive reads live. Actions. Each one waits on an approval card for a member to approve, even on Act:- Only records Hive read. An action on an existing prospect, person, account, opportunity, stage or owner names one Hive read from your account in the same chat or run, so a workflow step offers only the creates that name no existing record (a new account, or a Copper company).
- Nobody is emailed. Adding a prospect or person stores their details; Hive never adds anyone to an Outreach sequence or a Salesloft cadence, and never creates an email task, because those send email.
- Not offered. Hive does not delete or merge records, edit in bulk, or log emails.
- Permissions. Outreach reads need the read scopes for prospects, accounts, opportunities, stages, users, tasks, sequences and calls; actions need the matching write scopes. A change the connection may not make is refused by the app, and Hive shows what it answered.
Connect-only providers
Shopify and Greenhouse connected with OAuth now read, act and start workflows like their API-token and client-credentials connections: see One app, several sign-ins. Mailchimp builds campaign drafts: see Campaign drafts in Mailchimp and Brevo.Proposal and CRM events from other tools
If your CRM or proposal tool is not listed, send its events to Hive through an incoming webhook. Hive understandsproposal.created,
proposal.won and client.created natively.
Ideas
- “Which HubSpot deals over £20,000 have not moved stage in three weeks?”
- The Renewal Scout workflow template finds upcoming renewals in HubSpot every Monday and drafts a renewal note for each.
- Ask Hive to summarise every open Intercom conversation with a customer before a call.
- “Reply to the customer on Zendesk ticket 4821 that the refund went out today, then mark it solved.”
Related
Sales and renewals
How sales teams use Hive.
Customer support
How support teams use Hive.