Save Plaud recordings to Google Docs and share in Slack

By General Input

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.

Integrations

  • Plaud
  • Google Docs
  • Slack

Type

Deterministic Code

Categories

  • Operations
  • Personal Productivity

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.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsA searchable RFP answer library your bid team drafts fromRun your weekly Lever pipeline review and decide in the appLinkedIn creator sourcing and vetting workbench for B2BWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollments