# Plaud Recordings to Google Calendar Events > Puts the meetings you agree to out loud straight onto your Google Calendar, without Zapier in the middle. Plaud's own app has no Calendar integration, so this closes that gap directly: each new recording is scanned, the transcript pulled, and any genuine scheduling commitment spoken in it ("let's do Tuesday at 3", "I'll come back out Thursday morning") is extracted with the relative date resolved against the recording's own date and your timezone. Each one becomes a Google Calendar event with the agreed time, a title naming who and what, and the surrounding quote from the transcript in the description so you can see exactly what was said. Vague intentions with no time attached ("we should catch up sometime") are deliberately ignored rather than guessed into a slot. Because it uses the full Google Calendar connector it also reads back, so an agent can answer what your week looks like from the same connection. A Google Sheet ledger records every recording id and every event created, so a scheduled run never double-books you. Content type: workflow Source URL: https://www.agentpmt.com/agent-workflow-skills/plaud-recordings-to-google-calendar-events Markdown URL: https://www.agentpmt.com/api/agent/workflows/plaud-recordings-to-google-calendar-events?format=agent-md Updated: 2026-07-26T00:01:29.867Z Author: firef1ie --- Estimated time saved: 10 minutes. ## Tools - Get Users Current Time / Date - Plaud - Google Calendar - Google Sheets ## Workflow Outline 1. Get User Timezone and Date: Get the user's current local date, time, timezone and UTC offset. The requested window, every recording timestamp, and every relative date spoken in a recording are resolved again... 2. Ask for the Recording Window: Goal: Establish the exact window of recordings this run covers, in the user's own timezone. | Inputs: The user's local date, time, timezone and UTC offset from the previous step, plus the last processed timestamp in the... 3. List Plaud Recordings: Call list_files with the widened UTC date_from and date_to from the previous step. Plaud's timestamps are inconsistent and must be handled deliberately: the name field carries the... 4. Each New Recording: Repeat this section for each recording. Handle one unprocessed recording at a time, using that recording's own LOCAL date and time as the anchor for resolving relative dates spoke... 5. Fetch Transcript: Call get_transcript with this recording's file id, reusing Plaud's existing transcript when one is available. 6. Summarize the Run: Goal: Tell the user exactly what landed on their calendar and what was deliberately left off. | Inputs: The per-recording extraction and creation results, and the window that was used. | Outputs: The window covered stat... 7. Extract Scheduling Commitments: Goal: Find every concrete scheduling commitment spoken in the conversation and resolve it to a real calendar date and time in the user's timezone. | Inputs: The transcript of one recording, the recording's LOCAL date an... 8. Create Calendar Events: Create each extracted event on the user's primary calendar in their own timezone, putting the source quote and the recording link in the description. If an event with the same tit... 9. Log to Ledger Sheet: Append the recording id, its local recorded time, the events created, and any recordings that yielded nothing, so the next run skips them and the user has an audit trail of what w... ## Frequently Asked Questions ### How do I connect this workflow to my local agent like OpenClaw or Claude Code? You can install the local MCP server by opening a terminal and running: ``` npm install -g @agentpmt/mcp-router agentpmt-setup ``` This will connect you to local agents like Claude Code, Windsurf, Grok Build, Cursor, etc. Alternatively you can connect to the hosted version with this config block, no installation required: ``` { "mcpServers": { "agentpmt": { "type": "streamable-http", "url": "https://api.agentpmt.com/mcp", "headers": { "Authorization": "Bearer ", "x-instance-metadata": "{\"client\":\"generic-mcp\",\"platform\":\"remote\"}" } } } } ``` [View MCP Connection Instructions](/docs/mcp-reference/connection) for more details. ### How do I trigger this workflow? You can use it here in the browser by clicking the 'Try It' button. If you 'star' the workflow it will save to your dashboard for quick access. To use the workflow in an external agent, make sure you have followed the steps to connect it to the MCP server and then copy / paste this prompt, or just tell it to use the AgentPMT MCP server and use this workflow. > Call the AgentPMT-Workflow-Skills tool with action 'get\_workflow\_skill' and skill\_id 6a6534ddb640fe17224ac768 ("Plaud Recordings to Google Calendar Events").