Hiver and Zapier: what syncs, what doesn't, and how to set it up
Zapier's Hiver app turns Hiver shared-mailbox events into triggers for other apps. The docs list triggers only, so nothing writes back to Hiver, and they state no plan requirement.
- Connector
- Hiver app in the Zapier directory, documented in Hiver's help center; the pages read don't name who built it or state a fee
- Sync direction
- Hiver → Zapier → other apps; the docs list triggers and no actions
- Setup time
- Seven steps, one Hiver admin toggle and one API key; the docs give no time estimate
- Availability
- Hiver plan requirement not stated on the pages read; Zapier lists a free tier
- Our rating
- 3 out of 5. Eight documented Hiver triggers feed Zapier, but no actions are documented, so nothing writes back, and no plan requirement is stated.
| What | Direction | Detail |
|---|---|---|
| New inbound conversation | Hiver → Zapier | Fires when a conversation arrives in a shared mailbox. Zapier labels the trigger Instant. You can filter by tags, assignee, status, directory contact and company. |
| New outbound conversation | Hiver → Zapier | Fires when a new conversation is sent from a shared mailbox. Same filter fields as the inbound trigger. |
| Email sent or received | Hiver → Zapier | Fires on any email sent from or received into a shared mailbox, not only on new conversations. |
| Conversation updated | Hiver → Zapier | Fires when status, assignee, contact or tags change. The trigger has an Update Types field to narrow it. |
| New note | Hiver → Zapier | Fires when someone adds a note to a shared conversation. |
| SLA breaches | Hiver → Zapier | Two triggers: first response overdue and resolution overdue. Both offer an SLA Policy filter. Hiver's article calls them breached; Zapier calls them overdue. |
| SLA due soon | Hiver → Zapier | Two triggers on Zapier's listing: first response and resolution nearing violation. Hiver's help article doesn't list them. |
| CSAT responses | Hiver → Zapier | Fires when a customer satisfaction rating is received for a conversation. |
Setting it up
- In Gmail, open Hiver Settings, then Admin Panel.
- Go to Integrations, then Apps, then Zapier, and turn the Zapier toggle on.
- Copy the API key shown on that page.
- In Zapier, select Create, then New Zap, and click the Trigger block.
- Search for Hiver, select it, and choose Sign in.
- Paste the API key and select Yes, Continue to Hiver.
- Pick a trigger, choose the shared mailbox, then add the action app of your choice.
Where the integration stops
- The docs list no actions. Hiver's article and the Zapier listing show triggers only, so a Zap can't be documented as creating or updating a Hiver conversation. Check the action list in the Zap editor, or use the Hiver API.
- Hiver automations run before the Zap. Assignee, tags and status can change before the Zap fires, so the data your Zap receives may differ from the original event.
- Every trigger requires a shared mailbox. The docs describe no triggers for anything else.
- No plan requirement is stated. Neither Hiver's article nor Zapier's listing says which Hiver plan includes the Zapier toggle, so confirm in your Hiver admin panel before you plan around it.
- Trigger names differ between sources. Hiver's article and Zapier's listing disagree on names and count, and Zapier's list has a Load more button. Treat the Zap editor as the final list.
Zapier's Hiver app sends events from Hiver shared mailboxes to the other apps Zapier connects. It suits admins who want a Slack alert, a CRM record or a reporting row when a conversation arrives, changes or breaches an SLA. Hiver's help center documents the setup.
The fact that surprises teams: the documentation lists triggers and no actions. Events leave Hiver, but the pages I read don't show Zapier changing anything inside Hiver. For Hiver's own setup in Gmail, see Hiver and Gmail.
Hiver sends events out; the docs list no way back in
Hiver's article names eight triggers: new inbound conversation, new outbound conversation, email sent or received, new note, two SLA breaches, new CSAT response and conversation updated. Zapier's listing adds two "due soon" SLA triggers. Each one starts a Zap instantly.
Each trigger asks for a shared mailbox. Most also offer filters for tags, assignee, status, directory contact and company. SLA triggers filter by SLA policy instead of status.
Hiver's own page describes use cases that all run one way. Examples are a Slack alert when an SLA breaches, a CSAT rating pushed to a channel or report, and a CRM record updated when a conversation closes. If you need Zapier to change Hiver, check the Zap editor first. Otherwise look at the Hiver API.
Your Zap sees the conversation after Hiver's automations
Hiver runs its automations before the Zap triggers. A rule that assigns a conversation or adds a tag can finish first. The Zap then receives the new values, not the ones the event started with.
Test each Zap against a real conversation that your automation rules touch. Compare the assignee, tags and status in the Zap's test data with what you expect.
Native integrations cover CRMs; Zapier covers the rest
Hiver's integrations page lists native connections for Salesforce, NetSuite, HubSpot, Jira, Shopify, Asana, QuickBooks and Pipedrive. Hiver describes those as in-app views and updates. Hiver says Zapier covers everything else.
Check the native list first for your CRM. Choose Zapier when the target is a tool outside that list, or when you want an alert or a row logged on a Hiver event. Zapier's listing shows templates for Asana tasks, Slack messages, Pipedrive deals, Trello cards and Zendesk Sell deals from new shared-mailbox emails. The Zapier integrations page covers the platform side, and the Hiver vendor page and Hiver pricing cover the product.
Setup is one toggle and one key
An admin turns Zapier on in the Hiver Admin Panel and copies the API key. Anyone building Zaps then pastes that key when they sign in to Hiver inside Zapier. The sources don't say whether the Zapier toggle depends on your Hiver plan, so check that in the admin panel before you commit.