> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/connectivity/connectors/connect-monday.com-for-auto-updates.md).

# Connect Monday.com for auto-updates

The Monday.com connector lets a Key Result or Initiative update itself from a board — items done by status, sums or averages of a number column, items by group or person. The setup flow (Update mode › Set up auto update, then a short chat) is the same for every connector and is described in [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md). This article covers only what is specific to Monday.com.

## Before you connect Monday.com

* A Rhythms Admin has enabled **Monday.com** under **Settings › Workspace › Connectors**.
* **Your Monday.com administrator has installed the monday MCP app** (one-time for the account). Send them this link: [Install the monday MCP app](https://auth.monday.com/marketplace/listing/10000806/monday-mcp). The admin signs in, reviews the permissions (read boards, items and workspaces) and clicks **Install**. Until the app is installed, individual sign-ins fail.
* You have a Monday.com account with access to the boards you want to track.

## How Monday.com authentication works

Rhythms connects to Monday.com's MCP server with OAuth. Open **My connectors**, find **Monday.com**, click **Connect**, sign in and approve. Rhythms registers itself with Monday.com automatically — no keys to paste. Each person connects their own account, unless an admin has shared a connection with you.

## What you can track from Monday.com

* Item completion by a status column — items in a done-type status divided by all items
* Number column values — sums or averages, for example a Budget or Progress column
* Timeline progress
* Items filtered by group, status or assigned person

Give Rhythms the board name or URL, and the workspace if you have several. Status labels are specific to each board, so tell Rhythms which statuses should count as done ("Done and Shipped, not Working on it").

## Limits

* One board per connection.
* Text and date columns are not measured; use a status or number column.
* Rhythms never creates or changes items.

## Example prompts

* "Track the percentage of items with status Done on the Product Roadmap board."
* "Sum the Deal Value column for items in the Closed group of the Sales Pipeline board."

## Related articles

* [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md)
* [Enable Connectors for Your Workspace](/connectivity/manage-connectors-for-your-workspace.md)
* [Shared Connectors](/connectivity/share-a-connector-with-your-team.md)
* [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md)


---

# 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 dynamically by asking a question.

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

```
GET https://help.rhythms.ai/connectivity/connectors/connect-monday.com-for-auto-updates.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 `build a script that syncs our docs to a CMS` 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.