Hello, I've left the n within the key.

When utilizing a service account with our standard Google nodes, I input the following: -----BEGIN PRIVATE KEY----- [REDACTED] -----END PRIVATE KEY-...

Hello, One potential reason for this issue might be that many local LLMs aren't sophisticated enough to recognize when they need to invoke a tool an...

This is a known issue with the MCP community node; it is expected to be resolved in the upcoming release. More details about the issue can be found he...

Hey It seems the service you're interacting with isn't responding correctly. Are you utilizing Axios directly within a code node, or are you using o...

We are aware of this and will be investigating it. Thank you for the report.

Hello, Not yet, I've experimented with a straightforward workflow on version 1.68 using the example below, and it appears to be functioning. Could...

It appears so. I'll test it this morning to see if I can replicate the issue.

Hello, That's quite unusual. Could you share a screenshot of the error message? It doesn't appear to originate from the execute workflow node, so th...

Hello, Which tool is displaying the error?

Hey, There isn’t at the moment, but that sounds like it would make a great feature request. I am going to move this to the feature request categor...

Hello, I've just looked into this. The Loop node can indeed be challenging at times. In this scenario, the reset option is necessary to signal to th...

Hey, Selecting the right tool can sometimes be challenging. The model you're employing needs to be intelligent enough to recognize when to utilize a...

Hello, We are aware of this issue and are working on a fix. You can track the progress via the issue linked below. github.com/n8n-io/n8n ...

This is next in my queue to address.