Monday.com n8n integrationAutomate Monday.com with n8n.

Archiving pulls a board out of the active workspace without destroying it. The board leaves the sidebar, its items stop appearing in searches, and the whole thing stays recoverable inside Monday.com.

• Board Name or ID: choose the board from the list n8n loads from your account, or pass the identifier through an expression such as {{ $json.boardId }} when an earlier step already knows which board is finished.

A fresh board is created and the response carries its identifier, which the rest of the workflow needs before it can add a single group or item.

• Name: the board name, usually built from the record that triggered the run.
• Kind: public, private or share, which decides who inside the account can see it.
• Template ID: optional, in Additional Fields, to start from an existing board template instead of an empty grid.

Reading one board returns its details as a single item, which is what you want before writing into it or before branching on something the board already says.

• Board Name or ID: the identifier of the board to read, either picked from the dropdown or resolved at runtime with an expression.

This lists the boards the credential can see, which is the easiest way to inventory an account or to feed a loop that visits each board in turn.

• Return All: switched on, n8n walks the API pages and brings back every board; switched off, it stops at the number set in Limit.
• Limit: the maximum number of boards returned when Return All stays off, handy while you are still testing.

New columns get added to an existing board from the workflow, which matters when boards are generated automatically and have to come out with the right structure.

• Board Name or ID: the board that receives the column.
• Title: the column header as people will read it on the board.
• Column Type: the behavior of the column, from status, date, people, numbers, email, dropdown and the rest of the list.
• Defauls: optional JSON in Additional Fields that presets the column values.

Listing columns returns each column with its identifier, and that identifier is the thing you need before any operation that writes a column value.

• Board Name or ID: the board whose columns are listed, chosen from the list or resolved from an expression.

Deleting a group removes that section of the board along with what sits inside it, so it belongs at the end of a lifecycle rather than in the middle of one.

• Board Name or ID: the board holding the group.
• Group Name or ID: the group to remove, picked from the list n8n loads for that board.

Groups are the horizontal bands inside a board. Creating one gives the workflow a place to drop items instead of piling everything into whatever group happens to be first.

• Board Name or ID: the board that gets the new group.
• Name: the group name, often a period or a batch label computed at runtime.

The list of groups on a board comes back with names and identifiers, which turns a human label into the value the create and move operations expect.

• Board Name or ID: the board to inspect.

Updates are the comment thread attached to an item. Posting one leaves a trace people actually read, and it notifies whoever follows the item.

• Item ID: the item that receives the comment.
• Update Text: the text of the update, which is where an expression like {{ $json.message }} earns its keep.

One column on one item gets a new value. This is the workhorse of any status sync, and the value goes in as JSON whose shape depends on the column type.

• Board Name or ID: the board the item belongs to.
• Item ID: the item to modify.
• Column Name or ID: the column to write, chosen from the list or resolved at runtime.
• Value: the column value in JSON format, which a date column and a status column do not write the same way.

Several columns are rewritten in a single call, which keeps a board consistent and avoids chaining four nodes that could each fail on their own.

• Board Name or ID: the board holding the item.
• Item ID: the item to update.
• Column Values: the column fields and their values together in one JSON object, keyed by column identifier.

This is the operation most workflows are built around. A new item lands in a precise group of a precise board, and its columns can be filled in the same call.

• Board Name or ID: where the item goes.
• Group Name or ID: which band of the board receives it.
• Name: the item name, the line people read first.
• Column Values: optional JSON in Additional Fields to populate columns immediately instead of a follow-up call.

An item is removed from its board. There is no soft option here, which is why it usually sits behind a condition rather than running on everything the previous node returned.

• Item ID: the identifier of the item to delete, typically carried over from a search step.

Fetching an item by its identifier returns what the board currently holds, and it accepts more than one identifier at a time.

• Item ID: the item identifier, and several can be added separated by a comma to read a batch in one execution.

Searching by column value is how a workflow finds an item it did not create. Give it a column and the value to match, and it returns the items that carry it.

• Board Name or ID: the board to search.
• Column Name or ID: the column used as the search key.
• Column Value: the value to match, often an email or an external reference.
• Return All and Limit: bring back every match, or cap the number of items returned.

A whole group of a board comes back as items, ready to be counted, filtered or written somewhere else.

• Board Name or ID: the board to read.
• Group Name or ID: the group inside it, so the run stays scoped instead of pulling the entire board.
• Return All and Limit: page through every item of the group, or stop at a fixed number while testing.

Moving an item changes the group it sits in, without touching its name, its updates or its column values. On a board organized by stage, this is the visible part of progress.

• Board Name or ID: the board involved.
• Item ID: the item on the move.
• Group Name or ID: the destination group.