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

# Sort Bluedot meetings into collections

> File Bluedot recordings into the right collection by attendee or topic, and backfill the old ones that title-keyword auto-sorting never touches.

Source: https://cotlet.dev/integrations/bluedot-api-mcp-server/sort-meetings-into-collections

Bluedot files new recordings by a keyword in the title, so a call named "Catch up" lands nowhere, and every recording from before the rules sits in one pile.

Cotlet does it in your own Bluedot account with list\_collections, list\_meetings, get\_meeting and move\_meeting\_to\_collection, 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 sorts new recordings by a keyword in the meeting title (checked 20 Oct 2026). It does not read attendees or the notes, and it does not touch recordings that already exist. The official MCP server lists collections and meetings but has no tool that moves a recording.

## How you do it in Bluedot today

1. An admin opens Workspace settings > Auto-sorting, turns on Enforce auto-sorting rules workspace-wide and adds one rule per collection: a Keyword, a Match title option such as Contains keyword, and a Save to collection.
2. Rules are checked top to bottom, so specific keywords go above broad ones, otherwise a broad Sales catches your Sales demo meetings first.
3. A recording whose title has none of the keywords stays unsorted, and so do recordings of members who have no access to the chosen collection.
4. Older recordings are moved one by one: the Move icon on the meeting, the three-dot menu next to it, or a drag onto a collection in the sidebar.
5. To gather every call with one customer, a member opens a collection, clicks Filters, picks the attendee email and moves the matches by hand.

## How to sort Bluedot meetings into collections

Prompt

```
Find my unsorted Bluedot recordings from the last 2 weeks. File calls with customers into Customer calls and demos into Sales demos. Leave anything unclear for me.
```

1. 01  
### Read the folder tree  
list\_collections returns every collection and sub-collection with your access level. The agent files only into collections where your access is Full access or Can upload, and skips Can view and No access.
2. 02  
### Find the unsorted ones  
list\_meetings runs with a since date and follows next\_cursor to the end. A meeting row with collection\_id null is unsorted. Private recordings of other members never appear in the list, so the agent cannot file them.
3. 03  
### Judge on more than the title  
get\_meeting brings the summary and the attendees. The agent matches them against the rule in your prompt, for example "an attendee outside the company domain means a customer call", and quotes the line it used.
4. 04  
### Move, one meeting at a time  
move\_meeting\_to\_collection runs per recording. A collection with Send notes to Slack on posts the notes to its channel, and a collection shared with the workspace shows the recording to its members, so each move waits for your OK by default.
5. 05  
### Leave the unclear ones  
A call with no clear customer or topic stays where it is and goes on your list with the reason, instead of landing in a shared collection by guess.

### What you get back

Example data

```
Unsorted recordings from the last 2 weeks: 14
Moved 11, e.g. "Catch up" with Priya Nair to Customer calls
Left unsorted 3: no clear customer or topic
Collections used: Customer calls 7, Sales demos 4
```

### Other ways to ask

- Every Friday, file this week's recordings with an attendee from acme.io into the Acme collection.
- List my unsorted recordings with the collection you would pick for each, and move nothing.
- Move every recording from before September into Archive, and keep sub-collections as they are.

## What Bluedot allows, and what to know first

- Bluedot sub-collections always take the access level of their parent; the help center says there is currently no way to set different permissions for a sub-collection.
- Deleting a Bluedot collection permanently deletes every recording inside it, so this job moves recordings and never deletes a collection.
- Private recordings are visible only to their owner, and Owners and Admins get no default access to them, so the account can sort only what it can open.
- Slack caps messages at 3,000 characters, so a long summary filed into a collection that sends notes to Slack may not sync to the channel.
- Workspace-wide auto-sorting pauses members' personal rules, which show as Personal (Inactive) in their settings and resume when enforcement is turned off.

move\_meeting\_to\_collection asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Bluedot Help: Collections overview](https://help.bluedothq.com/en/articles/11414091-collections-overview) · [Bluedot Help: Set workspace-wide auto-sorting rules](https://help.bluedothq.com/en/articles/16972213-set-workspace-wide-auto-sorting-rules) · [Bluedot Help: Roles and permissions overview](https://help.bluedothq.com/en/articles/11036180-roles-and-permissions-overview) · [Bluedot Help: How to connect Bluedot to Slack](https://help.bluedothq.com/en/articles/11383869-how-to-connect-bluedot-to-slack) · [Bluedot Help: How to filter your collections](https://help.bluedothq.com/en/articles/12867859-how-to-filter-your-collections)

## Call move\_meeting\_to\_collection from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/bluedot/collections/c_5d90e7a2/meetings/m_8f3a21c4/to-collection/move \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"meeting_id": "m_8f3a21c4",
"title": "Catch up",
"collection_id": "c_5d90e7a2",
"collection_title": "Customer calls",
"moved": true
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is bluedot\_write → move\_meeting\_to\_collection. 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 sort Bluedot meetings into collections__
| Tool | Parameters |
| ----------------------------- | ---------------------------------------------------------------------------------------------- |
| list\_collections | workspace\_id, parent\_collection\_id |
| list\_meetings | workspace\_id, collection\_id, since, until, uploader\_email, participant\_email, sort, cursor |
| get\_meeting | meeting\_id, include |
| move\_meeting\_to\_collection | meeting\_id, collection\_id |

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

## Frequently asked questions

### Does this replace Bluedot auto-sorting?

No. Keep the title-keyword rules for new recordings, which cost nothing to run. The agent handles what the rules miss: calls with vague titles and every recording from before the rules existed.

### 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

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