smithery/sickn33

monday-automation

Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.

Installation

$ npx skills add smithery/sickn33 --skill monday-automation

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/sickn33 · top by installs.

npx skills add smithery/sickn33

Browse all from smithery/sickn33

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 12,632 B
  • docs SUMMARY.md 196 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Monday.com Automation via Rube MCP

Automate Monday.com work management workflows including board creation, item management, column value updates, group organization, subitems, and update/comment threads through Composio's Monday toolkit.

Prerequisites

  • Rube MCP must be connected (RUBESEARCHTOOLS available)
  • Active Monday.com connection via RUBEMANAGECONNECTIONS with toolkit monday
  • Always call RUBESEARCHTOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

  1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
  2. Call RUBEMANAGECONNECTIONS with toolkit monday
  3. If connection is not ACTIVE, follow the returned auth link to complete Monday.com OAuth
  4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Create and Manage Boards

When to use: User wants to create a new board, list existing boards, or set up workspace structure.

Tool sequence:

  1. MONDAYGETWORKSPACES - List available workspaces and resolve workspace ID [Prerequisite]
  2. MONDAYLISTBOARDS - List existing boards to check for duplicates [Optional]
  3. MONDAYCREATEBOARD - Create a new board with name, kind, and workspace [Required]
  4. MONDAYCREATECOLUMN - Add columns to the new board [Optional]
  5. MONDAYCREATEGROUP - Add groups to organize items [Optional]
  6. MONDAY_BOARDS - Retrieve detailed board metadata [Optional]

Key parameters:

  • board_name: Name for the new board (required)
  • board_kind: "public", "private", or "share" (required)
  • workspace_id: Numeric workspace ID; omit for default workspace
  • folderid: Folder ID; must be within workspaceid if both provided
  • template_id: ID of accessible template to clone

Pitfalls:

  • board_kind is required and must be one of: "public", "private", "share"
  • If both workspaceid and folderid are provided, the folder must exist within that workspace
  • template_id must reference a template the authenticated user can access
  • Board IDs are large integers; always use the exact value from API responses

2. Create and Manage Items

When to use: User wants to add tasks/items to a board, list existing items, or move items between groups.

Tool sequence:

  1. MONDAYLISTBOARDS - Resolve board name to board ID [Prerequisite]
  2. MONDAYLISTGROUPS - List groups on the board to get group_id [Prerequisite]
  3. MONDAYLISTCOLUMNS - Get column IDs and types for setting values [Prerequisite]
  4. MONDAYCREATEITEM - Create a new item with name and column values [Required]
  5. MONDAYLISTBOARD_ITEMS - List all items on the board [Optional]
  6. MONDAYMOVEITEMTOGROUP - Move an item to a different group [Optional]
  7. MONDAYITEMSPAGE - Paginated item retrieval with filtering [Optional]

Key parameters:

  • board_id: Board ID (required, integer)
  • item_name: Item name, max 256 characters (required)
  • group_id: Group ID string to place the item in (optional)
  • column_values: JSON object or string mapping column IDs to values

Pitfalls:

  • columnvalues must use column IDs (not titles); get them from MONDAYLIST_COLUMNS
  • Column value formats vary by type: status uses {"index": 0} or {"label": "Done"}, date uses {"date": "YYYY-MM-DD"}, people uses {"personsAndTeams": [{"id": 123, "kind": "person"}]}
  • item_name has a 256-character maximum
  • Subitem boards are NOT supported by MONDAYCREATEITEM; use GraphQL via MONDAYCREATEOBJECT

3. Update Item Column Values

When to use: User wants to change status, date, text, or other column values on existing items.

Tool sequence:

  1. MONDAYLISTCOLUMNS or MONDAY_COLUMNS - Get column IDs and types [Prerequisite]
  2. MONDAYLISTBOARDITEMS or MONDAYITEMS_PAGE - Find the target item ID [Prerequisite]
  3. MONDAYCHANGESIMPLECOLUMNVALUE - Update text, status, or dropdown with a string value [Required]
  4. MONDAYUPDATEITEM - Update complex column types (timeline, people, date) with JSON [Required]

