Issues / #81
Build Monday.com connector (read mode)
proposed
feature
Priority: high
Project: nimsforest2
Reporter: cederik
26 Mar 2026 16:13
Description
## Context
Required for the Growth Engine Sprint offer. Monday.com is a common CRM/project management tool in the SME segment.
## Requirements
- Read-only connector to Monday.com API (GraphQL API v2)
- Extract: boards, items, columns, status updates
- For CRM use case: leads, contacts, deal stages, custom fields
- Privacy controls: deterministic extraction — configure which boards/columns come in
- PII handling: must support field-level exclusion (important for healthcare/sensitive industries)
- Data flows into NimsForest as a River source
## First customer: Salix
- Uses Monday.com as CRM
- Tracks leads through stages: new → hot → cold → unqualified → closed
- Contains client names and contact details — MUST support PII exclusion
- Current funnel: 4 new, 17 hot, 74 cold, 175 unqualified, 17 closed
## Architecture
Follows NimsForest data flow: Source → River → Tree → Wind
- Monday.com GraphQL API as Source
- River carries board/item data
- Tree transforms into organisational context (lead counts, conversion rates, pipeline health)
- Wind publishes to nims (Nudge for marketing insights, Nectar for sales coordination)
Required for the Growth Engine Sprint offer. Monday.com is a common CRM/project management tool in the SME segment.
## Requirements
- Read-only connector to Monday.com API (GraphQL API v2)
- Extract: boards, items, columns, status updates
- For CRM use case: leads, contacts, deal stages, custom fields
- Privacy controls: deterministic extraction — configure which boards/columns come in
- PII handling: must support field-level exclusion (important for healthcare/sensitive industries)
- Data flows into NimsForest as a River source
## First customer: Salix
- Uses Monday.com as CRM
- Tracks leads through stages: new → hot → cold → unqualified → closed
- Contains client names and contact details — MUST support PII exclusion
- Current funnel: 4 new, 17 hot, 74 cold, 175 unqualified, 17 closed
## Architecture
Follows NimsForest data flow: Source → River → Tree → Wind
- Monday.com GraphQL API as Source
- River carries board/item data
- Tree transforms into organisational context (lead counts, conversion rates, pipeline health)
- Wind publishes to nims (Nudge for marketing insights, Nectar for sales coordination)
Comments (1)
nebula
26 Mar 2026 16:16
Grooming: set priority to high
Nebula's reasoning: Required for the Salix POC (#78) — Monday.com is their CRM. This connector carries the most PII risk of the three (client names and contact details for mental health patients), so the field-level exclusion design is non-negotiable. The GraphQL API v2 approach is well-scoped.
Nebula's reasoning: Required for the Salix POC (#78) — Monday.com is their CRM. This connector carries the most PII risk of the three (client names and contact details for mental health patients), so the field-level exclusion design is non-negotiable. The GraphQL API v2 approach is well-scoped.