Monday.com Integrations - GraphQL requests

Questions
1

Hi all,

Since last night around 8pm AEST (31/7), multiple Make scenarios using the Monday.com integration have started failing with the following error:

css

CopyEdit

[400] [{"message":"Invalid GraphQL request","extensions":{"code":"INVALID_GRAPHQL_REQUEST","details":"Request body must be a JSON with query."}}]

This is occurring across previously functional modules, including:

  • “Get an Item’s Column Value”

  • “Search items in board by column values (advanced)”

  • Others like “Get Item” and “Update Column Value”

There have been no changes to our scenarios — this appears to be caused by a breaking change in how Make.com structures its GraphQL requests to Monday.

It seems the modules are now sending invalid/malformed GraphQL — either missing the query field entirely or failing to format the body correctly — which results in Monday rejecting the call.

I’ve submitted a ticket but have not received a response.

It’s affecting production workflows- anyone else having a similar issue?

2 Likes
3

I’m having the same error. I’m mainly using the list group’s items, and it’s worked perfectly fine until yesterday.

1 Like
4

Same issue with me. Happening now in two scenarios with Monday modules.

Working fine when I last used them late last night. Broken a few hours later (early this morning) and continues to be so.

Seems this is a Make issue.

I’ve yet to hear back from support.

UPDATE: It happens in every scenario I run, including totally new scenarios that have Monday modules.

1 Like
5

from what tests I’ve run its unlikely a Make issue, it’s a monday.com issue with their (AU servers specifically)

They usually wait for their Israel team to come online before they patch any fixes, so I’d suggest raising complaints with them (monday.com) regarding their support around supporting our side of the world.

This isn’t the first time that’s happened when the AU servers specifically has issues, and we just have to wait around doing nothing till they fix it. They don’t report it on their status page as well which is a major gripe of mine

1 Like
7

Thanks for this info.
In light of this, I’ve now also reported it to Monday.com tech support.

Here’s hoping it’s resolved promptly.

8

The response from Make support, as of 1 hour ago:

We are aware of the issue, and this has been reported to the relevant team with the highest priority.

Hopefully it’s resolved soon.

I also took it up with Monday. Haven’t heard back from them yet.

1 Like
9

Hello everyone @here

I just wanted to let you know that we’re aware of this issue and that we’ve reported it to our development team. They’re currently investigating the root cause and will work on a fix as soon as it’s identified. We’ll keep you updated as soon as we have any news to share.

We sincerely apologize for any disruption or frustration this may be causing.

Thank you very much for your patience and understanding. :folded_hands:

3 Likes
10

Where can we subscribe to receiving updates on this issue?

11

I raised a support ticket and they’ve advised me it’s resolved. Testing on my side since Saturday morning i’ve had no issues.

2 Likes
12

Hello everyone @here

I’m just stepping in to confirm that the dev team has deployed a fix to the issue, and everything should be up and running again.

Please feel free to test on your end and let us know if you spot anything unusual.

Once again, we sincerely apologize for the disruption and thank you for your patience while we worked to resolve this. :folded_hands:

1 Like
13

@Michaela I have dozens of Make scenarios that make calls to monday.com that were working fine until last night. I am now receiving the error described in this thread in multiple scenarios when making an arbitratrary query to the Monday API. I have tested the exact same queries in Monday’s API playground and the queries do not produce any errors there. I am inclined to think the problem still lies with make.com. Thank you.

image
image450×861 57.1 KB

14

@Michaela I’m getting the same error as @Eric_Bashkoff when using the GraphQL Query module. We also have dozens of scenarios and all are returning errors.

We tried switching between all available API versions, but the error wasn’t solved. When using version 2024-10 the error changed to The operation failed with an error. [400] [{“message”:“Syntax Error: Expected Name, found .”,“locations”:[{“line”:1,“column”:8}],“extensions”:{“code”:“PARSING_ERROR”}}]

These scenarios have been active for months with no errors and no changes, so this seems to be something on your end.

15

Hi,

I also have the same issue as @Lalo_De_Alva, also on scenarios that have been working for months without issue.

Opened a support ticket.

16

Hi! For anyone still having this issue, I spoke with support and the solution was to switch the method from GET to POST.

3 Likes
17

@Michaela could you mark this as the actual answer?

18

Hello @Hunor, thank you so much for stepping in and sharing the insights you got from the support team with the rest of the community. We truly appreciate it.

I’ve marked your reply as the solution. Thanks again :folded_hands: