# One Plaud Recording, Several Differently Formatted Summaries

> Gets you past the one-template-per-recording ceiling. The Plaud app applies a single AutoFlow template to a recording, so if you want a short recap for yourself, a decisions-only version for the people who missed it, and a clean action list for your task manager, you are re-running or rewriting by hand. This workflow reads the transcript once and produces every format you have defined in a single pass: you list the output formats you want in a Google Sheet, each with a name and a description of the shape and audience, and the workflow generates all of them from the same source text and writes them into one Google Doc per recording with a section for each. Because every version comes from the same read of the transcript, they stay consistent with each other rather than drifting the way separately generated summaries do. Formats are yours to change at any time by editing the sheet, with no re-recording and no template juggling in the app. A processed log keeps each recording to a single pass so it can run on a schedule over everything new.

Content type: workflow
Source URL: https://www.agentpmt.com/agent-workflow-skills/one-plaud-recording-several-differently-formatted-summaries
Markdown URL: https://www.agentpmt.com/api/agent/workflows/one-plaud-recording-several-differently-formatted-summaries?format=agent-md
Updated: 2026-07-26T00:01:46.081Z
Author: firef1ie

---

Estimated time saved: 20 minutes.

## Tools

- Get Users Current Time / Date
- Google Sheets
- Plaud
- Google Docs Connector

## Workflow Outline

1. Get User Timezone and Date: Get the user's current local date, time, timezone and UTC offset. The requested window and every recording timestamp are resolved against this and never against the server clock.
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. Read Output Formats: Read the formats tab: each row defines one output the user wants, with a name, the audience it is for, and a description of its shape and length. These rows are the whole configur...
4. List Plaud Recordings: Call list_files with the widened UTC date_from and date_to from the window step. Plaud's timestamps are inconsistent and must be handled deliberately: the name field carries the r...
5. Each New Recording: Repeat this section for each recording. Handle one recording at a time, generating every configured format from a single read of its transcript.
6. Fetch Transcript: Call get_transcript with this recording's file id, reusing Plaud's existing transcript when one exists.
7. Summarize the Run: Goal: Report what was produced this run. | Inputs: The per-recording results, and the window that was used. | Outputs: The window covered stated in local time, then each recording processed with its doc link and the for...
8. Generate Every Configured Format: Goal: Produce every output format the user has configured from one reading of this transcript. | Inputs: The full transcript for one recording, its local recorded date and time, and the list of configured formats with t...
9. Write the Multi-Format Doc: Create one document for this recording with a clearly headed section for each configured format, in the order the sheet lists them, and the recording's local date and time plus a...
10. Log the Run: Append the recording id, its local recorded time, the doc link, and which formats were produced to the processed log so the recording is not handled again.

## 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 <AGENTPMT_BEARER_TOKEN>",
        "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 6a653522b640fe17224ac76a ("One Plaud Recording, Several Differently Formatted Summaries").