Monday.com
Collect Monday.com board, item, update, and user evidence through the Monday.com GraphQL API. Use only for change, incident, access-request, or approval evidence.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Board inventory for evidence scope
- Recent item and update evidence for configured boards
- User inventory for access-review context
Endpoints this template queries
The exact Monday.com API endpoints called once connected. All read-only GET requests unless noted.
- POST/
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://api.monday.com/v2)
- Endpoints (JSON)(prefilled: [ { "id": "boards-items-users", "name": "Boards, items, updates, and users", "path": "/", "method": "POST", "body": { "query": "query { boards(limit: 25) { id name state updated_at items_page(limit: 25) { items { id name state updated_at updates(limit: 10) { id text_body created_at creator { id name } } } } } users(limit: 50) { id name email enabled is_admin } }" }, "assertions": [ { "path": "data.boards", "op": "exists" } ] } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Monday.com evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Monday.com evidence
Get a guided demo, or start by scanning any domain for free.