Key parameters for MONDAYCHANGESIMPLECOLUMNVALUE:

  • board_id: Board ID (integer, required)
  • item_id: Item ID (integer, required)
  • column_id: Column ID string (required)
  • value: Simple string value (e.g., "Done", "Working on it")
  • createlabelsif_missing: true to auto-create status/dropdown labels (default true)

Key parameters for MONDAYUPDATEITEM:

  • board_id: Board ID (integer, required)
  • item_id: Item ID (integer, required)
  • column_id: Column ID string (required)
  • value: JSON object matching the column type schema
  • createlabelsif_missing: false by default; set true for status/dropdown

Pitfalls:

  • Use MONDAYCHANGESIMPLECOLUMNVALUE for simple text/status/dropdown updates (string value)
  • Use MONDAYUPDATEITEM for complex types like timeline, people, date (JSON value)
  • Column IDs are lowercase strings with underscores (e.g., "status1", "date2", "text"); get them from MONDAYLISTCOLUMNS
  • Status values can be set by label name ("Done") or index number ("1")
  • createlabelsifmissing defaults differ: true for CHANGESIMPLE, false for UPDATE_ITEM

4. Work with Groups and Board Structure

When to use: User wants to organize items into groups, add columns, or inspect board structure.

Tool sequence:

  1. MONDAYLISTBOARDS - Resolve board ID [Prerequisite]
  2. MONDAYLISTGROUPS - List all groups on a board [Required]
  3. MONDAYCREATEGROUP - Create a new group [Optional]
  4. MONDAYLISTCOLUMNS or MONDAY_COLUMNS - Inspect column structure [Required]
  5. MONDAYCREATECOLUMN - Add a new column to the board [Optional]
  6. MONDAYMOVEITEMTOGROUP - Reorganize items across groups [Optional]

Key parameters:

  • board_id: Board ID (required for all group/column operations)
  • groupname: Name for new group (CREATEGROUP)
  • columntype: Must be a valid GraphQL enum token in snakecase (e.g., "status", "text", "long_text", "numbers", "date", "dropdown", "people")
  • title: Column display title
  • defaults: JSON string for status/dropdown labels, e.g., '{"labels": ["To Do", "In Progress", "Done"]}'

Pitfalls:

  • columntype must be exact snakecase values; "person" is NOT valid, use "people"
  • Group IDs are strings (e.g., "topics", "newgroup12345"), not integers
  • MONDAYCOLUMNS accepts an array of boardids and returns column metadata including settings
  • MONDAYLISTCOLUMNS is simpler and takes a single board_id

5. Manage Subitems and Updates

When to use: User wants to view subitems of a task or add comments/updates to items.

Tool sequence:

  1. MONDAYLISTBOARD_ITEMS - Find parent item IDs [Prerequisite]
  2. MONDAYLISTSUBITEMSBYPARENT - Retrieve subitems with column values [Required]
  3. MONDAYCREATEUPDATE - Add a comment/update to an item [Optional]
  4. MONDAYCREATEOBJECT - Create subitems via GraphQL mutation [Optional]

Key parameters for MONDAYLISTSUBITEMSBYPARENT:

  • parentitemids: Array of parent item IDs (integer array, required)
  • includecolumnvalues: true to include column data (default true)
  • includeparentfields: true to include parent item info (default true)

Key parameters for MONDAYCREATEOBJECT (GraphQL):

  • query: Full GraphQL mutation string
  • variables: Optional variables object

