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

# Organize Krisp meetings into folders and tags automatically

> File each week's Krisp meetings into the right folder and tag them by your rule, so calls with one client or project sit in one place.

Source: https://cotlet.dev/integrations/krisp-api-mcp-server/organize-meetings-into-folders

By Friday My Notes holds 20 meetings with auto-generated titles, and the client folders are empty because filing each call is one more click nobody makes.

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

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

Hosted · nothing to install or maintain

## Can Krisp do this on its own?

The official Krisp MCP can attach and remove tags, list folders and open a folder to see its meetings, but it has no tool to add a meeting to a folder (checked 22 Oct 2026). Krisp has no setting that files meetings by title, tag or participant.

## How you do it in Krisp today

1. Hover over a meeting in the Meetings list, click the tag icon, then add a new tag or select an existing one. Tags are shared across the team.
2. Create a folder with the New Folder button, or with the + button on the Private or Teamspace header, with a name, an optional description and an icon.
3. Add meetings from the folder page with Add meeting, by dragging a meeting onto a folder, from the folder action on a meeting, or by selecting several and clicking Add to folder in the bulk actions bar.
4. Filter by tag with the three-line icon at the top of the Meetings page.
5. Krisp has no rule that files a meeting by title or participants, so filing repeats after every call.

## How to organize Krisp meetings into folders and tags automatically

Prompt

```
Go through this week's Krisp meetings. Put each client call in the folder named after the client and tag it Client. Leave meetings that match no folder for me.
```

1. 01  
### Read the folders  
list\_folders returns each folder's name, space (private or teamspace), your role and meeting count. The agent matches your rule to existing folders only. When no folder fits, it stops for that meeting and asks, because no tool creates a folder.
2. 02  
### Collect this week's meetings  
list\_meetings runs with from set to the start of the week and follows next\_cursor. Meetings already in a folder are skipped, so a second run does not repeat work.
3. 03  
### Match meeting to folder  
get\_meeting reads the title and participants. A participant's email domain or a client name in the title picks the folder. Two matching folders mean the meeting is listed for you instead of filed.
4. 04  
### File it, with a warning for shared folders  
add\_meeting\_to\_folder works only for your own meetings. Folder members get access to the meetings inside, and Teamspace folders are visible to the whole team, so each call waits for your OK, and the agent says which folders are Teamspace.
5. 05  
### Tag in the same pass  
tag\_meeting adds one to three tags per meeting. A meeting with 7 tags is skipped, and a tag name that does not exist yet is created for your whole team, so the agent lists new names in its report.

### What you get back

Example data

```
Meetings this week: 12
Filed 9 (Acme: 4, Lumen: 3, Pixel: 2)
Tagged Client: 9
No matching folder 3: "Intro call, Jordan", "Vendor demo", "1 to 1"
New tags created: 0
```

### Other ways to ask

- File this month's 1 to 1 meetings into my Team 1 to 1 folder and tag them with the person's name.
- Tag every meeting from last week whose title has "retro" as Retro, and file nothing.
- List meetings that sit in no folder and propose a folder for each, without changing anything.

## What Krisp allows, and what to know first

- Krisp lets you add only your own meetings to a folder.
- Folders live in two spaces, Private and Teamspace. Teamspace folders are visible and accessible to all members of your team, with view access by default.
- All folder members get access to the meetings inside the folder as Viewers by default.
- A Krisp meeting holds at most 7 tags in total, and tags are shared at the team level.
- If someone is removed from a folder, the meetings they added stay accessible to the folder members.

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

Sources: [Krisp Help: Meeting folders](https://help.krisp.ai/hc/en-us/articles/29185808893340-Meeting-folders) · [Krisp Help: Meeting tags](https://help.krisp.ai/hc/en-us/articles/30047825023132-Meeting-tags) · [Krisp Help: Krisp MCP supported tools](https://help.krisp.ai/hc/en-us/articles/25416265429660-Krisp-MCP-Supported-tools)

## Call add\_meeting\_to\_folder from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/krisp/folders/21212121212121212121212121212121/meetings/7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c/to-folder \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"meeting_id": "7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c7c",
"folder_id": "21212121212121212121212121212121",
"folder": "Acme",
"space": "private",
"status": "added"
}
```

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

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

## Krisp tools this automation uses

__Cotlet Krisp tools used to organize Krisp meetings into folders and tags automatically__
| Tool | Parameters |
| ------------------------ | ---------------------------------------- |
| list\_folders | space |
| list\_meetings | query, from, to, tag, folder\_id, cursor |
| get\_meeting | meeting\_id, include |
| add\_meeting\_to\_folder | meeting\_id, folder\_id |
| tag\_meeting | meeting\_id, tags, remove |

[All 11 Krisp tools with descriptions](https://cotlet.dev/integrations/krisp-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Krisp to Cotlet?

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

- [Share Krisp meeting notes with attendees after each call](https://cotlet.dev/integrations/krisp-api-mcp-server/share-meeting-notes-after-calls.md)
- [Assign Krisp action items an owner and due date](https://cotlet.dev/integrations/krisp-api-mcp-server/assign-action-items-due-dates.md)
- [Krisp API and MCP server: every tool](https://cotlet.dev/integrations/krisp-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Krisp.

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

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

---

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.