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

# Rename tl;dv meetings and file them in folders

> Give generic tl;dv titles a real name and file each call in the right folder, without the one-meeting-at-a-time clicking. Runs weekly.

Source: https://cotlet.dev/integrations/tldv-api-mcp-server/organize-meetings-in-folders

Calendar invites give recordings names like "Quick sync" or "Call with Dana", and finding last month's Acme call means opening five of them.

Cotlet does it in your own tl;dv account with list\_meetings, get\_meeting, list\_folders, rename\_meeting and add\_to\_folder, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can tl;dv do this on its own?

tl;dv has folders and renaming in the app, and no bulk add (checked 17 Oct 2026). The API and the official MCP server list and read meetings only: neither renames a meeting nor files it in a folder.

## How you do it in tl;dv today

1. In the Meetings & Folders tab, you select Folders at the top and click New folder at the top right; the new folder starts private.
2. A meeting goes into a folder one at a time: open it and click Add to a folder, because tl;dv cannot add meetings in bulk yet.
3. Only a meeting's Editor or Admin can add it to a folder or remove it; Viewers cannot.
4. To fix a title, open the recording from your library and rename it, which tl;dv describes as a way to find the meeting later.
5. A backlog of untitled recordings turns into dozens of open, click and pick rounds, so it is left until someone needs a call and cannot find it.

## How to rename tl;dv meetings and file them in folders

Prompt

```
Find tl;dv meetings from the last 7 days with a generic title like "Quick sync". Rename each one from its participants and topic, then file customer calls in the folder named after the customer.
```

1. 01  
### Spot the generic titles  
The agent lists the last 7 days and flags titles that match a pattern like "Quick sync", "Call with" or a bare calendar subject, and skips anything you already renamed.
2. 02  
### Work out the name  
get\_meeting gives the participants and their email domains. A name is built as "Customer, topic, date", and the agent leaves the title alone when it cannot tell the customer from the participants.
3. 03  
### Match a folder  
list\_folders shows which folders exist, who can open them and whether each is a new or a previous version folder. Previous version folders are skipped because tl;dv no longer edits them.
4. 04  
### Rename, then file  
rename\_meeting runs without asking, since one call undoes it. add\_to\_folder asks for your OK by default, because a shared folder shows the meeting to everyone who can open the folder.
5. 05  
### Report what it left  
Meetings where your role is Viewer, or where no folder fits, come back as a list, so a person decides only on those.

### What you get back

Example data

```
Meetings checked: 14
Renamed: 9, e.g. "Quick sync" is now "Acme, onboarding plan, 14 Oct"
Filed in "Acme": 4, "Northwind": 3
Left for you 2:
- "Call with Dana" (no matching folder)
- "Weekly" (you are Viewer)
```

### Other ways to ask

- Every Monday, rename and file last week's calls, and only list the ones you could not place.
- List the folders shared with the whole organization and tell me which of my meetings sit in them.
- Rename only, no folders, and show me the old and new title for each meeting.

## What tl;dv allows, and what to know first

- New tl;dv folders are private when created, and a folder can then be shared with individual users, Teams or entire organizations.
- Anyone with access to a folder can at least view every meeting in it, and the highest access level prevails, so filing a meeting in a shared folder can widen who sees it.
- Folders from the older version cannot be edited or shared with new users; a Folder Admin moves them with Update folder to new version.
- tl;dv adds meetings to a folder one at a time, and says bulk add is coming.

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

Sources: [tl;dv Help: How to use Folders](https://intercom.help/tldv/en/articles/11458852-how-to-use-folders) · [tl;dv Help: How to manage recordings in your tl;dv library](https://intercom.help/tldv/en/articles/5946324-how-to-manage-recordings-in-your-tl-dv-library) · [tl;dv Public API docs (v1alpha1)](https://doc.tldv.io) · [tl;dv MCP server (official repository)](https://github.com/tldv-public/tldv-mcp-server)

## Call add\_to\_folder from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/tldv/meetings/mt_4f21a9/folders/fo_31c2 \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"meeting_id": "mt_4f21a9",
"folder_id": "fo_31c2",
"folder": "Acme",
"status": "added"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is tldv\_write → add\_to\_folder. Example data.

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

## tl;dv tools this automation uses

__Cotlet tl;dv tools used to rename tl;dv meetings and file them in folders__
| Tool | Parameters |
| --------------- | ------------------------------------------ |
| list\_meetings | query, from, to, folder\_id, limit, cursor |
| get\_meeting | meeting\_id |
| list\_folders | none |
| rename\_meeting | meeting\_id, title |
| add\_to\_folder | meeting\_id, folder\_id |

[All 13 tl;dv tools with descriptions](https://cotlet.dev/integrations/tldv-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect tl;dv to Cotlet?

Yes. You sign in to tl;dv yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get tl;dv 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 tl;dv automations

- [Share tl;dv recordings automatically](https://cotlet.dev/integrations/tldv-api-mcp-server/share-recordings-automatically.md)
- [Turn tl;dv key moments into clips and notes](https://cotlet.dev/integrations/tldv-api-mcp-server/clip-key-moments.md)
- [tl;dv API and MCP server: every tool](https://cotlet.dev/integrations/tldv-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to tl;dv.

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

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

---

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.