Monday.com Sensor

What it ingests

Work activity from Monday.com — board items and their updates (comments) — optionally scoped to specific boards. Monday Board maps onto Corveil's Project entity (the Jira / Linear project analog). Groups, subitems, files, and docs are not first-class v1 entities.

This is GraphQL poll ingest against https://api.monday.com/v2. Incremental ticks walk board activity_logs since the watermark, then expand the touched items. Asana, ClickUp, and Jira stay separate sensors — this type is Monday.com alone.

Credential

References a monday_api_token credential by id. The secret is a Monday.com personal API token. Monday is a single cloud API, so there is no site URL beside the token.

curl -sS -X POST https://your-corveil-host/api/credentials \
  -H "Authorization: Bearer <admin>" -H "Content-Type: application/json" \
  -d '{"type":"monday_api_token","name":"acme-monday-token","secret":"..."}'

OAuth 2.0 / 3LO and monday app tokens are out of scope in v1.

Config fields

Key	Required	Notes
board_ids	no	Comma-separated Monday.com board IDs, e.g. 1234567890, 9876543210. Blank ingests every board the token can read.

Provider-side setup

1. Sign in as the Monday.com account that should own the token.
2. Open Avatar → Developers → API token (or Administration → Connections → Personal API token) and copy the token.
3. Make sure that account can view the boards you want to ingest.

Wire-up

POST /api/sensors

{
  "sensor_type": "monday",
  "name": "Acme Monday.com",
  "config": {
    "board_ids": "1234567890, 9876543210"
  },
  "credentials": { "api_token": "<monday_api_token credential id>" }
}

Verify

Run Test connection to confirm the token authenticates (me { id }). A bad token fails at save/test, not on the first poll. Once polling, created and updated items on the selected boards appear as task events; updates appear as conversation events.