Turn every Plaud recording into a structured Notion note
When Plaud finishes transcribing, an agent files a clean, categorized entry in your Notion meetings database so nothing stays trapped in a raw transcript.
Build an agent workflow that converts every Plaud recording into a structured Notion knowledge-base entry, so I never have to touch a raw transcript again.
Trigger: a Plaud webhook subscription on the audio_transcribe.completed event. Only proceed when the event status is SUCCESS. Ignore FAILURE and REVOKED events.
Step 1. Call Plaud Get Workflow Result with the workflow_id from the webhook payload. Extract the full transcript text, the AI summary, the recording title (if any), the recording date or created_at timestamp, the duration, and any attendee or speaker metadata Plaud returns.
Step 2. Have the agent read the transcript and summary and categorize the content into these discrete buckets: Decisions Made, Action Items, Open Questions, Key Insights, and Mentioned People. For Action Items, capture the owner if one is clearly named in the transcript, and the due date if one is mentioned; otherwise leave them blank. For Mentioned People, list the distinct names that come up, deduplicated.
Step 3. Generate a meeting title in the form "YYYY-MM-DD: <short topic>", where the topic is a 4 to 8 word phrase the agent infers from the transcript or summary. If Plaud already returned a title, prefer that.
Step 4. Call Notion Create a Page as a child of a pre-configured "Meetings" database. The database_id should be a workflow parameter the user fills in. Populate the database properties: Name (the generated title), Date (the recording date), Attendees (the Mentioned People list), and Summary (a 2 to 3 sentence condensed version of the Plaud AI summary).
Step 5. Populate the page body with these Notion blocks, in this order: a heading_2 "Summary" followed by a paragraph with the Plaud AI summary; a heading_2 "Decisions Made" followed by a bulleted list of decisions; a heading_2 "Action Items" followed by to_do blocks (one per item, unchecked) including the owner and due date inline when known; a heading_2 "Open Questions" followed by a bulleted list; a heading_2 "Key Insights" followed by a bulleted list; and a heading_2 "Mentioned People" followed by a bulleted list of names. Skip any section whose bucket is empty rather than rendering an empty heading.
Step 6. After the page is created, do nothing else. No Slack ping, no email, no follow-up workflow. The Notion entry is the deliverable.
Configurable inputs the user should set up front: the Plaud connection, the Notion connection, and the Notion Meetings database_id. Everything else should be inferred by the agent at runtime.
Failure handling: if Get Workflow Result returns an error or empty transcript, log the workflow_id and stop without creating a page. If Notion Create a Page fails with a permissions error, surface a clear message that the connection has not been shared with the Meetings database.
Additional information
What does this prompt do?
- Listens for a finished Plaud transcription and pulls the full transcript and AI summary the moment it is ready.
- Sorts the content into clear buckets: decisions made, action items, open questions, key insights, and people mentioned.
- Creates a new entry in your Notion meetings database with the title, date, attendees, and a tidy headed body for each section.
- Renders action items as a Notion checklist so you can tick them off without rewriting anything.
What do I need to use this?
- A Plaud account with developer access so recordings can be read once a transcription completes.
- A Notion workspace with a meetings database that has fields for title, date, attendees, and summary.
- The Notion connection shared with the meetings database so the agent can write into it.
How can I customize it?
- Change the buckets the agent uses (for example, add a Risks section or rename Key Insights to Learnings).
- Point it at a different Notion database, like a Research log or a 1:1 journal, instead of Meetings.
- Adjust how the title is generated (date plus topic, attendee list, or the meeting type).
Frequently asked questions
Do I need to start this manually after each recording?
What happens to the original transcript?
Can I use a database other than Meetings?
What if Plaud cannot identify the attendees?
Will it overwrite an existing Notion page if I record the same meeting twice?
Stop letting recordings die in your transcript app.
Connect Plaud and Notion once, and every recording lands in your knowledge base already categorized and ready to act on.