Bluedot logo Bluedot automation · runs daily

Comment on action items in Bluedot transcripts

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 All Bluedot tools

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 · Bluedot Help: Bluedot MCP overview · Bluedot Help: AI Chat overview · Bluedot Help: 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

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

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.

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