Maton Monday.com API

Support
1

<@243076783258206208> Hi team, I wanted to request support for monday.com’s create_update API action to be added to the Maton API.
At the moment, I can work with items, but I can’t post an update/comment directly onto an item through Maton. This is a key part of the workflow I’m trying to build, as I need my agent/integration to add notes, progress updates, and interaction history back onto the relevant monday.com item.
The specific action I’m referring to is monday’s create_update mutation, used to post an update to an item.
It would be great if support for this could be added, ideally with the ability to pass:
item_id
body
If possible, support for mentions would also be helpful later, but the main need right now is simply being able to post an update to an item.
This would unlock a much more complete monday.com workflow for me inside Maton. Please let me know if this is already planned, or if there’s any workaround currently available.

2

Thanks for reporting this. Wanted to let you know that we’re looking into this and will provide you an update later.

3

Thank you. Apprecaite the resonse.

4

Just a bit more information about the issue for your reference created by my agent:
This is important for the workflow I’m building, because my agent/integration needs to write back operational notes to the correct monday item as part of normal usage — for example:
progress notes
customer interaction history
follow-up context
handoff/status updates
In monday, these need to be posted as item updates rather than only stored in a column, because updates/comments are the correct activity-thread surface for this kind of context and collaboration.
The specific monday action I’m referring to is the GraphQL mutation:
create_update(item_id, body)
Minimum needed parameters:
item_id
body
Nice to have later:
mention support / mentions_list
If helpful, the current behavior I’m seeing is:
UNAUTHORIZED_FIELD_OR_TYPE on create_update

5

Thanks for letting us know. Could you please delete your connection, re-connect your Monday account, and try again? We modified to expand the permission scopes.

6

<@243076783258206208> Magic!! That worked. Thank you for getting this turn around so quickly. Apprecaite you and the team!

7

<@243076783258206208> , Sorry to be such a pain. Does your current API integration give access to the CRM side of Monday.com. Using the updated API settings I can not reach my CRM board ID

8

No problem. It should full access to your account. Could you provide the API endpoint and payload you’re seeing the error for?

9

Thanks — here are the exact calls showing the mismatch.

Maton endpoint
POST https://gateway.maton.ai/monday/v2

1) Workspace lookup

{
"query": "{ workspaces(ids:[2968583]) { id name kind description } }"
}

Actual via Maton

{ "data": { "workspaces": [] } }

2) Boards scoped to that workspace

{
"query": "{ boards(limit:100, workspace_ids:[2968583]) { id name workspace { id name } } }"
}

Actual via Maton

{ "data": { "boards": [] } }

3) Broad workspace listing via Maton

{
"query": "{ workspaces(limit:50) { id name kind description } }"
}

Only returns:

  • 2959516 — Hercules Projects

Control test: direct monday API
POST https://api.monday.com/v2

Running the same workspace/board queries directly against monday with my monday token returns:

  • workspace 2968583 = Hercules CRM
  • boards in that workspace successfully

So the issue appears specific to the Maton monday path: either workspace/product visibility differs there, or the Maton auth scope is not reaching the CRM workspace objects that the direct monday token can see.

But I would prefer to use Maton API rather than Direct.

10

<@243076783258206208> thanks again

11

That’s strange. Maton connection should have full permission scopes including workspaces.read and boards:read and it routes requests to https://api.monday.com/v2 so it should work the same. DM’ed you for email so I can look into it further. Also, just to confirm, this workspace exists in the monday.com account you used to connect via Maton, correct?