# Plaud Call Logger for Pipedrive > Turns your Plaud voice recordings of client calls into Pipedrive records automatically. Reviews every new recording, identifies genuine client conversations, transcribes them (reusing the recording's own transcript when one exists), saves the transcript to a "Plaud Call Logs" Drive folder, matches the spoken client name and company to a Pipedrive person and open deal, attaches a call note with the discussion summary, commitments, next steps, and transcript link, and creates a follow-up activity dated from spoken commitments. Keeps a Google Sheet ledger so every recording is processed exactly once; recordings that are not client calls are logged and skipped. Re-runnable and idempotent. Content type: workflow Source URL: https://www.agentpmt.com/agent-workflow-skills/plaud-call-logger-for-pipedrive Markdown URL: https://www.agentpmt.com/api/agent/workflows/plaud-call-logger-for-pipedrive?format=agent-md Updated: 2026-07-22T04:22:05.790Z Author: firef1ie --- Estimated time saved: 30 minutes. ## Tools - Google Sheets - Google Drive - Plaud - Speech to Text With Speakers - Pipedrive ## Workflow Outline 1. Find or Create Call Log: Locate the call-log spreadsheet. Run action 'search' with query 'Plaud Pipedrive Call Log'. If a spreadsheet named exactly 'Plaud Pipedrive Call Log' exists, use its spreadsheet_i... 2. Ensure Transcript Folder: Run action 'ensure_folder_path' with ensure_path 'Plaud Call Logs' to create the folder at My Drive root if it does not already exist. Output the folder_id for the transcript uplo... 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 processed by this workflow. | Inputs: The full list of Plaud recordings from the List Plaud Recordings step, and the set of already-logged Recording IDs from the... 5. For Each New Recording: Repeat this section for each recording. For each new recording: fetch it, obtain a transcript, decide whether it is a client call, and when it is, save the transcript, log a note... 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. Summarize Run: Goal: Report the results of the call-logging run. | Inputs: Per-recording outcomes: client call or not, CRM match or not, note and activity ids, transcript links, skips and fetch failures. | Outputs: A short summary: ho... 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. Classify & Distill Call: Goal: Decide whether this recording is a client call and, if so, distill what the CRM needs. | Inputs: The recording name, start_at, transcript utterances (Plaud in milliseconds or Speech-to-Text in seconds) and/or Plau... 10. Save Transcript to Drive: Only for client calls that have a transcript (transcript_source 'plaud' or 'speech-to-text'); otherwise output {skipped: true}. Save the transcript JSON into the 'Plaud Call Logs'... 11. Match Pipedrive Person & Deal: Only when is_client_call is true; otherwise output {matched: false, reason: 'not a client call'}. Search Pipedrive for the client: use the person search action with client_name (a... 12. Attach Call Note: Only when matched is true; otherwise output {skipped: true}. Create a Pipedrive note attached to the matched person (and to the deal when deal_id exists). Note content (formatted,... 13. Create Follow-Up Activity: Only when matched is true; otherwise output {skipped: true}. Create a follow-up activity linked to the matched person (and deal when present): type 'call' (fall back to 'task' if... 14. Write Log Row: Append exactly one row to the call log (spreadsheet_id and sheet_name from the Find or Create Call Log step) with action 'append_rows', object row keyed by headers: {'Recording ID... ## 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 6a6042b8b640fe17224aae6e ("Plaud Call Logger for Pipedrive").