Monday.com Integration

Manage Monday.com boards, items, groups, and statuses via the Monday.com MCP connector. Read board summaries, create/update items, and sync with Tandem task management. Outputs follow template.md.

---

Language

See METHODOLOGY.md language mirror rule. Reply in the user's language.

---

Prerequisites

This skill requires the Monday.com MCP connector. If not connected:

Monday.com isn't connected yet. You'll need to set it up first.

AskUserQuestion:
  - "Set up Monday.com connection now"
  - "Skip — I'll do it later"

If "Set up now" — guide the user to /connect and select Monday.com. After connection, return to the original request.

---

Column Value Formatting

Before calling create_item or change_item_column_values:

1. Query column types -- call get_column_type_info for the target board to discover which columns are phone, email, board_relation, date, status, link, or text
2. Auto-format values -- format each column value according to its type. See ${CLAUDE_SKILL_DIR}/references/column-formats.md for the correct JSON structure per column type
3. Never send plain strings for structured column types -- Monday.com API will reject them

Common pitfall: sending "0509778878" for a phone column instead of {"phone":"0509778878","countryShortName":"IL"}.

---

Operations

All operations use AskUserQuestion for board/group/item/status selection — never ask the user to type IDs. Present options dynamically from the API.

Supported operations:

• Read boards — list boards, view board summary with filters (by status/group/assignee/overdue)
• Create item — board -> group -> details (status, assignee, due date) -> confirm -> create
• Update status — find item -> show current -> offer new status options -> update
• Move between groups — find item -> select target group -> move
• Add update/comment — find item -> accept text -> post -> confirm
• Archive item — find item -> confirm archival -> archive (restorable from Monday.com UI)
• Delete item — find item -> warn permanent -> confirm or offer archive instead -> delete
• Create subitems — find parent item -> subitem details -> create under parent
• Search/filter items — search by name, filter by column value, or browse all
• Board setup — create board -> add groups -> add columns (with template option)
• Duplicate item — read source item -> select target -> create copy with same values

For detailed step-by-step procedures with AskUserQuestion flows for each operation, read ${CLAUDE_SKILL_DIR}/references/operations.md.

For board setup templates (CRM, project management, etc.), see ${CLAUDE_SKILL_DIR}/references/common-patterns.md.

---

Task Format

When syncing Monday.com items to kanban.md, follow the canonical format in tandem-skills/tasks/task-manager/references/kanban-format.md.

Key rules:

1. Read <!-- Config: Last Task ID: NNN --> from kanban.md to get the next ID
2. Increment the counter: if last ID was 005, next task is TASK-006
3. Write the updated counter back: <!-- Config: Last Task ID: 006 -->
4. Use canonical format: ### TASK-XXX | Title (H3, 3-digit zero-padded, pipe separator)
5. Meta on ONE line: **Priority**: X | **Category**: X | **Assigned**: @user

---

Proactivity Hooks

After completing a task in task-manager:

This task might be on your Monday.com board too. Want to update it there?

AskUserQuestion:
  - "Yes — mark it as Done in Monday"
  - "No — it's only tracked here"

After generating a daily plan:

Want to sync today's plan with your Monday.com board?

AskUserQuestion:
  - "Yes — update statuses for today's tasks"
  - "No — keep them separate"

After creating an item in Monday.com:

AskUserQuestion:
  - "Also track this in my local task list"
  - "Create another item"
  - "Nothing else"

After viewing a board:

AskUserQuestion:
  - "Create a new item"
  - "Update an item's status"
  - "Nothing else for now"

---

Error Handling

Error code quick reference:

Error	Common Cause	Recovery
InvalidColumnValueException	Wrong JSON format for column type	Check column-formats.md, call get_column_type_info to verify type
ItemNotFoundException	Item ID doesn't exist or was deleted	Search by name instead, offer to create new
InvalidBoardIdException	Board doesn't exist or no access	Call list_boards to show available boards
ColumnNotFoundException	Column ID doesn't match board schema	Call get_column_type_info to get correct column IDs
CreateBoardException	Invalid board parameters	Check board_kind is "public" or "private"
ResourceNotFoundException	Generic "not found"	Retry search with broader terms
UserUnauthorizedException	Token expired or insufficient permissions	Guide user to reconnect via /connect
ComplexityException	Query too complex (exceeded budget)	Simplify: fewer columns, use pagination
RateLimitException	Too many requests per minute	Wait 30 seconds, then retry

Connection errors: Offer "Try again" / "Check connection settings (/connect)" / "Skip for now"

Item not found: Offer "Show the full board so I can pick" / "Try a different search" / "Create it as a new item"

Permission errors: Offer "Try a different board" / "Check connection permissions (/connect)" / "Skip for now"

---

Rate Limits

Monday.com uses a complexity budget system, not simple request counting. Each query has a complexity cost based on the amount of data requested. Boards with many items cost more.

When you hit a ComplexityException:

1. Request fewer columns (specify only the fields you need)
2. Use pagination for large boards (MCP tools handle cursors, but smaller pages help)
3. Add small delays between rapid successive operations

MCP tools manage most complexity internally, but awareness helps when debugging repeated failures.

---

Batch Operations

When creating or updating multiple items (e.g., importing a list):

1. Process items sequentially -- create each item, wait for the response, then proceed
2. For bulk updates, call change_item_column_values per item sequentially
3. For 10+ items, add a brief pause between calls to stay within rate limits
4. Show progress to the user: "Created 3 of 10 items..."

Never attempt parallel item creation -- it risks hitting complexity and rate limits.

---

Schema-First Workflow

ALWAYS call get_column_type_info before creating or updating items. This is not optional.

1. Fetch the board's column schema (IDs, types, settings)
2. Match user-provided values to the correct column IDs
3. Format values per ${CLAUDE_SKILL_DIR}/references/column-formats.md
4. Only then call create_item or change_item_column_values

Cache the schema within a session -- same board, same schema. No need to re-fetch for every operation on the same board.

---

Anti-Patterns

• Do NOT ask the user to type board IDs or item IDs — always use names and AskUserQuestion
• Do NOT modify items without confirmation — always preview and confirm
• Do NOT skip the board/group selection — always let the user choose
• Do NOT assume board structure — fetch it dynamically from the API
• Do NOT show raw API responses — format everything using template.md
• Do NOT create items without all required fields confirmed
• Do NOT send plain string values for phone, email, date, status, link, or board_relation columns -- always format per column-formats.md