Save Plaud recordings to Google Docs and share in Slack

Every time Plaud finishes transcribing a recording, file the transcript and summary as a clean Google Doc and post a link in your team Slack channel.

Deterministic Code
PlaudGoogle DocsSlackOperationsPersonal ProductivityMeeting WorkflowsNotifications & AlertsDocument Processing
PromptCreate

Build me a code-based workflow that automatically archives Plaud recordings into Google Docs and announces them in Slack the moment Plaud finishes transcribing.

Trigger: a Plaud webhook on the audio_transcribe.completed event. Only proceed when the workflow status is SUCCESS. Ignore FAILURE and REVOKED events.

Step 1 — Fetch the result. Call Plaud Get Workflow Result using the workflow id from the webhook payload. From the response, pull out the recording title, the recording date, the full transcript text, and the AI summary text.

Step 2 — Create the doc. Call Google Docs Create Document with a title formatted as "[YYYY-MM-DD] - [Recording Title]" using the recording date and title from step 1. Capture the new document id and the shareable URL.

Step 3 — Populate the doc. Call Google Docs Batch Update Document on that document id with the following structure, inserted in one atomic batch (process inserts from highest index to lowest so offsets stay correct):

• A HEADING_1 styled line that says "Summary"

• A paragraph with the full AI summary text

• A HEADING_1 styled line that says "Transcript"

• A paragraph (or paragraphs, split on line breaks) with the full transcript text

Step 4 — Announce in Slack. Call Slack Send a Message to a configurable channel (expose channel as a workflow input, default to a channel name the user provides at setup). The message body should include: the doc title, the first two or three sentences of the summary as a preview, and a Slack-formatted hyperlink to the new Google Doc using mrkdwn syntax like <url|Open in Google Docs>.

Inputs to expose at the top of the workflow: the Slack channel (id or name), and an optional override for the doc title format. Everything else (transcript, summary, doc URL) flows from step to step.

Keep it deterministic — no LLM nodes. Every step is a direct integration call. If any step fails, surface the error and stop; don't post a half-broken Slack message.

Additional information

What does this prompt do?
  • Watches Plaud for newly transcribed recordings and runs the moment one is ready.
  • Creates a tidy Google Doc titled with the date and recording name, with a Summary section on top and the full Transcript below.
  • Posts a Slack message to the channel you pick with the doc title, the first lines of the summary, and a clickable link to the new doc.
  • Runs the same way every time so your meeting archive stays organized without anyone copy-pasting.
What do I need to use this?
  • A Plaud account with developer access so we can pull your finished recordings.
  • A Google account so we can create the Google Doc in your Drive.
  • A Slack workspace and the channel name or ID where the recap should land.
How can I customize it?
  • Change the Slack channel, or send to a private channel or DM instead.
  • Tweak the Google Doc title format, for example put the speaker name or project tag in front of the date.
  • Adjust how much of the summary appears in the Slack preview, from one sentence to a longer teaser.

Frequently asked questions

How fast does this run after I finish a recording?
It runs as soon as Plaud finishes transcribing. Plaud sends a signal the moment the transcript and summary are ready, and the workflow picks it up right away.
Where does the Google Doc end up?
In the Google Drive of the account you connect. You can then move it into a shared folder, or change the workflow to drop it in a specific folder.
Can I send to multiple Slack channels?
Yes. The most common setup is one channel, but you can route different recordings to different channels based on the recording title, tag, or speaker.
Will my full transcript get posted in Slack?
No. Slack only gets the doc title, a short summary preview, and the link. The full transcript lives in the Google Doc.
What if a transcription fails?
The workflow only runs on successful transcriptions. If Plaud reports a failure, no doc is created and no Slack message is sent.

Related templates

Weekend football matchday preview, posted to Slack

Every Friday, get a ready-to-read preview of your league's weekend matches, with positions, form, scorers to watch, and predicted results, posted to Slack.

API-Sports
Slack
Agentic Task
Weekly Braintree revenue and refund report for finance

Every Monday morning, finance leadership gets a clear recap of last week's Braintree sales, refunds, and disputes by email and Slack.

Braintree
Gmail
Slack
Agentic Task
Daily IP reputation screening with Slack threat alerts

Every morning we check your list of IP addresses for abusive activity, update your spreadsheet, and alert your team only about the risky ones.

AbuseIPDB
Google Sheets
Slack
Agentic Task
Turn Heroku deploys into a readable Slack changelog

Every time you ship to Heroku, we post a clear summary to Slack listing what changed, who deployed it, and whether it was a rollback.

Heroku
GitHub
Slack
Agentic Task
Morning team travel briefing with live flight alerts

Every weekday morning, your team gets one Slack briefing on who's flying today, their live flight status, and any delays or cancellations to act on.

AviationStack
Google Sheets
Slack
Agentic Task
Weekly self-audit of your company's IP address reputation

Every Monday we scan your office, VPN, mail, and hosting IP ranges for abuse reports, post a summary to Slack, and open a ticket when anything crosses your risk line.

AbuseIPDB
Slack
Jira
Agentic Task

Stop copy-pasting your recording transcripts.

Connect Plaud, Google Docs, and Slack once. Every recording lands as a Google Doc and a Slack link, automatically.