"URI malformed" error with Google Calendar node?

Questions
1

Describe the problem/error/question

Hi! Long-time fan of n8n. Got about a dozen workflows on my self-hosted instance.

I just tried to set up the Google Calendar node, but whenever I try to interface with it I get a URI malformed error.

I’ve successfully connected and used the Google Sheets and Google Drive nodes with the same API key and account that I’m using for Calendar, And my API key has the permissions for Google Calendar that I need for this node.

Trying to figure out why this would be.

Wondering if it’s because of the @gtempaccount.com domain that my account is currently using (IT team is in the middle of a migration to Google Workspaces). But I’m not having the same problem when interfacing with Google Drive or Google Sheets, even with that same account.

Anyone have advice?

What is the error message (if any)?

Here’s the error and the traceback:

{
  "errorMessage": "URI malformed",
  "errorDetails": {},
  "n8nDetails": {
    "n8nVersion": "1.67.1 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "URIError: URI malformed",
      "    at decodeURIComponent (<anonymous>)",
      "    at encodeURIComponentOnce (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GenericFunctions.js:53:31)",
      "    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GoogleCalendar.node.js:154:90)",
      "    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:722:42)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:704:66",
      "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1134:20"
    ]
  }
}

Please share your workflow

Information on your n8n setup

  • n8nVersion: 1.67.1
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.18.0
  • database: postgres
  • executionMode: regular
  • license: community
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3
  • n8n version: 1.67.1
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): regular (I think?)
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker on Railway
  • Operating system: Whatever the official n8nio/n8n docker image is. Ubuntu?
4

Hi @theJoshMuller

Thanks for posting here and welcome to the community! :partying_face:

The problem most likely is that your calendar has a % in its name and that’s being encoded and causing the malformation in the end. We should be fixing that on our end!

Until then, can you try if it works with selecting the calendar by ID?

5

Hi @ria ! Thanks for your reply and the warm welcome!

My org has now finished their migration, so I’m back to a calendar format that doesn’t have a % in it.

Now that I’ve switched to a normal email structure, my n8n Calendar node seems to be working well! So, I’m thinking that you’re right about the issue with the %.

Thanks again!

2 Likes
6

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