| name | plaud-recordings-to-google-calendar-events |
| description | 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. Eac. |
| version | 1.0.1 |
| homepage | https://www.agentpmt.com/agent-workflow-skills/plaud-recordings-to-google-calendar-events |
| compatibility | Agent instructions for AgentPMT-hosted remote tool calls. Follow this skill body for supported account, wallet, and setup routes. No local command runtime is declared. |
| metadata | {"author":"agentpmt","openclaw":{"homepage":"https://www.agentpmt.com/agent-workflow-skills/plaud-recordings-to-google-calendar-events"}} |
Plaud Recordings to Google Calendar Events
Freshness
Last updated: 2026-07-26.
If the current date is more than 7 days after the last updated date, reinstall this skill from skills.sh or ClawHub before relying on endpoints, schemas, setup steps, or examples.
What This Workflow Does
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.
Required Setup
- AgentPMT overview:
../what-is-agentpmt.
- Account MCP/REST setup:
../agentpmt-account-mcp-rest-api-setup.
Core AgentPMT setup skills:
- What AgentPMT is: ../what-is-agentpmt
- AgentPMT account MCP/REST setup: ../agentpmt-account-mcp-rest-api-setup
skills.sh install script:
npx skills add AgentPMT/agent-skills --skill what-is-agentpmt
npx skills add AgentPMT/agent-skills --skill agentpmt-account-mcp-rest-api-setup
Workflow Session Management
Call AgentPMT-Workflow-Skills with start_workflow before the first step and end_workflow after the final step.
{"action":"start_workflow","skill_id":"plaud-recordings-to-google-calendar-events"}
{"action":"end_workflow","skill_id":"plaud-recordings-to-google-calendar-events","rating":5,"comment":"completed"}
Workflow Process
- Get User Timezone and Date
- Ask for the Recording Window
- Prompt: Establish the exact window of recordings this run covers, in the user's own timezone.
- List Plaud Recordings
- Tool product: Plaud.
- Tool skill:
../plaud.
- ClawHub page: https://clawhub.ai/agentpmt/plaud.
- skills.sh install:
npx skills add AgentPMT/agent-skills --skill plaud.
- Marketplace: https://www.agentpmt.com/marketplace/plaud.
- Tool instructions: 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 recording's LOCAL time (for example '2026-07-25 19:53:50') while start_at and created_at are UTC written as naive strings with no Z and no offset (the same recording reads '2026-07-25T23:53:50'). Treat start_at as UTC, convert it into the user's timezone, and only then decide whether the recording falls inside the requested local window. This matters twice over here, because the recording's local date is also the anchor for resolving every relative date spoken inside it. Then skip any recording id already in the ledger sheet.
- Each New Recording
- Iterate over the configured collection, then continue through the connected workflow path.
- Fetch Transcript
Tool Skill Links
AgentPMT Reference