Pitfalls:

  • Subitems can only be queried through their parent items
  • To create subitems, use MONDAYCREATEOBJECT with a create_subitem GraphQL mutation
  • MONDAYCREATEUPDATE is for adding comments/updates to items (Monday's "updates" feature), not for modifying item values
  • MONDAYCREATEOBJECT is a raw GraphQL endpoint; ensure correct mutation syntax

Common Patterns

ID Resolution

Always resolve display names to IDs before operations:

  • Board name -> boardid: MONDAYLIST_BOARDS and match by name
  • Group name -> groupid: MONDAYLISTGROUPS with boardid
  • Column title -> columnid: MONDAYLISTCOLUMNS with boardid
  • Workspace name -> workspaceid: MONDAYGET_WORKSPACES and match by name
  • Item name -> itemid: MONDAYLISTBOARDITEMS or MONDAYITEMSPAGE

Pagination

Monday.com uses cursor-based pagination for items:

  • MONDAYITEMSPAGE returns a cursor in the response for the next page
  • Pass the cursor to the next call; boardid and queryparams are ignored when cursor is provided
  • Cursors are cached for 60 minutes
  • Maximum limit is 500 per page
  • MONDAYLISTBOARDS and MONDAYGETWORKSPACES use page-based pagination with page and limit

Column Value Formatting

Different column types require different value formats:

  • Status: {"index": 0} or {"label": "Done"} or simple string "Done"
  • Date: {"date": "YYYY-MM-DD"}
  • People: {"personsAndTeams": [{"id": 123, "kind": "person"}]}
  • Text/Numbers: Plain string or number
  • Timeline: {"from": "YYYY-MM-DD", "to": "YYYY-MM-DD"}

Known Pitfalls

ID Formats

  • Board IDs and item IDs are large integers (e.g., 1234567890)
  • Group IDs are strings (e.g., "topics", "newgroup12345")
  • Column IDs are short strings (e.g., "status_1", "date4", "text")
  • Workspace IDs are integers

Rate Limits

  • Monday.com GraphQL API has complexity-based rate limits
  • Large boards with many columns increase query complexity
  • Use limit parameter to reduce items per request if hitting limits

Parameter Quirks

  • columntype for CREATECOLUMN must be exact snake_case enum values; "people" not "person"
  • columnvalues in CREATEITEM accepts both JSON string and object formats
  • MONDAYCHANGESIMPLECOLUMNVALUE auto-creates missing labels by default; MONDAYUPDATEITEM does not
  • MONDAYCREATEOBJECT is a raw GraphQL interface; use it for operations without dedicated tools (e.g., createsubitem, deleteitem, archive_board)

Response Structure

  • Board items are returned as arrays with id, name, and state fields
  • Column values include both raw value (JSON) and rendered text (display string)
  • Subitems are nested under parent items and cannot be queried independently

Quick Reference

Task Tool Slug Key Params
List workspaces MONDAYGETWORKSPACES kind, state, limit
Create workspace MONDAYCREATEWORKSPACE name, kind
List boards MONDAYLISTBOARDS limit, page, state
Create board MONDAYCREATEBOARD boardname, boardkind, workspace_id
Get board metadata MONDAY_BOARDS boardids, boardkind
List groups MONDAYLISTGROUPS board_id
Create group MONDAYCREATEGROUP boardid, groupname
List columns MONDAYLISTCOLUMNS board_id
Get column metadata MONDAY_COLUMNS boardids, columntypes
Create column MONDAYCREATECOLUMN boardid, columntype, title
Create item MONDAYCREATEITEM boardid, itemname, column_values
List board items MONDAYLISTBOARD_ITEMS board_id
Paginated items MONDAYITEMSPAGE boardid, limit, queryparams
Update column (simple) MONDAYCHANGESIMPLECOLUMNVALUE boardid, itemid, column_id, value
Update column (complex) MONDAYUPDATEITEM boardid, itemid, column_id, value
Move item to group MONDAYMOVEITEMTOGROUP itemid, groupid
List subitems MONDAYLISTSUBITEMSBYPARENT parentitemids
Add comment/update MONDAYCREATEUPDATE item_id, body
Raw GraphQL mutation MONDAYCREATEOBJECT query, variables

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Example

User request:

Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio).

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.