# Monday.com

![Logo-monday.com-2.png](https://assets.relyanceuat.xyz/images/docs/18374733948941/18374738886029.png)
Monday.com is an online SaaS digital tool that helps teams get organized and work together smoothly. It offers customizable boards, automation, and collaboration features, streamlining team communication and project tracking.

In order to integrate Monday.com with Relyance AI you will need a **Client ID**, **Client Secret**, and to follow an OAuth2 flow.

#### In Monday.com:

1. Login to your Monday.com account.
2. From the top-right profile menu, select **Developers**.
3. Ensure you're on the **My apps** tab in the left-hand navigation menu.
4. Click the **Build App** button.
5. In the basic Information section fill out the form with: **Name**: Provide a meaningful name (e.g. Relyance Scan) **Short Description (optional)**: Provide a description
6. Copy the **Client ID** and **Client Secret** to be used in Relyance.
7. Click **Save App** at the bottom of the page.
8. In the left-hand navigation menu, select **OAuth**.
9. In the **Scopes** tab click the following *OAuth Scopes*:
    - me:read
    - boards:read
    - users:read
    - updates:read
10. Click **Save Feature** at the bottom of the page.
11. Click the **Redirect URLs** tab at the top of the OAuth page.
12. Enter [https://root.relyance.ai/api/oauth2](https://root.relyance.ai/api/oauth2) in the **Redirect URLs** input box.
13. Click **Save Feature** at the bottom of the page.

![Monday-4.png](https://assets.relyanceuat.xyz/images/docs/18374733948941/18628770806413.png)

![Monday-5.png](https://assets.relyanceuat.xyz/images/docs/18374733948941/18628754640013.png)

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Click on the **Vendor Integration** tab.
5. Find the **Monday.com** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Oauth2 / App Token**.
8. Paste the **Client ID** and **Client Secret** into their respective fields.
9. Click **Authenticate**.
10. This will bring you to the Monday.com site to authorize Relyance. You may be asked to sign in.
11. Click **Authorize**.
12. At this point, you should see the following result on the **Vendor** integrations page:

![Monday-2.png](https://assets.relyanceuat.xyz/images/docs/18374733948941/18629227321741.png)

![Monday-6.png](https://assets.relyanceuat.xyz/images/docs/18374733948941/18629287648909.png)

![Monday-1.png](https://assets.relyanceuat.xyz/images/docs/18374733948941/18374738894989.png)

13. Congratulations, you are now connected to **Monday.com**.

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
2. **A credential rotated at the vendor is not picked up here.** **API Key** and **Secret** are stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

<!-- failure-modes:end -->

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Monday Custom** | `API Key` (secret) | — |
| **Oauth2 / App Token** | `Client ID`, `Secret` (secret) | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

### API key

```hcl
resource "relyance_integration_connection" "monday_0" {
  vendor = "monday"
  name   = "<your connection name>"

  auth = {
    method = "api-key"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_key = var.monday_api_key
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

### OAuth (browser authorization)

The **OAuth (browser authorization)** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example monday/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

<!-- terraform-examples:end -->