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

# Assign Krisp action items an owner and due date

> Read what was said in each Krisp meeting, then set the action item owner and due date it names, and list what still has no owner.

Source: https://cotlet.dev/integrations/krisp-api-mcp-server/assign-action-items-due-dates

Krisp lists every task from your calls, but half of them have no owner and no date, so on Monday nobody knows what is theirs.

Cotlet does it in your own Krisp account with list\_action\_items, get\_meeting and update\_action\_item, 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 lists action items and marks them done or open again, one at a time or up to 50 in a call, but it has no tool to set a due date, priority or assignee (checked 22 Oct 2026). Krisp assigns items automatically only when it can match a participant.

## How you do it in Krisp today

1. Open the Action Items page in the account dashboard. The Assigned to Me view lets you prioritize tasks, mark them completed, set due dates and assign them to team members.
2. Switch to All Action Items to see tasks from all meetings and all team members, with the same options.
3. Or open a meeting's notes after Summarize and edit its action items there, adding a Due date, Priority and Assignee.
4. Krisp assigns items to participants on its own when your calendar is connected or the speakers are assigned in the transcript. Everything else stays unassigned.
5. Items you add in the Personal section are visible only to you.

## How to assign Krisp action items an owner and due date

Prompt

```
List open Krisp action items with no assignee or no due date. Read the source meeting, and where someone said who and by when, set the assignee and due date. Leave the rest for me.
```

1. 01  
### Pull the open items  
list\_action\_items runs with view all and status open. Each item comes back with its ID, assignee, due date and source meeting, and the agent keeps the items missing an assignee or a due date.
2. 02  
### Read where it was said  
For each source meeting, get\_meeting returns the action items with the summary and key points, and the transcript when the summary is not enough. The agent looks for a name and a date said about that task, such as "Dana sends the quote by Friday".
3. 03  
### Set only what was said  
update\_action\_item sets due\_date, assignee\_email or priority where the meeting names one. A date or owner the meeting never mentioned is not guessed: the item goes on your list with the line that made it unclear.
4. 04  
### Ask before you notify  
An assignment shows up in the assignee's Activity Center, so each update waits for your OK until you switch confirmation off for update\_action\_item.
5. 05  
### Report what is still open  
The agent returns the updated items, then those still without an owner or a date, grouped by meeting.

### What you get back

Example data

```
Open items without owner or date: 11
Updated 7 (e.g. "Send revised quote" to Dana, due 2026-10-30)
Owner set, no date said 2
Nothing said about it 2: "Look into pricing page", "Book the venue"
Assignment notifications sent: 5
```

### Other ways to ask

- Every Monday, list my action items that are overdue and group them by meeting.
- Set the due date on every open item from the product sync to the Friday after the meeting.
- Show items assigned to nobody from the last two weeks, but change nothing.

## What Krisp allows, and what to know first

- Krisp has an Assigned to Me view and an All Action Items view, and the Personal section holds items visible only to you.
- Krisp lets you edit an action item's Due date, Priority and Assignee in the meeting notes.
- If you delete the Action Items section from a meeting's notes, you have to summarize the meeting again and all manual edits are erased.
- Each Krisp action item has its own ID, and titles are not unique, so an update goes by ID.
- Krisp lists action item assignments in the Activity Center of the person they are assigned to.

update\_action\_item asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Krisp Help: Centralized Action Items in account dashboard](https://help.krisp.ai/hc/en-us/articles/18809437531420-Centralized-Action-Items-in-account-dashboard) · [Krisp Help: Meetings page in account dashboard](https://help.krisp.ai/hc/en-us/articles/10291109632412-Meetings-page-in-account-dashboard) · [Krisp Help: Krisp MCP supported tools](https://help.krisp.ai/hc/en-us/articles/25416265429660-Krisp-MCP-Supported-tools)

## Call update\_action\_item from a script

curl

```
curl -X PATCH https://cotlet.dev/api/v1/krisp/action-items/91919191919191919191919191919191 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"due_date":"2026-10-30","assignee_email":"dana@yourteam-example.com"}'
```

Example response

```
{
"action_item_id": "91919191919191919191919191919191",
"text": "Send revised quote",
"assignee": "Dana Whitfield",
"due_date": "2026-10-30",
"completed": false
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is krisp\_write → update\_action\_item. 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 assign Krisp action items an owner and due date__
| Tool | Parameters |
| -------------------- | ----------------------------------------------------------------- |
| list\_action\_items | view, status, meeting\_id |
| get\_meeting | meeting\_id, include |
| update\_action\_item | action\_item\_id, due\_date, priority, assignee\_email, completed |

[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)
- [Organize Krisp meetings into folders and tags automatically](https://cotlet.dev/integrations/krisp-api-mcp-server/organize-meetings-into-folders.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.