monday.com
Read and write monday.com boards - browse boards with their groups and columns, page through items, create and update them, archive or delete them, and work their update threads.
Connect a monday.com account with a personal API token to run its boards end to end: list the boards the token can reach with monday.com's own item counts, read a board's groups and columns with the ids and types every write depends on, page through items by cursor or filter them by column value, create items with column values set, change those values or move an item between groups, archive or delete it, and read and post the updates (monday.com's word for comments) on it. Everything written through this connection is attributed in monday.com to the person whose token it is.
Connect
| Credential field | Required | Where it comes from |
|---|---|---|
API token (API_TOKEN) | Yes | From your avatar → Developers → My access tokens. It carries the full board access of the user who created it - there are no scopes to narrow it - and every write is attributed to them. |
Tools
| Tool | Access | What it does |
|---|---|---|
Whoami (yekar.monday.whoami) | Read | The monday.com user this connection's token belongs to, and the account it is in. Run it first - every other tool is scoped to this person's own access, and a guest token sees only the boards it was invited to. |
List boards (yekar.monday.list-boards) | Read | A page of the boards this token's user can see, each with monday.com's own count of its items. Boards page by number here; items page by cursor in List items. |
Get board (yekar.monday.get-board) | Read | One board's structure - its groups (sections) and its columns with ids, types and settings. This is what Create item and Update item need, because a column value's shape depends on its column's type. Items are not included; use List items. |
List items (yekar.monday.list-items) | Read | A page of a board's items, optionally filtered by column values, with cursor paging. Ask for only the columns you need - monday.com bills by query complexity, so every extra column costs page-size times more. |
Get item (yekar.monday.get-item) | Read | One item in full - its group, board, and every column value in both monday.com's rendered form and the raw JSON string a write to that column must mirror. |
Create item (yekar.monday.create-item) | Write | Create an item on a board, optionally in a specific group and with column values set. Column values are keyed by column id and their shape depends on the column's type - call Get board first. monday.com has no dry run. |
Update item (yekar.monday.update-item) | Write | Change an item's column values and/or move it to another group. Column values are keyed by column id and their shape depends on the column's type - call Get board first. Only the columns you name are touched. |
Archive or delete item (yekar.monday.delete-item) | Write | Archive an item (reversible - it keeps its id and history) or delete it (monday.com's recycle bin holds it for 30 days, restorable only by hand). The mode is required: there is no default, because the two have very different consequences. |
List item updates (yekar.monday.list-item-updates) | Read | A page of an item's updates - monday.com's word for the comments on it, not a log of column changes. Newest first. monday.com reports no total, so counting a thread means paging it. |
Add item update (yekar.monday.create-item-update) | Write | Post an update - monday.com's word for a comment - on an item, attributed to the user whose token this connection holds. Everyone subscribed to the item is notified immediately; there is no draft state and no unsend. |
Notes
- Create a token in monday.com under your avatar → Developers → My access tokens (or Administration → Connections → API for an account-level one) and paste it here.
- A personal API token IS that person: it carries exactly their board access, and every item, column change and update made through this connection appears in monday.com under their name. Bind automations using this integration as service connections so the attribution is a role rather than an individual's side effect. A GUEST token additionally sees only the boards it was invited to.
- Run Whoami first, then Get board on the board you intend to work. A monday.com write is keyed by COLUMN ID, and a column value's JSON shape is decided by that column's TYPE - Get board is the only place to learn both, and a status column's legal labels live in its settings string.
- monday.com rate-limits by query COMPLEXITY, not by request count: an account gets a complexity budget per minute, and one query asking for many columns across many items can exhaust it where a hundred small queries would not. Ask List items for only the columns you need.
- This integration pins monday.com's API version 2025-04. monday.com promotes a new dated schema version periodically and removes fields as it does, so the pin is what keeps a running automation from changing shape underneath itself.
- Archiving and deleting are different, and the tool makes you choose: archiving is reversible and keeps the item's id and history, while a deleted item goes to monday.com's recycle bin for 30 days and can only be restored by a person in its own UI.
- monday.com calls comments 'updates'. Add item update posts a comment; Update item changes column values. They are unrelated operations.
- Add one credential per token - a production and a sandbox token can live on the same connection.