[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)

# Comment on action items in Bluedot transcripts

> Leave a timestamped Bluedot comment on each promise made in a call and @mention the owner, so follow-ups sit on the transcript line they come from.

Source: https://cotlet.dev/integrations/bluedot-api-mcp-server/comment-on-meeting-action-items

A customer call ends with three promises, and the teammate who owns one never opens the transcript to find it.

Cotlet does it in your own Bluedot account with list\_meetings, get\_meeting, list\_comments and add\_comment, 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 has comments in the app but no way to write one from code (checked 20 Oct 2026). The official MCP server only reads, webhooks only send a finished recording out, and the AI Chat tab answers questions about recordings without posting to the transcript.

## How you do it in Bluedot today

1. A member opens the recording's transcript, highlights the text, clicks Comment in the toolbar, types the comment and clicks Post.
2. Typing @ followed by a name mentions a teammate, who is notified and can reply in the comment thread.
3. Bluedot time-stamps every comment to that moment, and a click on the timestamp jumps the recording to it.
4. A posted comment cannot be edited: the author deletes it and writes a new one.
5. Without comments, follow-ups live in the AI notes, for example as a checklist of tasks from a template, which stays inside the notes and tells nobody.

## How to comment on action items in Bluedot transcripts

Prompt

```
Read yesterday's customer calls. For every promise someone made, comment on that line of the transcript and mention the person who owns it.
```

1. 01  
### Take yesterday's calls  
list\_meetings runs with a since date and your collection, so only recordings you can open are read. Private recordings of other members are not in the list.
2. 02  
### Find the promises  
get\_meeting returns the transcript with speaker labels and timestamps. The agent looks for sentences where a speaker commits to something ("I will send the quote by Friday") and notes the speaker as the owner.
3. 03  
### Skip lines already commented  
list\_comments shows what is already on the recording. A line that has a comment is skipped, because a posted comment cannot be edited and a second one would only add noise.
4. 04  
### Comment on the exact line  
add\_comment takes the quoted transcript text, so the comment attaches to that line and carries its timestamp. When the owner is a teammate, the text starts with their @name, which notifies them, so each comment waits for your OK by default.
5. 05  
### Hand back one list  
The agent returns the promises per call with owner and timestamp. Lines where the owner is unclear stay uncommented and go on your list.

### What you get back

Example data

```
Customer calls from yesterday: 3
Comments added 5, e.g. 00:24:10 "I will send the quote by Friday" for Dana Whitfield
Skipped 2: already commented
No clear owner 1: "someone should check the contract"
```

### Other ways to ask

- Only comment on promises with a date in them, and list the rest in this chat.
- Every Monday, comment on open questions from last week's product syncs and mention the product lead.
- Show me the promises from yesterday's calls as a list and post nothing.

## What Bluedot allows, and what to know first

- A Bluedot comment cannot be edited once posted; deleting it and writing a new one is the only fix.
- A mentioned teammate is notified and can reply in the comment thread.
- Every Bluedot comment is time-stamped to the highlighted moment, so a reader jumps straight to it.
- Bluedot shows transcripts with speaker labels and timestamps, which is what lets the agent name the owner of a promise.
- Private recordings are visible only to their owner, so the account can comment only on recordings it can open.

add\_comment asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Bluedot Help: How to add comments to a recording](https://help.bluedothq.com/en/articles/11532672-how-to-add-comments-to-a-recording) · [Bluedot Help: Bluedot MCP overview](https://help.bluedothq.com/en/articles/14708332-bluedot-mcp-overview) · [Bluedot Help: AI Chat overview](https://help.bluedothq.com/en/articles/11468929-ai-chat-overview) · [Bluedot Help: Roles and permissions overview](https://help.bluedothq.com/en/articles/11036180-roles-and-permissions-overview)

## Call add\_comment from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/bluedot/meetings/m_6e0f13b8/comments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"quoted_text":"I will send the quote by Friday","text":"@Dana Whitfield owns this: send the quote by Friday."}'
```

Example response

```
{
"comment_id": "k_9c31",
"meeting_id": "m_6e0f13b8",
"at": "00:24:10",
"quoted_text": "I will send the quote by Friday",
"text": "@Dana Whitfield owns this: send the quote by Friday.",
"mentions": [
"Dana Whitfield"
],
"created_at": "2026-10-16T08:05:00Z"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is bluedot\_write → add\_comment. 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 comment on action items in Bluedot transcripts__
| Tool | Parameters |
| -------------- | ---------------------------------------------------------------------------------------------- |
| list\_meetings | workspace\_id, collection\_id, since, until, uploader\_email, participant\_email, sort, cursor |
| get\_meeting | meeting\_id, include |
| list\_comments | meeting\_id |
| add\_comment | meeting\_id, quoted\_text, text |

[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)
- [Apply a Bluedot notes template to past meetings](https://cotlet.dev/integrations/bluedot-api-mcp-server/apply-notes-template-to-past-meetings.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.