Monday

Monday.com is a comprehensive work operating system that enables teams to plan, organize, and track work through customizable boards, workflows, and automation tools, providing visual project management and collaboration capabilities for enhanced productivity.

Power end-to-end data operations for your Monday API with Nexla. Our bi-directional Monday connector is purpose-built for Monday, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Monday or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Monday workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Monday credential, you need to obtain your API token from your Monday.com account. Monday.com uses token-based authentication for all API requests, with the API token sent in the Authorization header.

To obtain your Monday.com API token, follow these steps:

1. Sign in to your Monday.com account using your administrator credentials.

2. Click on your profile picture or avatar in the top right corner of the Monday.com interface.

3. Select Admin from the dropdown menu to access the admin settings.

4. In the admin settings, navigate to API or Developers section in the left menu.

5. If you don't have an API token yet, look for the API Token or Token section and click Generate Token or Create Token to create a new API token.

6. Alternatively, if you're using Monday.com's V2 API, you can access your API tokens through the Developers section. The method for accessing API tokens may vary depending on your user level and Monday.com plan.

7. Copy the API token immediately after it's generated, as it may not be accessible again after you navigate away from the page.

8. Store the API token securely, as you will need it to configure your Nexla credential. The API token provides access to your Monday.com account data and should be treated as sensitive information.

The API token is sent in the Authorization header for all API requests to the Monday.com GraphQL API. The token authenticates your requests and grants access to Monday.com resources based on your account permissions. If your API token is compromised, you should immediately revoke it in your Monday.com account settings and generate a new one. For detailed information about obtaining API tokens, API authentication, and available GraphQL queries, refer to the Monday.com API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Token	No	Yes	Your Monday.com V2 API tokens. To access your API tokens, you can use one of two methods depending on your user level. Check https://api.developer.monday.com/docs/authentication for details.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Monday

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Monday.com uses token-based authentication for all API requests. Enter your Monday.com API token in the API Token field. This is the API token you obtained from your Monday.com account settings (Admin > API or Developers section) in Prerequisites. The API token is sent in the Authorization header for all API requests to the Monday.com GraphQL API and must be kept confidential.

   Your Monday.com API token can be found in your Monday.com account settings under the Admin > API or Developers section. The method for accessing API tokens may vary depending on your user level and Monday.com plan. The API token is sent in the Authorization header for all API requests to the Monday.com GraphQL API.

   If your API token is compromised, you should immediately revoke it in your Monday.com account settings and generate a new one. The API token provides access to your Monday.com account data and should be treated as sensitive information. Keep your API token secure and do not share it publicly.

   For detailed information about obtaining API tokens, API authentication, and available GraphQL queries, see the Monday.com API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Monday.com connector tile, then select the credential that will be used to connect to your Monday.com account, and click Next; or, create a new Monday.com credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to execute common Monday.com GraphQL queries. Each template is designed specifically for the corresponding Monday.com query type, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Query One Page of Data

This endpoint template executes a GraphQL query that fetches a single page of data from your Monday.com account. Use this template when you need to retrieve a fixed set of data that doesn't require pagination, such as user information, board metadata, or item details for specific IDs.

• Enter your GraphQL query in the Query field. This should be a valid Monday.com GraphQL query that retrieves the data you need. The query should follow Monday.com GraphQL syntax and reference the appropriate Monday.com schema fields. For example, to retrieve user information, use: query { me { is_guest created_at name id }}. The query is sent as a POST request to the Monday.com GraphQL endpoint (https://api.monday.com/v2) with the query in the request body.
• Enter the JSONPath expression in the JSONPath to Data in Response field to specify which part of the API response should be treated as the relevant data by Nexla. This JSONPath expression should point to the data in the GraphQL response. For example, if your query returns user information, use $ to extract the entire response, or $.data.me to extract the user object from the response. The JSONPath expression determines which data will be extracted and processed by Nexla.

This template is designed for queries that return a single page of results. If your query returns paginated data, use the "Query Paginated Data" template instead. The GraphQL query must be valid according to the Monday.com GraphQL schema. You can reference the Monday.com API reference for available queries and schema information.

The JSONPath expression must correctly reference the structure of your GraphQL response. GraphQL responses typically have a data property containing the query results. Ensure your JSONPath expression matches the structure returned by your specific query.

Query Paginated Data

This endpoint template executes a GraphQL query that fetches multiple pages of data from your Monday.com account using cursor-based pagination. Use this template when you need to retrieve large datasets that span multiple pages, such as all items in a board, all boards, or all users. The template automatically handles pagination by using cursor-based pagination with the next_items_page query.

• Enter your GraphQL query in the Query field. This should be a valid Monday.com GraphQL query that includes pagination using the next_items_page query. The query must include a cursor variable that will be used for pagination. For example, to retrieve paginated items from a board, use: query { boards (ids: 7764629372) { items_page(limit:1) {cursor items {id name}} } }. The query is sent as a POST request to the Monday.com GraphQL endpoint (https://api.monday.com/v2) with the query in the request body.
• Enter the JSONPath expression in the JSONPath to Data in Response field to specify which part of the API response should be treated as the relevant data by Nexla. This JSONPath expression should point to the data in the GraphQL response. For example, if your query returns boards, use $.data.boards[*] to extract all board items from the response. The JSONPath expression determines which data will be extracted and processed by Nexla for each page.
• Enter the variable name for the cursor in the Query Variable for Page Number field. This should match the variable name used in your GraphQL query for pagination (typically cursor). Nexla will automatically use the cursor from the previous response to fetch subsequent pages of data.
• Enter the starting page number in the Start from Page Number field. This is the initial page number that Nexla will use when fetching data. Typically, this should be set to 1 to start from the first page. Note that Monday.com uses cursor-based pagination, so this value is used for the initial query, and subsequent pages use cursors from the API response.

This template automatically handles pagination using cursor-based pagination with the next_items_page query. The template uses a two-step approach: the first step executes your initial query, and the second step uses the next_items_page query with the cursor from the previous response to fetch subsequent pages. Ensure your GraphQL query includes pagination support using Monday.com's cursor-based pagination mechanism.

The GraphQL query must be valid according to the Monday.com GraphQL schema and must include cursor-based pagination. You can reference the Monday.com API reference for available queries and schema information. The JSONPath expression must correctly reference the structure of your GraphQL response, typically pointing to the data within the data property.

Consider your API rate limits when configuring pagination. Monday.com enforces rate limits on API requests, so ensure your pagination settings align with your account's rate limit capabilities.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Monday.com data sources can also be manually configured to execute custom GraphQL queries not covered by pre-built templates. Because Monday.com's API is entirely GraphQL-based, all requests are sent as HTTP POST requests to the single endpoint https://api.monday.com/v2, with the query provided in the request body as {"query": "{ your_graphql_query }"} (or with an added variables property for queries that use variables). Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Monday.com GraphQL responses nest data under the data property—for example, use $.data.me for a user query or $.data.boards[*] for a boards query. Monday.com uses cursor-based pagination via the next_items_page query; configure the Path to Data in Response field to match your query's response structure, and set up pagination using the cursor value returned in the response.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Monday.com data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.