# Plaud Spoken Commitments to Telegram Reminders > Catches every date and time you commit to out loud in your Plaud recordings — "I'll send it Thursday", "meet Bob at 3" — and sends the whole batch to you on Telegram. Scans each new recording, pulls the transcript (reusing the recording's own transcript when one exists), extracts spoken commitments and resolves relative dates against the recording date and your timezone, and logs them to a "Plaud Commitments" Google Sheet. Every run then sends one Telegram digest listing all open commitments sorted by due date, with overdue items flagged. Mark a row "done" in the sheet to drop it from future digests. Schedule it daily and the digest becomes your morning commitments briefing — no phone number needed: connect once through the AgentPMT Telegram bot, and if you haven't yet, the run summary walks you through it. A processed-recordings tab guarantees each recording is scanned exactly once. Content type: workflow Source URL: https://www.agentpmt.com/agent-workflow-skills/plaud-spoken-commitments-to-sms-reminders Markdown URL: https://www.agentpmt.com/api/agent/workflows/plaud-spoken-commitments-to-sms-reminders?format=agent-md Updated: 2026-07-22T14:01:25.974Z Author: firef1ie --- Estimated time saved: 15 minutes. ## Tools - Get Users Current Time / Date - Google Sheets - Plaud - Speech to Text With Speakers - Telegram Instant Messenger ## Workflow Outline 1. Get Current Time: Fetch the user's current date, time, and timezone. Output them for resolving spoken relative dates ('Thursday', 'tomorrow', 'the 15th') and for flagging overdue commitments in the... 2. Find or Create Commitments Sheet: Locate the commitments spreadsheet. Run action 'search' with query 'Plaud Commitments'. If a spreadsheet named exactly 'Plaud Commitments' exists, use its spreadsheet_id; otherwis... 3. List Plaud Recordings: List ALL of the user's Plaud recordings with action 'list_files' and page_size 100 (page_size must be at least 10), paginating through every page until no results remain. For each... 4. Find New Recordings: Goal: Determine which Plaud recordings have not yet been scanned for commitments. | Inputs: The full recording list from List Plaud Recordings and the processed-id set from Find or Create Commitments Sheet. | Outputs: A... 5. For Each New Recording: Repeat this section for each recording. For each new recording: fetch it, obtain its transcript, extract every spoken commitment that carries a date or time, and log the commitmen... 6. Get Plaud File: Call action 'get_file' with file_id copied EXACTLY from the current recording's 'id' in the List Plaud Recordings output. A '500 Internal Server Error' almost always means the fil... 7. Read Open Commitments: This step runs on EVERY run, even when no new recordings were found. Read the full 'Commitments' tab with action 'read', range A2:E. Collect every row whose Status is 'open'. Outp... 8. Get Transcript (Plaud or STT): Obtain a transcript, preferring Plaud's own. IF has_plaud_transcript is true: do NOT call this tool — output {used_plaud_transcript: true} and reuse the utterances from Get Plaud... 9. Send Telegram Digest: If there are no open commitments, send nothing and output {sent: false, reason: 'nothing open'}. Otherwise send ONE Telegram message with action 'send_message' containing the full... 10. Extract Dated Commitments: Goal: Find every spoken commitment that carries a date or time and resolve it to a concrete datetime. | Inputs: The transcript utterances (Plaud times in MILLISECONDS, Speech-to-Text in SECONDS) and/or Plaud's summary m... 11. Summarize Run: Goal: Report the results of the commitments scan and digest delivery. | Inputs: Per-recording outcomes (commitments found, skips, fetch failures), the open-commitments list, and the digest delivery result (sent, nothing... 12. Log Commitments & Mark Processed: Two writes to the commitments spreadsheet (spreadsheet_id from Find or Create Commitments Sheet). FIRST, when commitments were extracted, run action 'append_rows' on tab 'Commitme... ## 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 6a604406b640fe17224aae76 ("Plaud Spoken Commitments to Telegram Reminders").