Loading...
How to connect ReVoice to Zapier, use the triggers and remove the connection.
On this page
ReVoice is an AI meeting-intelligence platform that transcribes your meetings and generates summaries and action items. The ReVoice integration for Zapier starts your Zaps when something happens in a meeting: a summary is ready, a meeting starts or ends, a transcript is ready, or an action item is found.
You connect ReVoice in Zapier by signing in to ReVoice and approving. There is nothing to copy or paste. Your Zaps then receive meeting events. A connection on its own does nothing: the Zapier card in ReVoice shows the real state of the setup.
Connecting Zapier has three parts: connect ReVoice in Zapier, choose what should happen, and approve that your meetings are sent.
| Access | What the connection can do |
|---|---|
| Zapier connection (ReVoice sign-in) | Identify your account so Zapier can label the connection, add and remove the Zap subscriptions that Zapier registers for you, and read the recent meeting data Zapier shows as test data while you build a Zap. It cannot edit or delete meetings, summaries or transcripts, and it cannot read anything else in ReVoice. Disconnecting ends it immediately. |
If a step does not work, see the Troubleshooting section below.
After setup, you can use the following:
Zapier's Terms of Service do not allow sensitive personal data to be sent through Zapier: health information, financial account numbers, government ID numbers and the special categories of personal data in the GDPR. A meeting is free text, and ReVoice cannot know whether a meeting title or an action item contains such data. So ReVoice does not send the text at all.
A Zap receives identifiers, states and times, never anything that was said or written in a meeting. Specifically, ReVoice does not send the transcript, the summary text, the meeting title, the text of an action item, the name of the person responsible, participant names or email addresses, recordings, or any token, key or secret. This is how the integration is built (an allow-list of fields per event); it is not a filter that looks for words.
To read the content of a meeting, open the link every event carries. It opens only for a signed-in ReVoice user who has access to the meeting.
You decide what leaves ReVoice. Personal meetings are sent only after you approve it yourself, delivery stops from the next event when you withdraw the approval or when your plan, your company or the sharing rule of a Space no longer allows it, a deleted meeting sends nothing, and disconnecting Zapier removes the Zap subscriptions.
Your own Zaps can still add data from other apps. What you do with the events in Zapier, and the data you add there, is your responsibility under Zapier's terms.
The ReVoice app for Zapier uses the public ReVoice API at https://re-voice.io. The app signs in with OAuth 2.0 (authorization code with PKCE): you sign in to ReVoice from Zapier and approve, and ReVoice gives Zapier a one-hour access token that is renewed with a refresh token. Every call carries the access token as a Bearer token: Authorization: Bearer <token>. All calls use HTTPS and JSON.
A token is accepted only while the connection exists, it has not expired and its owner is not suspended, and it works only on the three calls listed below. An ended, expired or unknown token is answered with 401 and nothing is read or changed. GET /api/v1/me is the connection test: it answers 200 with { email, name, label } and returns no meeting data. The label is the account email.
Limits: the shared API rate limit answers 429 when exceeded, an account can hold at most 50 Zap subscriptions (409 beyond that), and a hook address must be a public HTTPS URL.
These are the calls the Zapier app makes. Zapier calls subscribe when a Zap is turned on and unsubscribe when it is turned off.
| Call | What it does and what it answers |
|---|---|
| GET /api/v1/me | Tests the connection and labels it. 200 { email, name, label }, or 401. |
| POST /api/v1/zapier/subscribe | Body { "event": "<event>", "targetUrl": "<Zapier hook URL>" }. Registers the hook. 201 { id, event } for a new hook, 200 with the same id for a repeat of the same request. 400 for an unsupported event or a URL that is not public HTTPS, 401, 403 when the plan or the company does not allow the integration, 409 at the 50 subscription limit. |
| DELETE /api/v1/zapier/subscribe?id=<id> | Removes a hook that Zapier registered for this account. 200 { success, removed }. Repeating the call, or using an id that belongs to someone else, answers 200 with removed false. Webhooks created by hand in ReVoice are never removed by this call. |
| GET /api/v1/zapier/sample?event=<event> | Up to three recent real events of the account, shaped exactly like the data of a live event, for the test step in the Zap editor. An event that has not happened yet answers an empty list. |
ReVoice sends one event per trigger, containing only the fields below (an allow-list; any other field is not sent, whatever ReVoice holds). The Zapier app returns these fields plus an id that Zapier uses to avoid running a Zap twice for the same event, and a link to the meeting.
| Event (trigger) | Fields |
|---|---|
| summary.generated (New Meeting Summary) | conversationId, summaryId, type (AUTO, CUSTOM or TEMPLATE) |
| meeting.started (Meeting Started) | meetingId, conversationId, status (RECORDING), startedAt |
| meeting.ended (Meeting Ended) | meetingId, conversationId, status (COMPLETED), endedAt, durationMinutes |
| transcript.ready (Transcript Ready) | conversationId, status (TRANSCRIBED), transitionedAt. The event says that the transcript exists; it does not contain it. |
| commitment.created (New Action Item) | conversationId, summaryId, and a list of action items, each with type, status, dueDate and hasAssignee (true or false). The app starts one Zap run per action item. |
No event carries a transcript, a summary text, a meeting title, an action item text, a name, an email address, a recording or a secret. Times are ISO 8601 in UTC. Events other than these five are never sent to Zapier.
Errors are JSON of the form { "error": "<message>" } with these status codes.
| Status | Meaning and what to do |
|---|---|
| 400 | The request is not valid: an unsupported event, a URL that is not public HTTPS, or malformed JSON. |
| 401 | The token is missing, invalid, ended or expired, or the account is suspended. Reconnect the account in Zapier. |
| 403 | The plan does not include webhook integrations, or the company does not allow Zapier for this account. |
| 409 | The account has reached 50 Zap subscriptions. Turn off Zaps that are no longer used. |
| 429 | Too many requests. Wait and try again; Zapier retries by itself. |
| 500 | ReVoice could not complete the request. Try again; if it keeps failing, contact support. |
You can remove the integration from either side.
From ReVoice: go to Integrations, then Zapier, open Manage connection (shown when a Zap is on) and select Disconnect. ReVoice ends the Zapier connection and removes every Zap subscription that Zapier registered for your account.
From Zapier: turn off or delete a Zap, and Zapier removes its subscription in ReVoice. Disconnect the ReVoice account in Zapier under My Apps to remove the connection there.
Can Zapier change my ReVoice data? No. The connection can identify your account, manage the Zap subscriptions Zapier registers and read recent event metadata for test purposes. It cannot edit or delete meetings, summaries or transcripts.
Does ReVoice send meeting text to Zapier? No. No transcript, summary text, meeting title, action item text or name is sent, only identifiers, states, times and a link. Zapier's Terms of Service do not allow sensitive personal data to be sent through Zapier, and a meeting's free text cannot be guaranteed free of it.
Do I have to copy a key or a password? No. You sign in to ReVoice and press Connect. ReVoice gives Zapier short-lived access that renews itself and that you can end at any time with Disconnect.
Are my private meetings sent to Zapier automatically? No. Your personal meetings are sent only after you approve it yourself, and only while your plan, your company and the Space rules allow it. You can withdraw the approval at any time and delivery stops at the next event.
Do I need a paid plan? Yes. Zapier is available on plans that include webhook integrations (Individual and higher).
Where is my data stored? Connection data is stored in our EU-hosted database. Events go to the Zapier hook address you chose, over HTTPS, signed. See our Privacy Policy for details.
Need help with the Zapier integration? Reach us through any of these channels: