Automate Wave with Zapier
Send every finished session — summary, transcript, title and link — to 8,000+ apps the moment Wave is done with it, with no code.
Wave's Zapier integration fires a trigger every time a session finishes processing, with the summary, the speaker-labelled transcript and a link to the session. Connect it once and Zapier can post the summary to Slack, file it in Notion or Google Sheets, create a CRM note, or start any other Zap you can build.
What you need
- A Wave account on the web, desktop or mobile app.
- A Zapier account. Zapier's free plan is enough to try it; Zapier bills for higher volumes, Wave does not charge for the integration.
Connect Wave to Zapier
From then on each session fires the trigger within seconds of its summary being ready.
What the trigger sends
Every delivery has the same fields, so your Zap can map any of them:
| Field | What it holds |
|---|---|
| Title | The session title, as shown in Wave |
| Summary | The AI summary |
| Transcript | The full transcript with speaker names, one line per turn |
| Notes | Anything you typed in the session's notes |
| Duration (seconds) | Length of the recording |
| Session Type | recording, phone, meeting, desktop or import |
| Meeting Platform | For meeting bots: zoom, google-meet or microsoft-teams |
| Language | The language Wave detected, as a code such as en |
| Ready At | When processing finished |
| Session URL | A link that opens the session in the Wave web app |
| Session ID | Wave's identifier for the session |
Fields that do not apply to a session arrive empty rather than missing, so a Zapier Filter step can test them safely.
Very long recordings are cut at about 1.5 million characters of transcript, roughly 40 hours of speech, because Zapier limits the size of a single delivery. The summary is never cut.
What fires, and what does not
- Every session that finishes processing fires once: phone recordings, meetings, desktop recordings, imports and phone calls.
- A recording you continue later does not fire again when the extra audio is added.
- Edits to a session after it is ready (renaming, fixing speakers, regenerating the summary) do not fire.
- Each Zap on the same Wave account gets its own delivery. Two Zaps, two deliveries.
Staying connected
Your Wave connection in Zapier renews itself for as long as the Zap keeps running. If a Zap stays off for more than 90 days the connection expires; turn the Zap on again and Zapier asks you to sign in to Wave once more.
To disconnect, delete the Zap, or remove the Wave AI connection under Apps in your Zapier account. Deleting your Wave account removes every Zapier connection as well.
FAQ
Add a Zapier Filter step after the trigger. Filter on Session Type to run only for meetings, on Title for a keyword, or on Transcript to look for a phrase.
Not yet. The integration is trigger-only. To read or search sessions from other tools use the Wave Developer API or connect an AI assistant with the Wave Agents toolkit.
That works. Each Zapier account gets its own connection and each Zap its own deliveries.
¿Te resultó útil este artículo?
¿Necesitas más ayuda?