> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/monday-integration-setup.md).

# monday.com Integration Setup

### Getting Started

Use this guide to connect monday.com to your BalkanID tenant. You will need an API token from monday.com and access to the Integrations section in BalkanID.

#### Requirements:

Before you begin, collect the following value from monday.com:

* **API Token**

{% hint style="info" %}
The API token inherits the permissions of the person who generated it, so it must be created by a monday.com **account admin**. A token created by a member returns only the users and teams that person can already see, and monday.com reports no error in that case.
{% endhint %}

### Configure monday.com within your BalkanID tenant

1. To find the API Token, sign in to monday.com as an account admin.
2. Click your profile picture, then navigate to **Administration** > **Connections** > **Personal API token**. Any user can also reach their own token from the profile picture under **Developers** > **API token**.
3. Copy the token that is displayed. monday.com shows the token only in this screen, so copy it before you navigate away.
4. In BalkanID, go to **Integrations** and click **Add integration**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FBArEtXhVcP4zqPlGCC1J%2Fmonday-add-integration.png?alt=media" alt="The BalkanID Integrations page with the Add integration button in the top right"><figcaption><p>Integrations</p></figcaption></figure></div>

5. Search for **monday.com**, select it, and click **Next**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fb2I2cX5vpzgRCepUldYV%2Fmonday-connect-application.png?alt=media" alt="The Connect a new application step with monday.com selected"><figcaption><p>Connect a new application</p></figcaption></figure></div>

6. Set the **Primary application owner**, and a **Description** and **Secondary application owner(s)** if you need them. Under **Select Extraction Type**, keep **Direct Configuration** and paste your token into **API Token**.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FnI8RmJ2P8Wbi9Uui7heA%2Fmonday-direct-configuration.png?alt=media" alt="The Direct Configuration section showing the API Token field"><figcaption><p>Direct Configuration</p></figcaption></figure></div>

7. Click Next to move onto Optional Configuration.
8. Fill **Optional Configuration**, if required.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FZbipc8nl8LTFl5YsVIaj%2Foptional-configuration.png?alt=media" alt="The Optional Configuration step"><figcaption><p>Optional Configuration</p></figcaption></figure></div>

9. Once you have filled in the information, click **Save**. Your integration is now configured and you will see the status of the integration displayed alongside other integrations on the Integrations page. When data is available, the integration Status column will read **Connected** and the integration Message will read **Data available**.

### What BalkanID extracts

| Type              | Description                                                                                                                                 |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Users**         | Every user in the monday.com account, including deactivated and pending users, with their status, kind, department, job title and location. |
| **Teams**         | The account's teams, and each user's membership of them. Team owners are recorded as owners rather than members.                            |
| **Account roles** | The account's roles, including any custom roles your plan allows, and the role each user holds.                                             |

### Integration Scopes

A monday.com API token carries the permissions of the account admin who created it; there are no scopes to enable separately. BalkanID reads only the following areas of the monday.com API.

| Read Only Scopes                                                    | Lifecycle Management Scopes |
| ------------------------------------------------------------------- | --------------------------- |
| **Users (Read)** — account users and their profile, status and role | N/A                         |
| **Teams (Read)** — teams and their members and owners               | N/A                         |
| **Account (Read)** — the account's roles                            | N/A                         |


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/monday-integration-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.