In Ask and Signals, an action follows the
Read, Draft or Act level of the account it uses, and new
accounts start on Act. Even on Act, an action that cannot be undone or that a safety
check holds back, such as deleting a Jira issue or suspending an Okta user, waits for your
approval, and so does any change through an MCP server. Agents and workflows follow the same level
for the actions selected for them (on Draft each waits for approval) and on Act carry them
out by themselves, unless where an action sends, such as a Slack channel or a
GitHub repository, did not come from you: then it waits for your approval. Name a repository in
an agent’s instructions by its GitHub link and a Slack channel as
#name; see
What agents and workflows do by themselves.GitHub
Connect: OAuth. Hive reads: your repository inventory, a repository’s pull requests, issues assigned to you, a search of one repository’s issues and pull requests by state, assignee, label, words, review requested from or given by someone, or the day they last changed, and one issue or pull request with its description and latest comments. Search results show an issue’s milestone, and the day it is due while it is open. Searches are always scoped to the repositories you connected, never the whole of public GitHub. Ask also reads a repository’s last 20 commits with who made them, one pull request with the check runs on its latest commit (up to 50) and its reviews (up to 50), and the people an issue can be assigned to. Each read says when it reached its limit. These reads work on a connection made with a personal access token too. Actions: create, comment on, update, close and reopen issues; add a label; assign an issue to someone; request a review on a pull request.- Assigning and review requests name the person by the GitHub login Hive read from the
repository’s assignable people, and the issue or pull request as
owner/repo#number. Undo removes the assignee or the review request Hive added. If the person was already assigned, or their review was already requested, Hive changes nothing and offers no undo, so it never removes something that was there before. Both also work with a personal access token.
Jira
Connect: OAuth. Hive reads: your user, assignable users, your open issues, project issues and projects; a search of your issues by project, words, assignee or JQL; one issue with its description, latest comments and change history; the transitions an issue can take now, with their ids; your boards; a board’s sprints with their dates, state and goal; and the issues in one sprint, in the board’s order. Search results also show each issue’s numeric id and its Jira status category (to do, in progress or done). Ask also reads the priorities, a project’s issue types and the issue link types, so an action can name them by id. Actions: create, comment on, assign, transition, update, label and delete (permanent) issues; set an issue’s priority; create a subtask; log work; link two issues.- Priority, subtasks and links by id. Setting a priority, creating a subtask (under the parent issue, with the project’s subtask type) and linking two issues (“as relates to”) each show the name and the Jira id on the card, for example Priority: High (id 2), and every id comes from a Jira read in the same chat.
- Logging work records whole minutes, at most 24 hours in one entry, with the time the work started and an optional comment. Jira lowers the issue’s remaining estimate by the time logged.
Linear
Connect: OAuth, or Linear’s official MCP server (https://mcp.linear.app/mcp).
With the OAuth connection, Hive reads Linear itself, acts in it on an approval card and starts
workflows when issues change; these are rolling out to workspaces gradually. With the MCP server,
Ask uses Linear’s own tools: in Ask any tool that changes something goes through approval, even on
Act, and an agent carries out the Linear tools selected for it by itself, unless a call names an
address or link that did not come from you. See MCP servers.
Reads (OAuth). Ask and agents can read teams with their workflow states and members, a team’s
issues (most recently changed first, or in one state), the open issues assigned to you, issues
changed since a time, issue search by words, one issue with its description, labels, sub-issues and
comments, projects and a project’s issues, cycles, labels and workspace members.
Actions (OAuth). Each one waits on an approval card for a member to approve, even on Act:
create an issue in a team, change its title, description, priority or due date, change its status,
assign it, comment on it, move it into a project, and create a project. An action on an existing
issue, state, person or project names one Hive read, so a workflow step offers none of them. Hive
does not delete or archive issues.
Starts workflows. A Connected app event
trigger can start a workflow when a Linear issue is created, updated, changes status or is
completed. The events carry the issue’s id, identifier, title, status, team, project, priority and
dates, and the assignee by id only.
Notion
Connect: OAuth. Hive no longer offers Notion’s MCP server; an existing Notion MCP connection keeps working. Hive reads: pages and page metadata, a database’s items with their properties (status, owner, dates), optionally only those where one property equals a value (“where Status is In progress”), and a page’s open comments. Actions: create a page, append blocks, add a to-do, update properties (including status properties), archive a page, comment on a page, move a page under another page, and create a page from a template.- Notes with to-dos in one card: ask Hive to add meeting notes to a page “with the actions as to-dos” and one card adds the headings and paragraphs, then each action as an unchecked to-do.
- From a template: name a template page and Hive creates the new page under the page you choose with Notion copying the template’s content into it. The new page is blank for a moment while Notion fills it in.
- From a template, filled in: when the new page needs your details (“with team Ada and Bob, scope audit and milestones…”), Hive reads the template page’s blocks and one card shows each block of the new page with your details filled in, then creates the page with them. It copies up to 100 top-level text blocks (headings, paragraphs, lists, quotes and to-dos); nested blocks, tables and images are not copied this way.
PostHog
Connect: OAuth. Choose your region — EU (eu.posthog.com) or US (us.posthog.com).
The wrong region points at a different host, so reads return no data.
Hive reads: projects, dashboards, saved insights, feature flags and annotations. For a saved insight, Hive
first reads the latest result PostHog has already calculated, with the time it was last refreshed.
If PostHog has no cached result for that insight, Hive asks PostHog to calculate it once. PostHog
reuses a fresh cached result instead of running the query again, and Hive never forces a
recalculation of a result that is already fresh. Calculations run on your PostHog account, so Hive
limits them:
- At most 3 insights per lookup. One Ask answer or one workflow agent step can ask PostHog to calculate up to three insights. Any further insight is reported without a value, with a note that the limit was reached.
- A time limit on each calculation. If PostHog does not finish in time, Hive reports the insight without a value rather than failing the answer.
- Event trend: how often one event happened over the last days (30 unless you say), with each day’s or week’s count.
- Site users and top pages: how many people viewed pages over the last days, optionally only on one host (your client portal) or paths, and the 20 pages viewed most. Each person counts once over the whole period.
- Persons seen recently: the people PostHog saw in the last days (7 unless you say), with their name, email and when they were last and first seen, from the first 50 persons PostHog lists. Other person properties are not read. This is personal data: share it only as far as you need to.
- Session recordings of a person: one person’s recordings from the last 30 days, found by their exact email: when each started, how long it ran, active time, clicks and the page it started on. The recording itself is watched in PostHog; Hive reads none of its content.
feature_flag:write, dashboard:write, insight:write).
Sentry
Connect: Sentry’s official MCP server (https://mcp.sentry.dev/mcp), listed under
Observability. Hive reads organisations, projects, issues, members and teams. In Ask, changes such
as resolving or assigning an issue go through approval; an agent carries out the Sentry tools
selected for it by itself, unless a call names an address or link that did not come from you.
With the Sentry OAuth connection, Ask also reads a project’s unresolved issues with the most
events in the last 24 hours (up to 25) and an issue’s latest events (up to 25, as summaries without
stack traces). Resolving an issue can also be resolved in the next release, so Sentry reopens it
if it happens again in a later release; the card says so.
Trello
Connect: OAuth. Hive reads: your open boards with their lists, a board’s lists and cards, a card with its checklists, a board’s members and labels, a search of your cards, and the open cards assigned to you across your boards, each with its board and list by name. Actions: create, update, move, archive and delete (permanent) cards; comment on a card; add a checklist item, a member or a label to a card.- A card with a checklist in one approval: “create a Trello card “Acme audit 2026” in the list To do with the due date 31 December and the checklist …” creates the card, then its checklist, then each item (up to 50). If an item cannot be added, the receipt names it. Undo deletes the card.
- Move and comment: “move the card … to Done and comment …” is one card: the move, then the comment.
- Members and labels are named on the card with their Trello ids, from the board read in the same chat. Undo removes the member or label again.
Figma
Connect: OAuth. Hive reads: your user, a file’s pages, its comments and its version history (up to 30 versions a read), a project’s files, and the projects in a team (the number after/team/ in a Figma team
link).
Actions: post, resolve and delete comments.
Okta
Connect: OAuth. Hive can suspend a user, which Okta can reverse by unsuspending. In Ask and Signals a suspension never runs without your approval, even on Act. An Owner or Admin can select it for an agent or add it to a workflow, where it runs by itself. Hive does not read from Okta yet.Shortcut, Azure DevOps and GitLab
Hive reads these apps live (see Apps Hive reads live and engineering apps). Ask also answers “did the latest GitLab pipeline on main pass?”: it reads the newest pipeline on that branch, with either GitLab token, and checks the branch name before it is sent. Hive can also:
Starts workflows: a Connected app event
trigger on GitLab with a personal access token starts when an issue is opened or closed, or a merge
request is opened or merged, in the 10 most recently active projects you are a member of, checked
about every 15 minutes.
- None of these 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 work Hive read. The story, work item or project an action names must be one Hive read from your account in the same chat or run, so Hive never writes to a guessed id. These actions therefore run from Ask and agents, which read first, and are not offered in a workflow’s Action step.
- Permissions. These actions use the same token as the reads. A GitLab token needs the
apiscope (read_apionly reads), and an Azure DevOps personal access token needs Work Items (Read & write). A read-only token is refused by the app.
Jira Data Center, Toggl, Float and CompanyCam
Hive reads these apps live (see Apps Hive reads live and engineering apps), and can also:- None of these 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 work Hive read. The Jira project or issue, Toggl workspace or project, or Float or CompanyCam project an action names must be one Hive read from your account in the same chat or run. Those actions run from Ask and agents; a workflow’s Action step offers only the Float and CompanyCam project creates, which name nothing existing.
- Jira Data Center comments are internal. On a Jira Service Management issue the comment is an internal note, so the customer portal does not show it and the reporter is not emailed; the card says Visibility: Internal. Other projects ignore the setting.
- Toggl. Hive logs a finished entry with its start time and length; it never starts or stops a running timer. Times are in UTC.
- Permissions. These actions use the same credentials as the reads. The Jira account must be allowed to create issues and comment in the project, and a Float or CompanyCam key must be allowed to write. A read-only key is refused by the app.
MSP, field service, property and content apps
Hive reads these apps live (see Apps Hive reads live, Finance, ERP and contracts and engineering apps), and can also:- None of these 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 change to an existing ticket, company, organisation, document, job, record, article or key names one Hive read from your account in the same chat or run, so Hive never writes to a guessed id. Those actions run from Ask and agents. A workflow’s Action step offers only the creates that name nothing existing: a ConnectWise company, an IT Glue organisation, a Veeva object record and a Phrase project.
- Deletes, cancellations and starting a Phrase job need the stronger approval. The card says what is deleted, cancelled or started. Starting a Phrase job notifies its translators. Deleting a Phrase job keeps its keys and translations; deleting a key removes its translations.
- Nobody is emailed. A ConnectWise note is an internal-analysis note and never asks ConnectWise to send its notifications. An IT Glue document is created unpublished and not public. A Document360 update changes the article’s latest version, and Hive never publishes an article.
- Not offered. Hive never reads or writes IT Glue passwords, and does not delete in IT Glue, which deletes only in bulk. Creating or publishing a Document360 article, creating a BigChange contact or note, and creating Buildium records other than notes need ids or settings Hive cannot read yet.
- Veeva Vault. Field names are Vault’s own, such as
title__vorname__v. A lifecycle state is not a field: Hive does not change a document’s state, and your Vault security profile still decides what you may edit or delete. To update or delete an object record, Hive first reads that record (or, on the OAuth connection, lists the object’s records) so the change names a record id Vault returned; a document id never stands in for one. - Permissions. These actions use the same credentials as the reads, so they must be allowed
to write. The ConnectWise API member needs a security role with Add, Edit and Delete
on Service Tickets and Companies, a Phrase token the
writescope, a Document360 token more than GET permission, and a BigChange client thecontacts:writeandjobs:writescopes. A read-only key, role or scope is refused by the app: give it write access, or reconnect with one that has it.
Engineering and IT service apps connected with a key or token
Hive reads these apps live (see Docs, projects and automation and Engineering, data and analytics), and can also change them after a member approves the card:- Approval every time. None of these can be undone from Hive, so in Ask and Signals each one waits on an approval card, even on Act. The actions in bold delete something or reach someone outside the team (a requester, a caller, the responders an incident alerts), so their cards are marked high-risk and say what will happen.
- Only work Hive read. An action on an existing issue, ticket, incident or record must name one Hive read from your account in the same chat or run. A GitHub issue is named by the address the read returned, and a GitLab issue or merge request by its web address together with the project on that same record, so Hive never writes to a guessed number. Those actions run from Ask and agents. A workflow’s Action step offers only the creates that name nothing existing: ServiceNow incidents, problems and change requests, Freshservice tickets and Halo PSA clients.
- Jira comments are internal. On a Jira Service Management issue, a comment Hive adds is an internal note: the customer portal does not show it and the reporter is not emailed. Hive does not post public replies to service desk customers. Other Jira projects ignore the setting.
- ServiceNow. A work note stays with the fulfiller team. A comment is an additional comment the caller sees and may be emailed. Hive never resolves or closes an incident, because ServiceNow needs a close code and notes for that.
- Autotask. Ticket status, priority and queue, and a note’s type and who it is published to, are your instance’s own picklist values. Hive reads them from Autotask before it fills the card. A note’s publish value can put it in front of the customer, so a note card is marked high-risk.
- Workflow triggers. A Connected app event trigger on Autotask PSA starts when a ticket is created, has new activity or is completed; on ConnectWise PSA (and its staging host), when a service ticket is created, changed or closed; on Halo PSA, when a ticket is created, changed or closed; on incident.io, when an incident is declared, changes status or is closed; on Sentry, when an issue is new, regresses or escalates; on Azure DevOps, when a pull request is opened or completed or a build succeeds or fails; on a GitLab group access token, when an issue or merge request in the token’s groups is opened, closed or merged; on Rootly, when an incident starts, is mitigated or is resolved; on Datadog, when a monitor starts alerting or recovers, or an incident is declared. Each is checked about every 15 minutes, on the workflow owner’s own connection, and only read.
- incident.io. Declaring an incident is real: it alerts responders, so choose public or private visibility on the card. Approving the same card twice opens only one incident. Editing an incident never notifies its channel.
- Freshservice. A new ticket’s requester may receive Freshservice’s automatic acknowledgement, so check the address on the card; a workflow’s card also says where the address came from. A reply is emailed to the requester the ticket read returned, and its card names them; private notes are seen only by agents.
- Permissions. These actions use the same credentials as the reads, so they must be allowed
to write. A GitHub token needs Issues: Read and write on the repository, a GitLab group token
the
apiscope, and a ServiceNow integration user write access (for example theitilrole) on the incident, problem and change request tables. A read-only key or role is refused by the app.
Actions in identity, device, automation, monitoring and OKR 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 remove or grant access, lock or restart a device, run automation code now, cancel, delete or reach someone outside the team, so their cards are marked high-risk and say what will happen. Running an Apify Actor uses your Apify platform credit.
- Nothing sent quietly. A new Okta user is staged, so Okta sends no activation email, and an
Okta deactivation or app unassignment emails nobody. JumpCloud emails a new user an activation
link, Adobe can invite a new user or tell one about a new product, Firstbase emails the person
an order was for when you decline it, and Greenhouse can confirm an application to the applicant.
Those addresses are checked like an email recipient: they must be in your workspace directory,
typed by you, or set by the workflow. A Datadog monitor’s message notifies whoever its
@-handles name when it fires, an event’s title and text notify theirs as soon as it is posted,
silencing a monitor stops its alerts for the window, and declaring an incident can page
responders, so all four are high-risk. Hive refuses an
email handle (
@name@example.com) in a Datadog monitor or downtime message or an event, because Datadog would email that address; integration handles such as@slack-opsstill work. - Only records Hive read. An action on an existing user, group, application, device, blueprint, run, task, recipe, scenario, workflow, execution, schedule, team, project, issue, release, monitor, annotation, dashboard, document, connection, goal, key result, KPI, inventory item, office or order names one Hive read from your account in the same chat or run. A JumpCloud or Adobe user is found by exact email; Hive never lists the directory. A workflow’s Action step therefore offers only the actions that name no existing record (such as a new user, group, tag, folder, annotation, schedule, document, report, goal or initiative); the others run from Ask and agents.
- Not offered. Hive never sets or resets a password, enrolls or removes an MFA factor, assigns an admin role, changes a sign-in or security policy, erases or wipes a device, or locks a Kandji device (Kandji answers a lock with the device’s unlock PIN). It never creates, rotates or reads an API key, token, webhook secret or environment variable, publishes an Apify task or dataset, orders or approves Firstbase equipment, or offboards a person. Pave’s API is read-only, so Hive only reads it.
- Permissions. These actions use the same key, token or app registration as the reads, so it
must be allowed to write. For example, an Okta service app needs
okta.users.manage,okta.groups.manageandokta.apps.manage; a Microsoft app registration needsGroup.ReadWrite.All,SecurityAlert.ReadWrite.AllorDomain.ReadWrite.All; a Grafana service account needs the Editor role; a JumpCloud or Kandji key and an n8n or Make key need write access; and a Datadog application key needsmonitors_write,monitors_downtimeandincident_write. A read-only key or role is refused by the app. - Not yet available. Hive does not yet act in SAP SuccessFactors, whose write API could not be checked against a published reference. Personio (API v2) actions are under Actions in HR, recruiting, onboarding project and SaaS management apps.
Actions in access, identity, device, hiring and content 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 grant, remove or restore someone’s access, delete, cancel, disqualify a candidate, put a job on your careers site or publish documentation, so their cards are marked high-risk and say what will happen.
- Nothing sent quietly. A new PingOne user’s address, and a new JazzHR applicant’s address (your JazzHR workflow may email them), are checked like an email recipient: they must be in your workspace directory, typed by you, or set by the workflow. OneLogin sends no invite to a user created through its API, and a new Recruitee candidate joins no job and gets nothing. A Recruitee disqualification can trigger your own Recruitee automations to email the candidate.
- Only records Hive read. An action on an existing app, task, review, request, user, group, device, building, department, team, project, release, member, candidate, placement, job, applicant, key result, document or publish setting names one Hive read from your account in the same chat or run. PingOne, OneLogin and Duo users are found by exact email or username; Hive never lists the directory. A workflow’s Action step therefore offers only the actions that name no existing record (such as a new app, review, user, building, candidate, job, applicant, company or category); the others run from Ask and agents.
- Not offered. Hive never sets or resets a password, enrolls or removes an MFA factor, assigns a OneLogin, Lumos or admin role, connects a Lumos integration with credentials, requests access on someone’s behalf, offboards a person, or erases, locks or un-manages a Jamf device. Cisco Duo signs a create or update over its form body, which the connection cannot sign, so Hive only deletes there. Leapsome praise, feedback and private notes are written in a named person’s name, so Hive does not post them, and Firefish changes to existing records wait until Hive can tie Firefish’s record numbers to a read.
- Permissions. These actions use the same key, token or app registration as the reads, so it
must be allowed to write. For example, a PingOne worker app needs a role that can manage users
and groups; a OneLogin credential needs Manage users; a Duo Admin API application needs
Grant write resource; a Jamf Pro API role or user needs the matching Update, Create and Delete
privileges; a Firefish client needs
companiesAPI-write; and a Sentry token needs the write scopes for teams, projects, releases and members. A read-only key or role is refused by the app.
Actions in network, identity, device, recruiting, planning and call-agent 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 grant, remove or restore someone’s or a device’s access, change how a whole tailnet resolves names, delete, disqualify a candidate, reopen a job, or change what a live call agent says or who answers a number, so their cards are marked high-risk and say what will happen.
- Nothing sent. None of these actions emails, texts or calls anyone. A new Hail contact is only someone an agent can hand a call to, and Hail sends them nothing. A Recruiterflow candidate is added to a job as sourced, which sends no welcome email, though a disqualification can trigger your own Recruiterflow recipes to email them.
- Only records Hive read. An action on an existing device, organization, domain, connection, directory, user, membership, group, application, MDM server, app, catalog, task, candidate, job, stage, client, contact, plan, item, song, AI agent or phone number names one Hive read from your account in the same chat or run. WorkOS, Auth0 and Oracle Cloud Identity users are found by exact email or user name; Hive never lists the directory. A workflow’s Use a connected app step therefore offers only the actions that name no existing record (such as a new organization, group, app, catalog, client company, song, AI agent, contact, inventory device, or a tailnet’s DNS settings); the others run from Ask and agents.
- Not offered. Hive never sets or resets a password, creates an auth key, API key or OAuth client, edits a Tailscale policy file, assigns a role or a permission, invites someone by email, or approves or denies an access request. It does not buy or ship hardware in Quipteams, place calls or send emails or texts through Hail, add people to Recruiterflow sequences or campaigns, or schedule people in Planning Center.
- Permissions. These actions use the same key, token or app registration as the reads, so it
must be allowed to write. For example, a Tailscale OAuth client needs the
devices:coreanddnsscopes; an Auth0 machine-to-machine app needs scopes such asupdate:users,create:organizationsanddelete:sessions; an Oracle Cloud Identity app needs a User or Application Administrator role; a ConductorOne client needs a role that can manage apps and catalogs; and a Planning Center token needs Editor access to the service type. A read-only key or role is refused by the app. - Not yet available. Hive does not yet act in HiBob, Pingboard, SAP SuccessFactors or Setmore, whose write APIs could not be checked against a published reference, or in KnowBe4, whose reporting key is read-only. Paychex actions are under Actions in dashboard, contact-centre QA, payroll, ecommerce CRM, church and customer data apps. Personio (API v2), Breezy HR, Manatal, Lattice, Trakstar Hire, SmartRecruiters, Rocketlane and Torii actions are under Actions in HR, recruiting, onboarding project and SaaS management apps; Recruit CRM and Namely actions are under Actions in Atlassian, time-tracking, database, content, e-signature, subscription, recruiting, HR and account-access apps; WorkRamp and JobDiva actions are under Actions in accounting, staffing, learning, meeting recorder, file sharing and reviews apps.
Actions in hosting, DNS, database, infrastructure and observability 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 change what production serves (a deploy, a rollback, a paused project, a domain), change DNS or the cache, expose or delete files, apply infrastructure changes, reset or delete a database branch, drop live database connections, or end alerting, so their cards are marked high-risk and say what will happen.
- Only records Hive read. An action on an existing project, deployment, team, domain, zone, DNS record, bucket, workspace, run, branch, compute, dataset, monitor, search job or problem names one Hive read from your account in the same chat or run. A Neon branch reset uses the parent that the same branch record names. A workflow’s Use a connected app step therefore offers only the Supabase bucket create; the others run from Ask and agents.
- No secrets. Hive never creates, edits, shows or deletes an environment variable, a Terraform variable, an API token, a database role or a password, so no card carries a secret value.
- Not offered. Hive does not create a Vercel deployment from source, write Cloudflare firewall, WAF or access rules, start a Terraform destroy run, delete a whole Vercel or Neon project, Cloudflare zone or Axiom dataset, write Supabase table rows, change an Axiom dataset’s retention, run a Splunk search, or send events to Dynatrace.
- Permissions. These actions use the same token or key as the reads, so it must be allowed to
write. For example, a Cloudflare API token needs DNS Edit, Cache Purge and Zone
Settings Edit; Supabase bucket changes need the
service_rolekey; an HCP Terraform user or team token needs permission to queue and apply runs and lock workspaces; an Axiom token needs annotation create and monitor delete; and a Dynatrace access token needsproblems.write. A read-only token is refused by the app. - Dynatrace account management user-group actions are in the section below.
- Starts workflows. A Connected app event trigger on Vercel starts when a deployment starts, succeeds or fails, and one on Dynatrace when a problem opens or closes. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it.
Actions in Atlassian, time-tracking, database, content, e-signature, subscription, recruiting, HR and account-access 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 or trash, send signature requests or reminders, void documents, pause, resume or cancel a subscription, post to everyone in the company, create a person’s record or change who can reach a Dynatrace account, so their cards are marked high-risk and say what will happen.
- Only records Hive read. An action on an existing project, issue, space, page, client, task, time entry, app, table, field, model, packet, document group, signer, subscription, order, event, comment, job tier, job title, folder or group 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 (a new Harvest client or task, a Recruit CRM company, task or candidate, a Namely announcement, job tier, folder or pending profile, or a new Dynatrace group); the others run from Ask and agents. Hive added reads so these actions can name a record: Anvil packets with their document group and signer ids, and Namely job tiers, job titles, folders and an event’s comments.
- Ids you give once. The Atlassian cloud id, Harvest account id and Dynatrace account UUID are the ones you connected with; Hive asks for them rather than guessing.
- Not offered. Hive never creates or removes a Harvest user or writes a Harvest invoice, denies a Quickbase user or changes a Quickbase group or user token, publishes Builder.io content, creates an Anvil packet (that uploads files and names signers) or changes a signer’s email, charges an Appstle customer now or changes a price, discount or payment method, emails anyone from Recruit CRM, or touches Dynatrace users, policies, tokens or IP allow lists. It does not change or delete a Quickbase record or an existing Recruit CRM record, because no read names one by an id Hive can check.
- Permissions. These actions use the same key, token or client as the reads, so it must be
allowed to write. For example, an Atlassian service-account token needs
write:jira-workand Confluence page and comment write scopes; a Quickbase user token needs an app role that can change tables, fields and records; an Anvil key needs a role that can send packets; a Dynatrace OAuth client needsaccount-idm-write. A read-only key or role is refused by the app. - Not yet available. Hive does not yet act in WorkRamp, Oomnitza or NinjaOne SaaS Backup, whose write APIs could not be checked against a published reference Hive could reach, or in PRTG, whose classic API changes things only through GET links.
Actions in lists, recruiting, search, HR, testing, cloud data, scanning, filtering and network 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 or recycle, overwrite a record or a whole index, reject a candidate, stop a service or a test run, turn scanning or web filtering off, reconnect an isolated machine or reboot a network device, so their cards are marked high-risk and say what will happen.
- Only records Hive read. An action on an existing list, candidate, application, job, stage, source, rejection reason, index, record, document, task, company list, suite, flow, run, organization, service, customer, endpoint, site, alarm or device 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 (a new SharePoint list, an Ashby or Greenhouse candidate, a Meilisearch index, an Autosana suite or flow, a Zorus customer, a dope.security category or policy, or turning AWS Inspector scanning on or off); the others run from Ask and agents. Hive added two reads so these actions can name a record: an Ashby interview plan’s stages and an Algolia index search. Hive also reads Ashby’s interview schedules, so “which interviews are scheduled this week and who is on each panel” is answered from them.
- Nobody is emailed. A Greenhouse rejection never carries a rejection email, an Ashby note notifies nobody, and an Ashby candidate’s address only sits on their profile.
- Not offered. Hive never starts an Autosana run (it spends your Autosana balance), changes a password, API key, JWT provider or IP access list in ClickHouse, changes an Algolia key or index settings, creates an AWS Inspector suppression rule, isolates a Zorus endpoint (that needs a passphrase Hive would have to hold), adds a dope.security bypass or exception, or upgrades Mist device firmware. It does not change or remove a SharePoint list item, or change a dope.security policy or category that already exists, because no read can name one by an id.
- Permissions. These actions use the same key or token as the reads, so it must be allowed to
write. For example, the SharePoint Entra app needs Sites.ReadWrite.All (or Sites.Manage.All
to create a list); an Ashby key needs write permission on candidates and applications; a
Greenhouse Harvest v3 client needs the matching write scopes; an Algolia key needs the
addObject, deleteObject and deleteIndex ACLs; a Meilisearch key needs the documents
and indexes actions; a HiBob service user needs task and company-list edit permissions; a
ClickHouse key needs the Admin role; AWS Inspector needs
inspector2:Enableandinspector2:Disable; and a Juniper Mist token needs a Write or Admin role. A read-only key or role is refused by the app. - Not yet available. Hive does not yet act in Perdoo, Slab, Streamline AI, Ergo, Auvik, ThreatDown (Malwarebytes) or Mimecast, whose write APIs could not be checked against a published reference Hive could reach. Paylocity, Pipedream, Personio (API v2), Breezy HR, Manatal, Lattice, SmartRecruiters, Rocketlane, Torii and Trakstar Hire actions are under Actions in HR, recruiting, onboarding project and SaaS management apps, and Elevio actions under Actions in insurance CRM, wealth, email marketing, knowledge base and ecommerce analytics apps.
Actions in support, meeting, voice agent, search, code review, sign-in and security 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 reach someone outside the firm (a Plain reply, a Fireflies share), grant or remove access (a Clerk role, a ban, a lock, a signed-out session), merge or block code, change where a go link sends everyone, post to the whole company, cut a machine off the network, change or remove its protection, end a live call or a backup, or delete, so their cards are marked high-risk and say what will happen.
- Only records Hive read. An action on an existing customer, thread, transcript, call, agent, knowledge base, collection, go link, change, reviewer, organization, user, session, department, location, employee, holiday, queue, ring group, job reference, host, agent, threat, endpoint, alert, case or backup job 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 a new Plain customer, a Fireflies recording, a Glean collection, go link or announcement, a Clerk organization or user, an Onboarding department, location or pending hire, a 3CX holiday or a Huntress organization); the others run from Ask and agents.
- Who is emailed. A Fireflies share emails each person a link, a new Greenhouse Onboarding pending hire can start its welcome emails, a new Clerk user’s address receives your app’s own sign-in mail, and Gerrit emails a reviewer added by email address (on a project that allows it, even someone with no Gerrit account), so these addresses must come from your records, your own request or the workflow’s data, never from text Hive read. A Gerrit reviewer added by username or group is someone already on your Gerrit server. A Plain reply goes to the thread’s customer only.
- Not offered. Hive never sets a password, places a call or sends a text through Retell AI, sends a Fireflies bot into a live meeting, writes raw GraphQL, invites anyone to Clerk by email, allows, excludes or unblocks a file, address or process in a security app, opens a remote shell, runs a script, approves or rejects a Huntress remediation, reveals or regenerates a tamper protection password, uninstalls or decommissions a SentinelOne agent, resizes an EKS node group, or starts, restores or deletes an AWS backup.
- Permissions. These actions use the same key or token as the reads, so it must be allowed to write. For example, a Plain machine user needs the thread, customer and note write permissions; a Glean token needs write access to collections, go links and announcements; a Gerrit account needs the matching label, abandon and submit rights on the project; a Clerk secret key manages users and organizations; a SentinelOne or Sophos Central role must allow threat and endpoint actions; a CrowdStrike API client needs Hosts: Write; and a GravityZone API key needs the Network and Incidents APIs. A read-only key or role is refused by the app.
- Not yet available. Hive does not yet act in Mimecast, Nerdio Manager, Oomnitza or NinjaOne SaaS Backup, whose write APIs could not be checked against a published reference. (SharePoint and HiBob actions are in the section above; Personio (API v2), Breezy HR, Manatal, Lattice, SmartRecruiters, Rocketlane, Torii and Trakstar Hire actions are under Actions in HR, recruiting, onboarding project and SaaS management apps.) It does not change a Retell AI phone number, an EKS node group or a backup recovery point, which no read can name by an id.
Actions in construction, Atlassian, incident, IT asset, HR and hiring apps
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.- High-impact actions. A delete, declaring a Rootly incident, marking one mitigated or resolved (each runs your team’s Rootly workflows, such as channels and paging), and a HackerRank test invitation (HackerRank emails the candidate) need the stronger approval.
- Nobody else is emailed by default. A new Lessonly user gets no welcome email, a HackerRank interview is created without emailing anyone, and Jira comments are internal on a service desk project. Confluence pages are saved as drafts.
- Addresses checked like email recipients. The address of a new Hailey HR employee or Lessonly user, and a HackerRank interview’s or test invitation’s candidate, must be in your workspace directory, typed by you, or set by the workflow. The approval card names it and says where it came from.
- Only records Hive read. A change to a project, issue, page, space, incident, action item, asset or test names one Hive read from your account in the same chat or run. The Atlassian actions also name a site from the sites read. A workflow’s Action step therefore offers only the creates that name no existing record. The other actions run from Ask and agents.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to
write: an ingenious.build user with edit rights, an Atlassian service account with the
write:jira-workand Confluence page and comment write scopes, a Rootly API key that is not read-only, a Snipe-IT token whose user can edit, check in, audit and delete assets, and admin-level Hailey HR, Lessonly and HackerRank keys. A read-only key, role or scope is refused by the app.
Actions in feature flag, event and meeting 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 change what a live product shows its users, email guests or hosts, release preserved notes, or delete, so their cards are marked high-risk and say what will happen.
- Who Luma emails. Luma emails each guest you add or invite, each host you add, and every going guest of a blast. Those addresses are checked like an email recipient: they must be in your workspace directory, typed by you, or set by the workflow. Luma also emails guests when an event’s name, time or place changes. Hive never refunds a guest: a paid guest moved out of Going keeps their payment until you refund it in Luma.
- Only records Hive read. An action on an existing gate, experiment, dynamic config, flag, event, guest, ticket type, tag, legal hold or action item 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 new gate, experiment, config, event, tag or legal hold); the others run from Ask and agents.
- Not offered. Hive never cancels a Luma event (Luma’s cancellation refunds and notifies every guest), creates a coupon, imports or blocks calendar contacts, changes calendar admins or sets a webhook. It never edits Statsig rules, overrides or targeting, or approves a review.
- Permissions. These actions use the same key as the reads, so it must be allowed to write: a Statsig Console API key with write access (not read-only), a Luma Plus calendar API key, a Granola Enterprise workspace API key that can manage legal holds, and a Fellow API key. A read-only key is refused by the app.
- Not yet available. Hive does not yet act in Pendo, whose write API could not be checked against a published reference. Fathom’s and Kno Commerce’s APIs offer no changes Hive could make and Zigpoll’s connection is read-only, so Hive only reads them. Recall.ai actions are under Actions in meeting recorder, call intelligence and support apps, and Podscribe and Northbeam actions under Actions in ERP, personal finance, spend, commerce, booking and ad measurement apps.
Actions in BI and dashboard 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 content (a Looker folder delete removes what is in it), or start, stop or send a scheduled delivery to its recipients, so their cards are marked high-risk and say what will happen. Archiving a Metabase item keeps it restorable, so it is the option Hive offers first.
- Only records Hive read. An action on an existing collection, dashboard, question, folder, Look, page, collection, dataset, document, label or schedule 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 writes users, groups, permissions, database connections, public links or embeds, runs or changes a query, loads rows into a Domo dataset, or adds a delivery recipient.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to write: a Metabase API key in a group with curate access to the collections, a Looker API user that can save content in the folders, a Domo client with the data and dashboard scopes, and an Omni token whose user is an editor on the folders and documents. A read-only credential is refused by the app.
- Klipfolio actions are under Actions in dashboard, contact-centre QA, payroll, ecommerce CRM, church and customer data apps.
Actions in notebook and lakehouse 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 run or stop compute you are billed for, show a draft to everyone a dashboard is shared with, or delete, so their cards are marked high-risk and say what will happen.
- Safe defaults. A Hex run never replaces the published app’s results and notifies nobody. A published Databricks dashboard never embeds the approving member’s credentials: its viewers query with their own access. A metastore is never force-deleted, so Databricks refuses while it still holds catalogs.
- Only records Hive read. An action on an existing project, run, collection, dashboard, warehouse or metastore 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 shares a Hex project or collection, writes Hex users, groups, data connections or cells, or edits a Databricks dashboard’s layout or queries. It never creates or resizes a SQL warehouse, and never changes Databricks workspaces, credentials, storage or network settings, users or permissions.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to write: a Hex token with the Run projects scope and edit access to the projects, and a Databricks service principal with CAN MANAGE on the dashboards and warehouses (workspace) or the account admin or metastore admin role (account). A read-only credential is refused by the app.
Actions in HR, recruiting, onboarding project and SaaS management 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 change a person’s HR or candidate record, reach a candidate or a hiring team, put a job ad in front of applicants, change who can work on a project, start an offboarding or another Torii workflow, or delete, so their cards are marked high-risk and say what will happen.
- Only records Hive read. An action on an existing person, employment, absence, project, document, candidate, job, position, goal, company, stage, opening, contact, note, task, phase, time entry, space, user, app, contract, transaction, field or workflow 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 a Paylocity new hire, a Personio person or project, a SmartRecruiters candidate, job or department, a Trakstar Hire opening or candidate, a Manatal candidate or client organisation, a Torii custom app or field, or a Pipedream project); the others run from Ask and agents.
- Who is emailed. A Breezy HR message or questionnaire goes to the candidate, a SmartRecruiters hiring-team message emails everyone on that job’s team, and a Torii workflow can message the user it acts on. A candidate’s address in SmartRecruiters, Breezy HR, Trakstar Hire or Manatal, a Paylocity new hire’s work address and a Torii workflow’s user must come from your records, your own request or the workflow’s data, never from text Hive read. Breezy HR stage actions (automatic stage emails) stay off for a candidate Hive adds or moves to another position; moving a candidate to another stage runs the actions set up on that stage, and the card says so.
- Not offered. Hive never changes a Paylocity employee once hired (Paylocity has no exact employee lookup, and Hive does not list a firm’s employees), pay rates, earnings, taxes, benefits, direct deposit or identity numbers; never writes a Personio compensation or skips Personio’s absence approval; never edits a Lattice goal (Lattice replaces every field on an edit); never uploads a resume or document; never creates a Torii plugin or API key, changes extension settings or anonymizes a user; never changes a Rocketlane budget, revenue setting, custom field or placeholder; and never touches a Pipedream OAuth client, app override, webhook, connected account or deployed trigger.
- Permissions. These actions use the same credentials as the reads, so they must be allowed to write. For example, Personio (API v2) credentials need the write scopes for persons, employments, absences, attendances, projects and documents; a SmartRecruiters key needs the candidate, job and message manage permissions; a Torii API key needs write scope; a Rocketlane key acts as its owner; and a Pipedream OAuth client needs the Connect project scopes. A read-only credential is refused by the app.
Actions in dashboard, contact-centre QA, payroll, ecommerce CRM, church and customer data 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, change who can see a dashboard, data source or account, publish a dashboard as a link, create or change a person’s record, cancel, pause or reactivate an order, purchase or membership, message a customer, or write customer data, so their cards are marked high-risk and say what will happen.
- Recipients checked. Konnektive emails order, shipping and billing notices to a customer’s stored address, so a changed customer email address is held to your workspace’s send rules and named on the card.
- Only records Hive read. An action on an existing client account, dashboard, Klip, data source, user, group, role, link, action, message, tag, document, 121, company, worker, custom field, job, order, fulfillment, customer, purchase, product, membership, person or job 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 (a new Klipfolio client account, dashboard, Klip or role, an EvaluAgent role or knowledge vault tag, a Konnektive product, a Pushpay ChMS person, and Data Cloud records or a bulk job); the others run from Ask and agents.
- New reads. Hive added reads so these actions can name a record: Klipfolio roles, one user by email, a user’s groups, a dashboard’s sharing, a group’s default dashboards and a dashboard’s published links; EvaluAgent groups, levels, roles, abilities, one user, coaching actions and their messages, 121s and their topics, and knowledge vault documents and tags; one Paychex worker by given and family name (both in full), that worker’s addresses, phones, email, custom fields and emergency contacts, and the company’s custom fields, categories and jobs; and one Pushpay ChMS group and its participants. Konnektive (campaigns, products, orders, customers, recurring purchases, fulfillments and club memberships, each by date range or by id) and Salesforce Data Cloud (bulk ingestion jobs and profile and calculated-insight metadata) now have reads of their own.
- Names you give once. The Data Cloud Ingestion API connector and object names are the ones set up in Data Cloud; Hive asks for them rather than guessing.
- Not offered. Hive never moves money: no Konnektive refund, charge, pre-authorisation, rerun, capture, imported order, price, coupon, card, gateway or affiliate commission, and no Paychex check, pay rate, pay component, direct deposit or tax change. It never approves a Konnektive order in QA, sets a Klipfolio password or published-link password, creates or revokes an EvaluAgent API token, uploads files (EvaluAgent documents and call audio, Data Cloud bulk CSV files), changes Paychex webhooks or client access, or sets Pushpay ChMS sign-in credentials. It does not add a Paychex worker, create a Paychex job or edit a Paychex company custom field, because those calls accept only a Paychex-specific format Hive does not send, and does not change a Pushpay ChMS person’s details, whose fields could not be checked against a published reference.
- Permissions. These actions use the same key, login or client as the reads, so it must be
allowed to write. For example, a Klipfolio API key must belong to a user who can manage
dashboards, users and roles; an EvaluAgent access key needs a role that can manage users,
groups and actions; a Paychex app needs the company access and worker write permissions Paychex
grants it; a Konnektive API user needs the order, customer, purchase and product APIs; and a Data
Cloud connected app needs the
cdp_ingest_apiscope. A read-only key or role is refused by the app.
Actions in accounting, staffing, learning, meeting recorder, file sharing and reviews 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, email someone, cancel or create an invoice that may be numbered at once, reject an application, create or change a person’s record, assign training, or change who can open a recording, playlist or file, so their cards are marked high-risk and say what will happen.
- Only records Hive read. An action on an existing contact, invoice, purchase, job, candidate, company, guide, user, assignment, group, recording, clip, playlist, team, share, question, answer, product or collection 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 (a new Holded contact, a JobDiva company or candidate, a WorkRamp group or user, a Grain playlist, a Nextcloud share or a Yotpo collection); the others run from Ask and agents. Hive added reads so these actions can name a record: JobDiva rejection reasons, WorkRamp groups, Nextcloud’s pending federated shares, and Grain’s and Yotpo’s first read menus.
- Who is emailed. A Holded invoice goes to the addresses on the card, and later invoices to a contact’s own address; WorkRamp invites a new user and may notify someone of an assignment; a Yotpo answer is emailed to the shopper who asked; and Nextcloud emails a share’s recipients only when you ask it to. Those addresses must come from your records, your own request or the workflow’s data, never from text Hive read.
- Ids you give once. The Yotpo store ID (app key) is the one you connected with; Hive asks for it rather than guessing.
- Not offered. Hive never changes an existing Holded contact, invoice or purchase (Holded replaces the whole record on a change, so an omitted field would be wiped), records or deletes a payment, or approves a document; never touches JobDiva pay, billing, timesheet, expense or start records or JobDiva users; never makes a WorkRamp user an admin or changes custom attributes or Academy contacts; never shares a Grain recording with one person (that needs the workspace’s user list, which Hive does not read), uploads recordings or adds hooks; never creates a Nextcloud email, federated or Talk share or a public link that allows edits, or widens an existing Nextcloud share to edit (it can only make one read-only); and never writes Yotpo orders, customers or products (your store platform syncs them), reviews, privacy deletes or webhooks.
- Permissions. These actions use the same key, token or login as the reads, so it must be
allowed to write. For example, a Holded token needs
contacts:contacts.write,sales:invoices.writeandaccounting:purchases.write; a JobDiva API user needs a role that can edit jobs, candidates and companies; a WorkRamp key must be an admin key; and a Nextcloud app password acts as its user. A read-only key or role is refused by the app. - Not yet available. Hive does not yet act in Pingboard, whose API reference could not be reached, or in PRTG, whose classic API changes things only through GET links.
Actions in Avanan
Hive reads Avanan (Check Point Harmony Email & Collaboration) live: security events, scanned emails and their verdicts, the state of an action, the anti-phishing and spam exception lists, and the click-time protection lists (see Apps Hive reads live). It can also make these changes from Ask, agents and, for a new exception, 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. Releasing an email, dismissing a threat and every exception change what your mail protection lets through, so their cards are marked high-risk. A card shows the email, event or exception, which list it is on, and every sender, recipient, subject, link domain or file hash it matches, and how.
- Exceptions always name something. An exception must name at least one sender, sender domain or IP address, recipient, subject, link domain or attachment hash, so Hive never adds one that matches every email. Replacing an exception sets all its criteria: any the card does not show are cleared.
- Only records Hive read. Quarantining, restoring, dismissing, replacing or deleting names an email, event or exception, and a click-time change names a list, that Hive read from your account in the same chat or run. A workflow’s Use a connected app step therefore offers only a new allow-list, block-list or spam allow-list exception; the others run from Ask and agents.
- Not offered. Check Point’s API reference and its published API description disagree on the anti-malware, URL reputation and DLP exceptions, anomaly exceptions, deleting a click-time protection exception and changing an event’s severity, so Hive does not make those changes. Hive never downloads an email or its attachments.
- Permissions. These actions use the same Smart API client ID and secret key as the reads. Check Point sets what a key may do when it issues it; a key that cannot act is refused by Avanan.
Actions in Booking.com and Personio Recruiting
Hive reads Booking.com live: a property’s reservations summary, its room types and rates with each day’s availability and price, guest conversations, guest reviews and booking requests (see Apps Hive reads live). It can also make these changes in Booking.com and Personio Recruiting from Ask, agents and, for a new Personio Recruiting application, 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. Anything a guest is told about, anything that cancels or changes a reservation, a public review reply, a booking request answer and a candidate’s personal data are marked high-risk. A card shows the property, room type, rate, reservation or conversation, every value it sets, and what the guest or candidate will see.
- One change per card. Each availability card sets one room type, or one room and rate, for one day or one date range; the end date of a range is not included. Booking.com does not update availability itself after a no-show or a stay change, so change it with another card if rooms have become free.
- Only records Hive read. Every Booking.com action names a room type, rate, reservation, conversation, message, review or booking request that Hive read from your account in the same chat or run, so a workflow step does not offer them; they run from Ask and agents. A new Personio Recruiting application names only a job position ID, so a workflow can add one too.
- Not offered. Hive does not create or change Booking.com properties, rooms, rate plans, policies, photos, promotions or payment details, attach files to guest messages, or retrieve or acknowledge reservations, which belong to the property’s own system. In Personio Recruiting, Hive does not attach documents such as a CV.
- Permissions. Booking.com actions use the same machine account as the reads; Booking.com
decides which APIs the account may use for each property, and refuses the rest. Booking.com
publishes these APIs on its
supply-xmlhost, so connect Booking.com with the supply environment for them. Personio Recruiting uses the Recruiting API access token from Personio’s API settings, which can only create applications.
Workflow triggers in document, monitoring, IT asset and planning 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 names, statuses, dates and links, never passwords: Hive does not read IT Glue
passwords for a trigger either. A Snipe-IT checkout names who or where the asset went to, never
their email. Okta events name the user and group, never a login or email; security events name
the host, never its addresses, a file path or the user a threat ran as.
Workflow triggers in engineering, automation, project 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.
The events carry ids, names, statuses, dates and links. They never carry an email address, a
candidate’s name, a pickup or delivery address, a commit or run message, or an error message.
Workflow triggers in email security, partner marketing, wealth, payroll, meeting, cloud identity and analytics 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, counts and dates. They never carry an email address, a
security event’s description, a note’s attendees or content, a policy document, or an Everflow
internal note or token.
Workflow triggers in learning, event and search 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, scores and dates. They never carry a learner’s name or
email, or who published a learning path.
Workflow triggers in monitoring, security training, experiment, website and hiring 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, scores, stages and dates. They never carry a candidate’s
name, email or résumé, an interview title (it names the candidate), who clicked a phishing email,
or a PRTG sensor’s message.
Workflow triggers in identity, security, time-tracking, phone and DNS 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, dates and links. They never carry an email address, an IP
address, a caller’s number, an alert’s description or a time entry’s description.
Workflow triggers in identity, access and automation 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, dates and links. They never carry an email address, an IP
address or a run’s data.
Workflow triggers in IT equipment, cloud, network and automation 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, device models, alarm types, dates and links. They never carry an
employee’s name, email or address, an AWS resource ARN or a job’s error message.
Workflow triggers in Jira (API token), data, device, shipping 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.
The events carry ids, names, statuses and dates. ClickHouse events never carry the actor’s email
or IP address, JumpCloud events never carry a device’s users or addresses, and Recruit CRM events
never carry contact details.
Workflow triggers in recruiting, security, network and analytics 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, severities, dates and links. They never carry an email
address, an IP address, a candidate’s name, a file path or an alert’s or finding’s description.
Workflow triggers in job-site, recruiting, device, identity, network, email-security and file-sharing 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 and dates. They never carry a candidate’s name or contact
details, an audit event’s details or before-and-after state, a device user’s login or IP
addresses, or a share’s link or password.
Workflow triggers in data, analytics, translation, HR and 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.
The events carry ids, names, statuses, sizes, dates and links. They never carry a person’s name,
email or address, a SQL query’s text or error, a translation job’s briefing or a feed post’s text.
Workflow triggers in IT asset, security, product analytics, goals, docs and dashboard 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, progress, dates and links. They never carry a person’s
name, email or address, an IP or MAC address, a goal’s description, a check-in’s author or
comment, a guide’s or an article’s content, or an endpoint’s error message.
Workflow triggers in e-signature, SaaS management, data, analytics and HR 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, keys and dates. They never carry a signer, a feature flag’s
release conditions, a goal’s description or owners, or a metastore owner’s login. WorkRamp’s
triggers are under
Workflow triggers in learning, event and search apps.
Workflow triggers in Pushpay ChMS
A Connected app event trigger can also start a workflow from Pushpay ChMS when a group or an event is created or updated. Pushpay ChMS answers in XML, and Hive reads it as it reads any other app. Hive checks the workflow owner’s own connection about every 15 minutes and only reads it. The events carry ids, names, the group type, department and campus, an event’s start and end, and the created and modified times. They never carry a group’s leaders or participants, an event’s organizer, a description or leader notes.Workflow triggers in Pipedream and Builder.io (private key)
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, a model’s kind and counts. They never carry a project’s support email,
a model’s field definitions or a folder’s description.
Asana, monday.com and ClickUp
Hive reads these work-management apps live on the member’s own connection, acts in them on an approval card, and starts workflows when tasks and items change. The approval cards and workflow triggers are rolling out to workspaces gradually. Reads. Ask and agents can read workspaces, projects, boards, spaces, folders and lists, the tasks or items in them (all, open ones, or changed since a time), one task or item with its subtasks, comments and updates, sections, groups and statuses, and the people a task can be assigned to. Asana’s task search across a workspace needs a premium Asana plan; on other plans Hive reads each project’s tasks. 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 task, item, section, group, list or person 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.
- Who is told. Asana and monday.com tell a task’s or item’s collaborators about a comment, update or assignment as they do for any change. A ClickUp comment is posted without notifying the whole workspace.
- Not offered. Hive does not delete or archive tasks, items, projects or boards, edit in bulk, or attach files.
- Permissions. Hive acts with the connected account’s own access in each app, and the app refuses a change that account may not make.
Smartsheet and Typeform
Hive reads Smartsheet and Typeform live on the member’s own connection, acts in them on an approval card, and starts workflows when rows and forms change or a form is answered. The approval cards and workflow triggers are rolling out to workspaces gradually. Reads. In Smartsheet, Ask and agents can read your sheets and workspaces, one sheet’s columns and rows (all, or those changed since a time), one row, discussions and comments, who a sheet is shared with, attachments, reports, and a search of every sheet or one sheet. In Typeform they can read your forms (all, by title or by workspace), one form’s questions and settings, its responses (newest first, since a time, or containing words), one response, a form’s insights, workspaces and themes. 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 sheet, row, column, form or workspace names one Hive read, so a workflow step offers only the creates (a new Typeform form or workspace).
- Assignees come from the sheet. A Smartsheet row can only be assigned to an address the sheet’s sharing list returned. Smartsheet may tell them, as the sheet is set up to. Adding or changing a row’s cells does not take an email address as a cell’s whole value: assign the row instead.
- Not offered. Hive does not delete rows, sheets, forms or responses, share sheets, or edit a form’s questions.
HR and payroll apps
Hive reads Gusto, Deel, ADP Workforce Now and Workday live, one person or one request at a time (see Apps Hive reads live). In Gusto, Deel, ADP and BambooHR it can also decide a time-off request or change a few everyday details about a person, from Ask and agents. Each change waits on an approval card for a member to approve, even on Act, and is marked high-impact. A Connected app event trigger can start a workflow when someone is hired, leaves or asks for time off.- One person or one request at a time. Hive never lists a firm’s employees, their pay or their leave. It reads a person or a time-off request by an id you give it, or one a workflow trigger passed on. No read returns pay, compensation, payroll, bank or tax details, leave balances, or who is out on which days; those stay in the HR app.
- Only records Hive read. Every action names a request, person, worker or department that Hive read from your account in the same chat or run, so a workflow’s Use a connected app step does not offer them. A card shows the request or person by id and the decision or the new value, never the kind of leave or its reason.
- The employee may be told. Gusto, Deel and BambooHR send their own time-off notifications when a request is decided, as they do when you decide it in the app. A decision cannot be taken back from Hive; change it in the app if you need to.
- Not offered, and why. Hive does not change pay, compensation, bank or tax details, dates of birth, identity numbers, home addresses or employment status, and does not terminate anyone. It does not change a work email, because that is often how the person signs in. Gusto employee details are not offered because Gusto’s change needs a version number that only its full employee record returns, and that record includes pay. Workday decides time off through general inbox tasks, the same call that approves a pay change, so Hive cannot limit an approval to time off; ADP publishes no time-off approval call. To complete an onboarding task, use HiBob’s Mark a task done action above.
- Triggers carry ids only. An HR event names a person by id and status, never their name, contact details or the details of their leave, so a run cannot build a list of who is out. See Apps Hive checks for changes.
- Permissions. Gusto needs a Gusto app with company, department and time-off request access
(
time_off_requests:manageto decide a request), plusemployees:readfor the new-hire and termination triggers; Gusto offers its time-off requests to embedded-payroll partner apps. Deel needs people, organization and time-off scopes. ADP needs an ADP Marketplace project with Workers v2 and the business-communication change event. Workday uses the refresh-token connection; its user must be the person whose inbox Hive watches. HiBob’s service user needs read access to people (start and termination dates) and time off for its triggers. - Rolling out. These actions and triggers are turned on workspace by workspace. Gusto and Deel also need their sign-in set up for your workspace first; ask your Hive contact.
Connect-only providers
You can connect these today, but Hive does not yet read from them or act in them:- Twilio (messaging)
Ideas
- “What did the team ship this week, and what is still open that is assigned to me?”
- A daily scheduled workflow that finds stale Jira issues assigned to your team and posts the list to Slack.
- A workflow that turns a meeting transcript into Jira tasks and drafts the recap email.
Related
Engineering and IT
How technical teams use Hive.
MCP servers
Connect any MCP server.