Pipedream monday.com steps in n8n

monday.com workflows on Pipedream create items from forms and emails, update status columns, and react when a column changes. n8n has a native monday.com node for boards, groups and items. There is no trigger node, so events come from monday.com webhooks.

The n8n side

monday.com node (n8n-nodes-base.mondayCom, n8n 1.22.6 or newer):

Resource	Operations
Board	Archive, Create, Get, Get Many
Board Column	Create, Get Many
Board Group	Create, Delete, Get Many
Board Item	Add Update, Change Column Value, Change Multiple Column Values, Create, Delete, Get, Get Many, Get By Column Value, Move

There is no monday.com trigger node.

The table shows node version 1, which matches docs.n8n.io and stable n8n 2.44. n8n 2.45 (beta on 21.10.2026) ships a version 2 with resources Board, Board Group, Column, Item and Update (Item → Create, Update, Search, Move…); new nodes will default to it once it is stable, so labels may differ.

What maps where

Pipedream (app monday)	In n8n	Status
Create Item	Board Item → Create	manual
Create Subitem	HTTP Request → GraphQL create_subitem	manual
Create an Update	Board Item → Add Update	manual
Update Column Values	Board Item → Change Multiple Column Values	manual
Get Items By Column Value	Board Item → Get By Column Value	manual
Create Board, Create Column, Create Group	Board → Create, Board Column → Create, Board Group → Create	manual
New Item Created (Instant)	monday webhook "When an item is created" → n8n Webhook	manual
Column Value Updated / Specific Column Updated / Name Updated (Instant)	monday webhook "When a column changes" → n8n Webhook	manual
New Board Created (polling)	Schedule Trigger + Board → Get Many	manual

The converter has no monday.com mapping yet. Each step is a placeholder that keeps its props, including the column-values JSON, so the rebuild is mostly paste work.

monday.com credentials in n8n

• API token: profile picture → Developers → My access tokens.
• OAuth2: an app in the monday Developer Center with boards:read and boards:write.

The HTTP Request node can reuse the credential for GraphQL calls the node does not cover (subitems, files, users).

Webhooks without a trigger node

monday.com webhooks need a challenge response: the first request contains {"challenge": "…"} and must be echoed back.

1. Webhook node (POST), Respond set to "Using Respond to Webhook Node".
2. If {{ $json.body.challenge }} exists → Respond to Webhook with {"challenge": "{{ $json.body.challenge }}"}.
3. Otherwise process body.event (board, item, column, value).
4. In monday.com: board → Integrate → Webhooks → pick the event, paste the production URL.

Typical migration: form to board item

Pipedream: Typeform New Submission → monday Create Item (board, group, column values). n8n: Typeform Trigger → monday.com → Board Item → Create (Board ID, Group ID, Name, Column Values JSON). Status and date columns need their own JSON shape ({"status": {"label": "Working on it"}}).

monday.com migration pitfalls

• Complexity limits. Each query may cost at most 5 million complexity points; personal tokens get 10 million points per minute in total (1 million on trial and free accounts). Get Many on a big board can hit it; paginate.
• Column IDs (status, date4, text_1) differ from titles. Board Column → Get Many lists them.
• Subitems live on a separate board; the node does not create them.
• Challenge step. Without the echo, monday.com never activates the webhook.

How to move your monday.com workflows

1. Export from Pipedream.
2. Upload on /convert; the free report lists every monday.com step with its props.
3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the webhook guide. Related: Asana, Trello, ClickUp.