> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Monday as a data source
> Bring data from Monday to Nekt.
Monday is a work operating system that enables organizations to build custom workflow apps in minutes to run their processes, projects, and everyday work. It provides tools for project management, task tracking, and team collaboration with a focus on visual and intuitive workflows.
## Configuring Monday as a Source
In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the Monday option from the list of connectors.
Click **Next** and you'll be prompted to add your access.
### 1. Add account access
You'll need your Monday API Token for this connection. You can find it in your [Monday account settings](https://monday.com/developers/v2/quickstart-view). Once you have it, add the account access and the connector configuration.
The following configurations are available:
* **API token**: The token to authenticate against the API service. It can be generated by clicking on your Profile Picture -> Developers -> API token in your Monday workspace.
* **Board IDs**: Restrict extraction to a specific set of board IDs. When set, only the listed boards and their items are extracted, and boards are returned regardless of state (active, archived, or deleted). Leave empty to extract every active board your token has access to.
Once you're done, click **Next**.
### 2. Select streams
Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you.
> Tip: The stream can be found more easily by typing its name.
Select the streams and click **Next**.
### 3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
* **Layer**: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
* **Folder**: a folder can be created inside the selected layer to group all tables being created from this new data source.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** to all tables at once and make this process faster!
* **Sync Type**: you can choose between INCREMENTAL and FULL\_TABLE.
* Incremental: every time the extraction happens, we'll get only the new data - which is good if, for example, you want to keep every record ever fetched.
* Full table: every time the extraction happens, we'll get the current state of the data - which is good if, for example, you don't want to have deleted data in your catalog.
Once you are done configuring, click **Next**.
### 4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters.
To define your [Trigger](https://docs.nekt.com/runs/scheduling-and-triggers), consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times).
Optionally, you can define some additional settings:
* Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource [here](https://docs.nekt.com/get-started/core-concepts/resource-control).
* Determine when to execute an **Additional [Full Sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#additional-full-sync)**. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click **Next** to finalize the setup.
### 5. Check your new source
You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.
# Streams and Fields
Below you'll find all available data streams from Monday and their corresponding fields:
Stream for managing boards and their configuration.
**Key Fields:**
| Field | Type | Description |
| :----------------- | :------ | :--------------------------------------------------------------- |
| `id` | String | Unique identifier for the board |
| `name` | String | Name of the board |
| `board_folder_id` | String | ID of the folder containing the board |
| `board_kind` | String | Kind of board |
| `permissions` | String | Board permissions |
| `state` | String | Board state (all, active, archived, deleted) |
| `type` | String | Board type (board, sub\_items\_board) |
| `updated_at` | String | Last update timestamp |
| `workspace_id` | String | Workspace identifier |
| `description` | String | Board description |
| `items_count` | Integer | Number of items in the board |
| `items_limit` | Integer | Board items limit |
| `item_terminology` | String | Board item terminology |
| `url` | String | Board URL |
| `columns` | Array | Array of column objects (id, title, description, type, archived) |
| `groups` | Array | Array of group objects (id, title) |
| `owners` | Array | Array of owner objects with id and name |
| `creator` | Object | Creator object with id and name |
| `subscribers` | Array | Array of subscriber objects with id and name |
Stream for managing items (tasks/cards) within boards.
**Key Fields:**
| Field | Type | Description |
| :-------------- | :----- | :--------------------------------------------------------------------------------- |
| `id` | String | Unique identifier for the item |
| `name` | String | Item name |
| `created_at` | String | Creation timestamp |
| `creator_id` | String | Creator's ID |
| `email` | String | Associated email |
| `state` | String | Item state |
| `relative_link` | String | Relative link to the item |
| `updated_at` | String | Last update timestamp |
| `url` | String | Item URL |
| `description` | Object | Description object containing blocks with content and metadata |
| `assets` | Array | Array of asset objects (id, name, file\_extension, url, public\_url, uploaded\_by) |
| `board` | Object | Board object with ID |
| `column_values` | Array | Array of column values (id, column, text, type, value) |
| `group` | Object | Group object with id and title |
| `parent_item` | Object | Parent item reference |
| `subitems` | Array | Array of subitem references |
| `subscribers` | Array | Array of subscriber objects |
Stream for managing user accounts and permissions.
**Key Fields:**
| Field | Type | Description |
| :--------------------- | :------ | :----------------------------------- |
| `id` | String | Unique identifier for the user |
| `name` | String | User's name |
| `email` | String | User's email |
| `url` | String | User's profile URL |
| `birthday` | String | User's birthday |
| `country_code` | String | User's country code |
| `created_at` | String | Account creation timestamp |
| `current_language` | String | User's language preference |
| `join_date` | String | Join date |
| `last_activity` | String | Last activity timestamp |
| `location` | String | User's location |
| `mobile_phone` | String | Mobile phone number |
| `phone` | String | Phone number |
| `title` | String | User's title |
| `time_zone_identifier` | String | Time zone |
| `utc_hours_diff` | Integer | UTC hour difference |
| `enabled` | Boolean | Whether the user is enabled |
| `is_admin` | Boolean | Admin status |
| `is_guest` | Boolean | Guest status |
| `is_pending` | Boolean | Pending status |
| `is_verified` | Boolean | Verification status |
| `is_view_only` | Boolean | View-only status |
| `photo_original` | String | Original photo URL |
| `photo_small` | String | Small photo URL |
| `photo_thumb` | String | Thumbnail photo URL |
| `photo_thumb_small` | String | Small thumbnail URL |
| `photo_tiny` | String | Tiny photo URL |
| `account` | Object | Account information (id, name, slug) |
| `teams` | Array | Array of team memberships (id, name) |
| `custom_field_metas` | Array | Array of custom field definitions |
| `custom_field_values` | Array | Array of custom field values |
## Implementation Notes
* **Board Filtering**: Setting specific IDs in the configuration allows the connector to efficiently extract only those requested boards, circumventing pagination across irrelevant data, and ignoring the board state constraints (it fetches them whether active, archived, or deleted). Leaving the property empty brings in every accessible active board.
* **Pagination**: Extraction mechanisms utilize standard page-number pagination for parent streams (like Boards) and robust cursor-based pagination for child resources (Items) to ensure performance consistency across large sets of data.
## Skills for agents
Monday connector documentation as plain markdown, for use in AI agent contexts.