Anyone else: 400 INVALID_GRAPHQL_REQUEST error from API with MAKE Monday modules

Platform discussions monday apps & integrations
, ,
1

Is anyone else (mostly like with Monday housed in AU data centre) having issues with Monday.com modules on Make.com scenarios, starting around 9PM AEST / 11PM NZT?

The issue is that all Monday modules that try to request data from Monday get the following response from the Monday API:

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

It’s been reported by three other people on the AU Monday data centre, plus me that makes four known reports.

The reports I’ve seen are here: Monday.com Integrations - GraphQL requests - Features - Make Community

One of the reporters pointed out it’s more likely an issue with Monday than with Make. Hence my brining it up here.

5 Likes
2

Same issue here. The API changelog shows a new version release on 1 August 2025, shows no breaking changes

2 Likes
3

Same here. Got a ton of errors on scenarios that were previously working without issue.

2 Likes
4

It seems that the issue is now resolved.

5

Hi!

The 400 INVALID_GRAPHQL_REQUEST error usually means there’s something wrong with the structure or content of the GraphQL request being sent to the Monday API via MAKE (formerly Integromat). Here are some things to check that might help resolve it:

  1. Validate Your Query/Mutation: Ensure your GraphQL query or mutation syntax is correct and matches the Monday API schema. Even a small typo or missing field can cause this error.
  2. Check Required Fields: Make sure all required fields and variables are included and properly formatted.
  3. API Version and Permissions: Verify that you’re using the correct API version and that your API token has the necessary permissions for the requested operation.
  4. Test Outside MAKE: Try running the same GraphQL query directly in Monday’s API playground or a tool like GraphiQL to isolate whether the issue is in the request or MAKE’s module setup.
  5. Module Configuration: Double-check your MAKE Monday module setup, especially the input parameters and headers.

If you can share the exact query or a screenshot of your module setup, the community can help troubleshoot more precisely!

6

I just ran into the same problem! This happens when you use a monday.com module in make.com where you can specify an arbitrary GraphQL request. The make.com people did implement a fix, but the fix only works if you explicitly specify that you are making the call to the 2024-10 version of the monday.com API. If you try to set it to the current version, it still fails. Once I made that change, Make’s fix worked for me. Hope that helps someone!

8

We are also facing this issue as of August 4th. This only happens on cursor paginated requests as describe here i.e. that the board queries are fine but the next_items_page requests are failing with the following message:

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

We are using version 2024-10 of the API. Changing the request from a GET to a POST as described on the Make community post did not solve the issue for us. Were there other potential solutions or somewhere we can track this issue?

1 Like
9

After some trial and error, we have found that this scenario only occurs when passing the GraphQL query as a query param. Through a JSON body, the request is working fine.

2 Likes
10

Thanks for your work to resolve this! What is the usual timeframe for an updated version of the connector to be published as a Python package (PyPI)?

11

We’re running into this too. Something definitely changed under the hood. We’ve had some api calls / queries in place for months that just stopped working. After we switched back to API-Version 2024-10 everything starts to work again.

Anyone at monday able to comment on this?

1 Like