GraphQL Node Suddenly Returning Errors for Monday.com Queries

Questions
,
1

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:

“Invalid GraphQL query”

The strange part is that these exact same queries still work perfectly in Monday.com’s developer playground and other third-party tools. That leads us to believe this may be an issue with how n8n’s GraphQL node is processing or sending the query.

Has anyone else experienced something similar?
Are there any recent changes to the GraphQL node that we should be aware of?

4 Likes
2

Having the same issue!

3

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

4

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!

5

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;
			}
1 Like
6

Same here!

7

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

8

Maybe if we give this some votes:

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.