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

# Share tl;dv recordings automatically

> Share each tl;dv recording with the right people by your own rule, as viewer or editor, and spot public links. Runs daily from your agent.

Source: https://cotlet.dev/integrations/tldv-api-mcp-server/share-recordings-automatically

Every call ends up in your tl;dv library, and someone has to open each one, click share and type the same teammates' emails before anyone else can watch it.

Cotlet does it in your own tl;dv account with list\_meetings, get\_meeting, share\_meeting and set\_link\_access, 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 shares with participants in your organization by default, and Pro users can change that default and set Default recording privacy rules in Preferences (checked 17 Oct 2026). Those are fixed settings. The API and the official MCP server have no share action, and the API docs state that sharing a meeting does not grant API export rights.

## How you do it in tl;dv today

1. tl;dv shares a recording by email with the meeting participants who belong to your organization, and only Pro users can change that default in Preferences.
2. For anyone else, an admin or editor of the meeting opens it and clicks share above the video.
3. In the sharing window they pick the overall access level, Anyone with the link or People with access, then type an email address or a domain such as \*@company.com in the invitation field.
4. A dropdown next to each person or domain sets Admin, Editor or Viewer, and each person added gets an email.
5. The link is copied from the same window, and a toggle decides whether the meeting notes travel with it.
6. Calls pile up every day, so a call nobody shares stays in one library, and a link once made public stays public until someone looks.

## How to share tl;dv recordings automatically

Prompt

```
List today's tl;dv recordings. Share customer calls with everyone at acme.io as viewers, share internal syncs only with their attendees, and tell me which meetings still have a public link.
```

1. 01  
### Collect the day's recordings  
Your agent lists the meetings from the day you name and skips any that tl;dv still processes, so a half-ready recording is picked up on the next run instead of shared too early.
2. 02  
### Read who can open each one  
get\_meeting shows the current access list and the link level, and your role on the meeting. A meeting where you are only a Viewer cannot be changed, so it goes on a list for you.
3. 03  
### Apply your rule  
The agent sorts calls by title and participant domain: a customer call goes to the domain you named, an internal sync goes only to its attendees, anything that fits neither stays untouched.
4. 04  
### Share and report public links  
share\_meeting adds each address at the level you set; every added person gets an email, so each call waits for your OK by default. A public link is only reported, and closed with set\_link\_access when your prompt says so.

### What you get back

Example data

```
Recordings today: 5
Shared with everyone at acme.io as viewers: 3 customer calls
Shared with its 4 attendees: Q4 planning
Skipped, still processing: 1
Public link still on: Q4 planning (I did not change it)
```

### Other ways to ask

- Every Friday, share the week's recordings tagged as demos with the sales team as editors, so they can add notes.
- Share a recording only with the people who attended, and list every call with a public link.
- Close the public link on every customer call and tell me which ones had one.

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

- Only someone with admin or editor access to a meeting can change who sees it, so the account behind this job needs that role on every recording it touches.
- tl;dv offers three access levels per person or domain, Admin, Editor and Viewer, and removing someone does not notify them, while adding them does.
- Anyone with the link can watch a public tl;dv recording without signing in, and tl;dv says it is not indexed by search engines.
- tl;dv's default auto-share by email reaches only meeting participants who belong to your organization, so external attendees get nothing unless someone shares it.

share\_meeting and set\_link\_access ask for your OK by default. To run it daily without you, switch confirmation off for those tools in your dashboard.

Sources: [tl;dv Help: How to share meeting recordings](https://intercom.help/tldv/en/articles/5946340-how-to-share-meeting-recordings) · [tl;dv Help: How to auto-share recordings with meeting invitees](https://intercom.help/tldv/en/articles/8490523-how-to-auto-share-recordings-with-meeting-invitees) · [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 share\_meeting from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/tldv/meetings/mt_4f21a9/share \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"share_with":["dana@acme.io","sam@acme.io"],"access":"viewer"}'
```

Example response

```
{
"meeting_id": "mt_4f21a9",
"shared_with": [
{
"who": "dana@acme.io",
"access": "viewer"
},
{
"who": "sam@acme.io",
"access": "viewer"
}
],
"notified": 2
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is tldv\_write → share\_meeting. 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 share tl;dv recordings automatically__
| Tool | Parameters |
| ----------------- | ------------------------------------------ |
| list\_meetings | query, from, to, folder\_id, limit, cursor |
| get\_meeting | meeting\_id |
| share\_meeting | meeting\_id, share\_with, access |
| set\_link\_access | meeting\_id, link\_access |

[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

- [Turn tl;dv key moments into clips and notes](https://cotlet.dev/integrations/tldv-api-mcp-server/clip-key-moments.md)
- [Rename tl;dv meetings and file them in folders](https://cotlet.dev/integrations/tldv-api-mcp-server/organize-meetings-in-folders.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.