> For the complete documentation index, see [llms.txt](https://docs.zigiwave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigiwave.com/available-systems/monday.com.md).

# monday.com

Connect monday.com to ZigiOps. Supported versions, prerequisites, API token authentication, connected system configuration, supported fields, and operations.

### What is monday.com integration in ZigiOps?

monday.com is a work management platform where teams plan and track tasks, bugs, epics, and projects on customizable boards.

ZigiOps enables secure, agentless, no-code integration between monday.com and ITSM, DevOps, monitoring, and CRM systems. ZigiOps connects through the **monday.com GraphQL API v2** and authenticates with a **personal API token**.

monday.com has no built-in “task”, “bug”, or “epic” item type. Every item lives on a board, and each tenant defines its own board columns. ZigiOps therefore discovers **one collection per board**. The board name is converted to snake case, so “Tasks” becomes `tasks`, “Bugs Queue” becomes `bugs_queue`, and “Epics” becomes `epics`. Each board’s columns become real fields on that collection, so you work with readable field names such as `task_status` and `bug_priority`, and real select-list values, instead of raw column-value JSON.

With ZigiOps, you can:

* Sync monday.com items (for example, tasks, bugs, and epics) with another system. Each board is its own entity, and its status, priority, and type columns are exposed as select lists using the board’s own labels.
* Poll for new or changed items by `created_at` / `updated_at` (`>`, `<`, `>=`, `<=`). All time fields are converted to epoch.
* Get a single item by ID.
* Create items on a board: name, group, and any writable column.
* Update any column, including name and group. Unspecified columns are left untouched.
* Set the item description (monday.com’s rich-text doc), written as Markdown and read back as plain text.
* Read an item’s comments, filtered by created time, and add new comments to an existing item.
* Read the files on an item, from both file columns and comments, including the binary content, and upload files to an item.
* Read and create subitems under an item.
* Query boards, board columns, groups, and users as lookup lists.
* See who last changed an item, when the board has a “Last updated” column.

### Which monday.com versions are supported?

Using a supported version is mandatory.

| Product    | Supported Deployment Types | Supported Versions | API Used                                                                           |
| ---------- | -------------------------- | ------------------ | ---------------------------------------------------------------------------------- |
| monday.com | All                        | All                | monday.com GraphQL API v2 (`POST /v2`, file uploads via `POST /v2/file` multipart) |

### Are there any environmental prerequisites for monday.com?

Confirm the prerequisites of the corresponding integration template before continuing further, as some templates may not require all environmental prerequisites.

See the **Related Templates** section at the end of this page.

ZigiOps authenticates to monday.com with a personal API token. Get the token before you add monday.com as a connected system.

#### How do I get a monday.com personal API token?

1. Log in to your **monday.com** account with the user that ZigiOps will use for the integration.
2. Navigate to **Profile > Admin > API**.
3. Copy your personal API token and store it securely. You will need it when you configure the connected system in ZigiOps.

{% hint style="warning" %}
ZigiOps sends the token as is in the `Authorization` header, without a `Bearer` prefix. Do not add `Bearer` to the token. A Bearer-prefixed token returns `Not authenticated` with HTTP 200.
{% endhint %}

### How do I connect monday.com to ZigiOps?

#### monday.com - Connected System Configuration

Follow the steps below to add monday.com as a connected system in ZigiOps.

{% stepper %}
{% step %}
**Log in to ZigiOps**

Log in to your **ZigiOps** instance.
{% endstep %}

{% step %}
**Add monday.com as a connected system**

Navigate to **Connected Systems > Add New System > monday.com**.
{% endstep %}

{% step %}
**Configure the connection parameters**

**URL** (required)

Input the monday.com API host. Use the bare host without the `/v2` suffix; ZigiOps appends it automatically.

Example: `https://api.monday.com`

**Personal Token** (required)

Input your monday.com personal API token. The value is stored as a secure password field.

**Proxy Settings** (optional)

Enable this option and input the proxy address and proxy port if a proxy server is required for outbound communication.
{% endstep %}

{% step %}
**Verify the connection**

Click **Verify URL and personal token** to test the connection. The test queries the board collection (`id`, `name`).
{% endstep %}

{% step %}
**Save the connected system**

Click **Save** to store the connected system.

Once saved, monday.com becomes available for use in ZigiOps integration templates.
{% endstep %}
{% endstepper %}

### Which monday.com entities and fields does ZigiOps support?

ZigiOps discovers one collection per board (for example, `tasks`, `bugs_queue`, `epics`). Every board collection includes the static fields below, plus one discovered field per board column.

#### Static fields

| Field             | Label         | Type                       | Query | Create | Update | Notes                                                                     |
| ----------------- | ------------- | -------------------------- | ----- | ------ | ------ | ------------------------------------------------------------------------- |
| `id`              | ID            | number                     | Yes   | No     | No     | Globally unique item ID                                                   |
| `name`            | Name          | string                     | Yes   | Yes    | Yes    | Required on create                                                        |
| `board_id`        | Board ID      | number                     | Yes   | No     | No     |                                                                           |
| `group_id`        | Group ID      | string                     | Yes   | Yes    | Yes    |                                                                           |
| `state`           | State         | string                     | Yes   | No     | No     | active / archived / deleted                                               |
| `creator_id`      | Creator ID    | number                     | Yes   | No     | No     |                                                                           |
| `url`             | URL           | string                     | Yes   | No     | No     |                                                                           |
| `created_at`      | Created At    | timestamp                  | Yes   | No     | No     | Filterable                                                                |
| `updated_at`      | Updated At    | timestamp                  | Yes   | No     | No     | Filterable                                                                |
| `updated_by_id`   | Updated By ID | number                     | Yes   | No     | No     | Only when the board has a “Last updated” column                           |
| `updated_by_name` | Updated By    | string                     | Yes   | No     | No     | Same as above. Shows the API-token user for writes made by ZigiOps        |
| `description`     | Description   | string                     | Yes   | Yes    | Yes    | Rich-text doc, written as Markdown                                        |
| `comments`        | Comments      | reference → comment \[]    | Yes   | Yes    | Yes    |                                                                           |
| `attachments`     | Attachments   | reference → attachment \[] | Yes   | Yes    | Yes    |                                                                           |
| `sub_items`       | Subitems      | reference → subitem \[]    | Yes   | Yes    | Yes    | Named `sub_items` to avoid clashing with monday.com’s own subitems column |

#### Discovered fields

The field name is the monday.com column ID and the label is the column title. monday.com column types are mapped to ZigiOps types as follows:

| monday.com Column Type                                   | ZigiOps Type                                               |
| -------------------------------------------------------- | ---------------------------------------------------------- |
| status                                                   | select-list (items taken from the column’s labels)         |
| numbers                                                  | number                                                     |
| checkbox                                                 | boolean                                                    |
| date                                                     | timestamp                                                  |
| timeline                                                 | string (date range, for example `2025-05-13 - 2025-05-26`) |
| people, dropdown, tags, board\_relation, everything else | string (the column’s text value)                           |

#### Static collections

| Collection   | Operations    | Description                                                                                                                                         |
| ------------ | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| `board`      | Query         | Boards (id, name, state, board\_kind, workspace\_id, description, url, items\_count, updated\_at), with nested groups and columns                   |
| `column`     | Query         | Board column definitions (id, title, type, settings\_str). Reached through `board.columns`                                                          |
| `group`      | Query         | Board groups (id, title, color, position, archived, deleted). Reached through `board.groups` only, because monday.com has no top-level groups query |
| `user`       | Query         | Users (id, name, email, enabled, created\_at)                                                                                                       |
| `comment`    | Query, Create | Item comments, called “updates” in monday.com (id, item\_id, body (HTML), text\_body, creator\_id, created\_at, updated\_at, assets)                |
| `attachment` | Query, Create | Files/assets (id, name, file\_extension, file\_size, url, created\_at, blob, filename)                                                              |
| `subitem`    | Query, Create | Subitems (id, name, board\_id, created\_at, updated\_at)                                                                                            |

### Which operations does ZigiOps support for monday.com?

#### Read operations

| Operation                      | monday.com API                                                                         | Filtering                                                                                                                                                         |
| ------------------------------ | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Get boards                     | `boards(limit: 100)` / `boards(ids: […])`                                              | `id =`                                                                                                                                                            |
| Get users                      | `users(limit: 200)` / `users(ids: […])`                                                | `id =`                                                                                                                                                            |
| Get items                      | `boards(ids:[board]) { items_page(query_params: …) }`, cursor-paginated (100 per page) | `=`, `<`, `>`, `<=`, `>=` on any column. `created_at` / `updated_at` use monday.com’s `**creation_log**` / `**last_updated**` pseudo columns                      |
| Get item by ID                 | `items(ids: […])`                                                                      | `id =`                                                                                                                                                            |
| Get comments                   | `items(ids:[id]) { updates {…} }`                                                      | Created-time filters (`=`, `<`, `>`, `<=`, `>=`), plus `not-empty` / `is-empty`. Applied by the connector, because monday.com has no server-side date filter here |
| Get attachments (incl. binary) | `items(ids:[id]) { column_values { FileValue } updates { assets } }`                   | Created-time filters (`=`, `<`, `>`, `<=`, `>=`), applied by the connector                                                                                        |
| Get subitems                   | `items(ids:[id]) { subitems {…} }`                                                     | Parent item ID                                                                                                                                                    |

#### Write operations

| Operation       | monday.com API                                                | Required Fields          | Notes                                                                                                                                       |
| --------------- | ------------------------------------------------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Create item     | `create_item`                                                 | `name`                   | Any column and `group_id` are optional                                                                                                      |
| Update item     | `change_multiple_column_values`                               | `id`                     | Merges: columns left out of the update keep their current values                                                                            |
| Set description | `set_item_description_content`                                | `id`, `description`      | Separate mutation (description is not a column)                                                                                             |
| Add comment     | `create_update`                                               | `id`, `comments.body`    | One call per comment                                                                                                                        |
| Add attachment  | `create_update` + `add_file_to_update` (multipart `/v2/file`) | `id`, `attachments.blob` | ZigiOps first creates a carrier comment, whose body is `attachments.name` or a default, then uploads the file to it. `filename` is optional |
| Create subitem  | `create_subitem`                                              | `id`, `sub_items.name`   | Only the subitem’s name can be written                                                                                                      |

### What are the most common monday.com integration use cases?

#### Use case 1: Synchronizing monday.com boards with ITSM and DevOps platforms

ZigiOps syncs items on monday.com boards, such as tasks, bugs, and epics, with records in another system. Status, priority, and type columns are mapped as select lists using each board’s own labels, so values stay consistent on both sides.

#### Use case 2: Polling for new and changed items

ZigiOps filters items by `created_at` and `updated_at` to pick up only new or changed items on each run. All time fields are converted to epoch for reliable comparisons.

#### Use case 3: Keeping comments, files, and subitems in sync

ZigiOps reads and adds item comments, reads and uploads files (including binary content), and reads and creates subitems. Collaboration context moves with the work item, not just the core fields.

#### Use case 4: Tracking who changed an item

When a board has a “Last updated” column, ZigiOps exposes who last changed an item through `updated_by_id` and `updated_by_name`. For writes made by ZigiOps, it shows the API-token user.

### What integration templates are available for monday.com?

ZigiOps supports monday.com integrations with prebuilt and custom integration templates, depending on the target system and use case.

#### Related Templates

For detailed information about available templates for monday.com integrations, please contact:

**Email:** <support@zigiwave.com>

### monday.com integration FAQ

<details>

<summary>How does ZigiOps authenticate to monday.com?</summary>

ZigiOps uses a monday.com personal API token, sent as is in the `Authorization` header without a `Bearer` prefix.

</details>

<details>

<summary>Why does ZigiOps show one collection per monday.com board?</summary>

monday.com has no built-in item types, and each board has its own columns. One collection per board exposes each board’s columns as real, readable fields.

</details>

<details>

<summary>Can ZigiOps sync monday.com comments, files, and subitems?</summary>

Yes. ZigiOps reads and creates comments, attachments (including binary content), and subitems. Uploaded files are attached to a short carrier comment.

</details>

<details>

<summary>What happens when a new status label is added to a board?</summary>

Refresh the schema in ZigiOps. Status columns are select lists built from the column’s current labels, so a new label can only be written after the refresh.

</details>

### Summary

The monday.com integration in ZigiOps provides:

* Secure, agentless, no-code integration with monday.com through the GraphQL API v2
* Personal API token authentication
* Automatic discovery of one collection per board, with board columns as readable fields
* Read and write support for items, descriptions, comments, attachments, and subitems
* Lookups for boards, columns, groups, and users
* Flexible proxy support


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zigiwave.com/available-systems/monday.com.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
