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

# Create Nextcloud Deck cards from meeting notes

> Turn meeting notes into Nextcloud Deck cards with a description and due date, skipping tasks that already have a card.

Source: https://cotlet.dev/integrations/nextcloud-api-mcp-server/create-deck-cards-from-notes

After every meeting someone has to retype the action items from the notes into the Deck board, one card at a time, and half of them are already on the board from last week.

Cotlet does it in your own Nextcloud account with list\_deck\_boards, list\_deck\_cards and create\_deck\_card, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Nextcloud do this on its own?

Deck has a REST API that creates cards (checked 16 Oct 2026), but you build the requests, find the board and stack IDs, and avoid duplicates yourself. Deck imports from Trello through the API or the occ deck:import command, not from notes. Context Agent lists adding Deck cards among its tools, after an admin installs it.

## How you do it in Nextcloud today

1. Open the Deck app and pick the board for the team.
2. In the stack that stands for your To do column, add a card for each action item.
3. Click each card to open its details and fill them in: a description in markdown, a deadline, tags, and an assigned user who gets a notification.
4. Cards you no longer need are archived rather than deleted, and deleted stacks or cards can be restored from the board settings under Deleted objects.
5. Duplicates between this week and last week are found by eye, because the board has no check for repeated tasks.

## How to create Nextcloud Deck cards from meeting notes

Prompt

```
Read these meeting notes, find the action items and create a card for each in the Product board, in the To do stack, with the owner and due date in the description.
```

1. 01  
### Find the board and the stack  
The agent resolves the board name you gave through list\_deck\_boards, then reads its stacks to find the To do column, and reports an error if two stacks match instead of guessing.
2. 02  
### Extract the action items  
It reads your notes and keeps only sentences with an owner or a verb and an object, such as "Lena sends the pricing draft", and drops discussion and decisions.
3. 03  
### Compare with what is on the board  
list\_deck\_cards returns the cards already in the stacks, and the agent skips any item whose title is the same or nearly the same as an open card, listing it as already tracked.
4. 04  
### Create each card with the context  
create\_deck\_card writes a short title, and puts owner, due date and the sentence from the notes into the markdown description. Each card waits for your OK by default.
5. 05  
### Report what was created and what was left  
You get the new cards with their IDs, the items skipped as duplicates and the ones where no owner or date could be found.

### What you get back

Example data

```
Board: Product, stack: To do
Created 4 cards, for example:
- Send pricing draft to finance (due 2026-10-23, owner Lena)
- Book customer call with Acme (due 2026-10-21, owner Tom)
Skipped 2 already on the board: "Update changelog", "Fix export bug"
No owner found for 1 item: "Check the new onboarding copy"
```

### Other ways to ask

- Create a card for every unchecked task in /Projects/Launch/todo.md, in the Backlog stack.
- Every Monday, create a card "Weekly review" in the Team board with a due date of Friday.
- Only list the cards you would create from these notes, and create nothing.
- Move the action items from the last standup file into the board called Ops.

## What Nextcloud allows, and what to know first

- A Deck card title is limited to 255 characters in the API, and a longer title is rejected with an error.
- The card description is markdown, so a checklist or link from the notes keeps its formatting in the card.
- The Deck API takes a due date in ISO-8601 format, for example 2026-10-23T00:00:00+00:00.
- Stacks are the columns of a board, and the Deck docs set no limit on the number of cards per stack.
- A user who lacks access to a board gets 403 Permission denied from the API, so the agent can only write to boards your account can open.

create\_deck\_card asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.

Sources: [Nextcloud Deck: REST API](https://deck.readthedocs.io/en/latest/API/) · [Nextcloud Deck: User documentation](https://deck.readthedocs.io/en/latest/User%5Fdocumentation%5Fen/) · [Nextcloud Admin Manual: Context Agent](https://docs.nextcloud.com/server/stable/admin%5Fmanual/ai/app%5Fcontext%5Fagent.html)

## Call create\_deck\_card from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/nextcloud/boards/7/deck-cards \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"stack_id":21,"title":"Send pricing draft to finance","description":"Owner: Lena\nFrom the product sync on 15 Oct: \"Lena sends the pricing draft to finance by Friday.\"","due_date":"2026-10-23"}'
```

Example response

```
{
"card_id": 318,
"board_id": 7,
"stack_id": 21,
"title": "Send pricing draft to finance",
"due_date": "2026-10-23",
"status": "created"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is nextcloud\_write → create\_deck\_card. Example data.

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

## Nextcloud tools this automation uses

__Cotlet Nextcloud tools used to create Nextcloud Deck cards from meeting notes__
| Tool | Parameters |
| ------------------ | --------------------------------------------------- |
| list\_deck\_boards | none |
| list\_deck\_cards | board\_id, stack\_id |
| create\_deck\_card | board\_id, stack\_id, title, description, due\_date |

[All 15 Nextcloud tools with descriptions](https://cotlet.dev/integrations/nextcloud-api-mcp-server.md#tools)

## Frequently asked questions

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

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

- [Share a Nextcloud file with an expiring, password-protected link](https://cotlet.dev/integrations/nextcloud-api-mcp-server/share-file-with-expiring-link.md)
- [Audit and remove old public share links in Nextcloud](https://cotlet.dev/integrations/nextcloud-api-mcp-server/audit-public-share-links.md)
- [Nextcloud API and MCP server: every tool](https://cotlet.dev/integrations/nextcloud-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Nextcloud.

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

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

---

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.