The Monday.com integration captures activity from your boards: items, updates (comments), column value changes, and subitems. Combined with GitHub, Linear, and Claude Code data, this gives Cogniscape a complete picture of what your team is working on, who is involved, and how work progresses from idea to delivery. This setup needs to be done once per board you want to observe. If you add new boards later, just repeat the process for each one. Only a board owner or workspace admin can add integrations to a board.Documentation Index
Fetch the complete documentation index at: https://docs.cogniscape.app/llms.txt
Use this file to discover all available pages before exploring further.
Configure the webhook
Open the board you want to track
In Monday.com, open the board and click the Integrate button in the top-right corner.
Add a webhook recipe
In the Integrations Center, search for Webhooks and pick a recipe such as When an item is created, send a webhook. Monday.com offers one recipe per trigger type — add one recipe per event you want to capture.
Paste the Webhook URL
Use the following URL, replacing
<your-customer-key> with the key from the Customer Portal:Select the triggers to track
For the richest insights, add a webhook recipe for each of these triggers:
- When an item is created
- When an item’s name changes
- When a column value changes (covers status, person, date, and any custom columns)
- When an update is posted (comments on items)
- When a subitem is created
- When an item is moved to a group
Save the recipe
On save, Monday.com sends a
challenge request to the Webhook URL. Cogniscape responds with the matching challenge token automatically — no manual confirmation is required. If Monday rejects the recipe with a verification error, double-check the URL and customer key and try again.Once the handshake succeeds, events start flowing into your knowledge graph immediately.How requests are verified
Board webhook recipes do not use a signing secret. Monday.com authorizes the endpoint once at creation time via a challenge/response handshake:- Monday sends
POSTwith{ "challenge": "<token>" }to the Webhook URL. - Cogniscape replies with the same
{ "challenge": "<token>" }payload. - Monday saves the recipe and starts delivering events.
Programmatic webhooks created via the Monday GraphQL
create_webhook mutation under an integration app token include a JWT in the Authorization header. Cogniscape verifies that JWT when present, but the standard board-recipe path covered above does not produce one.Verify the webhook
After saving, trigger a test by creating or updating an item on the board. Monday surfaces failed deliveries in the recipe’s Activity log; a200 response from Cogniscape confirms the event was received.
Supported events
Cogniscape processes these Monday.com webhook event types:| Event | What it captures |
|---|---|
create_item | New item created — name, board, group, and creator |
change_name | Item name changes — previous and new value |
change_column_value | Column updates — status, person, date, text, numbers, and custom columns |
change_status_column_value | Status column transitions — previous and new label |
create_update | Comments posted on items — body text and author |
create_subitem | Subitem creation — parent item, name, and creator |
item_moved_to_any_group | Item moved between groups — source and destination group |
item_archived / item_deleted | Lifecycle terminal states for items |
Events not listed above are received but silently ignored. Enabling additional triggers is safe — it won’t create noise in your knowledge graph.