[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Apply a Bluedot notes template to past meetings

> Re-run old Bluedot recordings through a new notes template in one pass instead of opening each recording's notes view and assigning it by hand.

Source: https://cotlet.dev/integrations/bluedot-api-mcp-server/apply-notes-template-to-past-meetings

You write a better template for sales calls in Workspace Settings > Templates, and every call recorded before today keeps the old notes.

Cotlet does it in your own Bluedot account with list\_templates, list\_meetings, apply\_template\_to\_meeting and get\_meeting, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=bluedot) [All Bluedot tools](https://cotlet.dev/integrations/bluedot-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Bluedot do this on its own?

Bluedot applies a template to one recording from its notes view, and enforces one on new meetings in a collection (checked 20 Oct 2026). It has no action for a batch of existing recordings, and its MCP server and webhooks cannot change notes.

## How you do it in Bluedot today

1. On the Pro plan or higher, an admin opens Workspace Settings > Templates, clicks Add Template, names it, picks Claude 4.6 Sonnet or GPT-5 and writes a prompt or a list of questions.
2. Each template is Private to its author or Shared with the workspace; members choose their own default on the My Settings page.
3. In a collection, ••• (Settings) next to Share has Enforce notes template and Default notes template, so every new meeting there uses one template.
4. That setting reaches new meetings only: Bluedot says existing notes are not regenerated to match it.
5. For an older recording, a member opens its notes view, assigns the template there and waits for the new notes, one recording at a time.

## How to apply a Bluedot notes template to past meetings

Prompt

```
Apply the Sales call template to last month's recordings in Customer calls. Do one first and show me the notes before you do the rest.
```

1. 01  
### Find the template  
list\_templates returns the templates you can see in Workspace Settings > Templates, with visibility and creator. The agent picks the one you named and stops if it is not in the list, for example on a plan without custom templates.
2. 02  
### Count the recordings  
list\_meetings runs with the collection and the date range from your prompt and follows next\_cursor. The agent reports how many recordings it would change before it touches any.
3. 03  
### Try one first  
apply\_template\_to\_meeting runs on a single recording, then get\_meeting reads the new summary. The agent shows you that result and waits, because a template that reads well on paper can give odd notes on a real call.
4. 04  
### Apply to the rest  
After your go-ahead the tool runs per recording. A recording you can only view returns APP\_PERMISSION\_DENIED and is listed as failed instead of retried. Notes are visible to everyone the recording is shared with, so each call waits for your OK by default.
5. 05  
### Report the outcome  
The agent lists applied, failed and skipped recordings with their links, so you can open any of them in Bluedot.

### What you get back

Example data

```
Template: Sales call (Shared, Claude 4.6 Sonnet)
Checked first: "Pricing review" now follows the template
Applied to 9 of 10 recordings from last month
Failed 1: APP_PERMISSION_DENIED (view only)
```

### Other ways to ask

- Apply the Customer interview template to every recording in Research from this quarter.
- List which recordings in Customer calls still use another template than Sales call, and change nothing.
- Create a Weekly sync template with a checklist of follow-up tasks, then apply it to this month's syncs.

## What Bluedot allows, and what to know first

- Custom note templates start on the Bluedot Pro plan; Basic has none, so the template list can be short or empty on a lower plan.
- A template prompt can ask for a table or a checklist, and each checklist item can be checked off directly in the notes.
- Bluedot offers Claude 4.6 Sonnet and GPT-5 as the AI model of a template, chosen when the template is written.
- Setting a default or enforced template for a collection needs editing permission on that collection.
- A Shared template is visible to everyone in the workspace, and each teammate's list shows who created it.

apply\_template\_to\_meeting asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.

Sources: [Bluedot Help: How to create custom note templates](https://help.bluedothq.com/en/articles/11393395-how-to-create-custom-note-templates) · [Bluedot Help: How to set a default notes template for a collection](https://help.bluedothq.com/en/articles/17249145-how-to-set-a-default-notes-template-for-a-collection) · [Bluedot Help: Collections overview](https://help.bluedothq.com/en/articles/11414091-collections-overview) · [Bluedot: Pricing](https://www.bluedothq.com/pricing)

## Call apply\_template\_to\_meeting from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/bluedot/meetings/m_2b6d94e0/templates/t_41c7a9f3/to-meeting/apply \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"meeting_id": "m_2b6d94e0",
"title": "Pricing review",
"template_id": "t_41c7a9f3",
"template_name": "Sales call",
"status": "applied"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is bluedot\_write → apply\_template\_to\_meeting. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/bluedot-api-mcp-server.md#automations)

## Bluedot tools this automation uses

__Cotlet Bluedot tools used to apply a Bluedot notes template to past meetings__
| Tool | Parameters |
| ---------------------------- | ---------------------------------------------------------------------------------------------- |
| list\_templates | workspace\_id |
| list\_meetings | workspace\_id, collection\_id, since, until, uploader\_email, participant\_email, sort, cursor |
| apply\_template\_to\_meeting | meeting\_id, template\_id |
| get\_meeting | meeting\_id, include |

[All 14 Bluedot tools with descriptions](https://cotlet.dev/integrations/bluedot-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Bluedot to Cotlet?

Yes. You sign in to Bluedot yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Bluedot once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Bluedot automations

- [Sort Bluedot meetings into collections](https://cotlet.dev/integrations/bluedot-api-mcp-server/sort-meetings-into-collections.md)
- [Comment on action items in Bluedot transcripts](https://cotlet.dev/integrations/bluedot-api-mcp-server/comment-on-meeting-action-items.md)
- [Bluedot API and MCP server: every tool](https://cotlet.dev/integrations/bluedot-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Bluedot.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Bluedot.

[Sign up free](https://cotlet.dev/app/signup?app=bluedot)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.