Hi Community, We’ve been using the GraphQL node in n8n to integrate with Monday.com and execute custom GraphQL queries as part of our client automation workflows. This setup has been running smoothly for quite a while, but over the past 2–3 days, we’ve started receiving the following error: “Inval…

I am having the same issue. However, you can use the HTTP node instead and get it to work. Take your graphQL query and variables and convert it to a cURL so you can import it directly into an HTTP node. It works for me!

Looks like the issue with the operationName GraphQL Errors: [ { message: ‘Invalid GraphQL request’, extensions: { code: ‘INVALID_GRAPHQL_REQUEST’, details: ‘operationName: must be a string’ } } ] and n8n is doing if (jsonBody.operationName === '') { jsonBody.operationName = null; …

Still an ongoing issue, even after redeploying the server and updating the instance. Does anybody have an update on this?

Maybe if we give this some votes: [image] Null operationName API request break Feature requests bug Description The Monday API broke yesterday (Aug 6th) by no lo…

GraphQL Node Suddenly Returning Errors for Monday.com Queries

Questions

ben8n August 5, 2025, 8:17am 3

I’m having the same issue, worked liked a charm and suddenly stopped working !

GraphQL Node Does Not Work Properly

Topic		Replies	Views
GraphQL Node Does Not Work Properly Questions graphql	2	185	September 17, 2025
Issues with HTTP and GraphQL Node Errors Questions node	2	162	August 18, 2025
Error on graphql query Questions	4	302	October 16, 2024
Unexpected error in graph ql node Questions	1	83	April 26, 2025
Unexpected Cannot read properties of undefined (reading 'error') while using a GraphQL node Questions	2	76	September 23, 2025

GraphQL Node Suddenly Returning Errors for Monday.com Queries

Related topics