Problem with create event in google calendar

Hello, I’m just starting with n8n, and I’m having serious issues with the node for creating events in Google Calendar. I can’t get it to create the event on the date I specify. I used the expression {{$fromAI(“start_date”)}}, and although the correct date appeared in the description, it didn’t add the event to the calendar. I tried using the option to define it automatically through the model, but I got a request error. I’ve checked the calendar ID, Google authentication, replaced the node, specified it in the prompt, and I still can’t get past this issue.
Sorry if i miss anything, it´s the first time I post.
Thank to everyone.
Marti

{
“errorMessage”: “Bad request - please check your parameters”,
“errorDetails”: {},
“n8nDetails”: {
“time”: “28/2/2025, 18:28:10”,
“n8nVersion”: “1.79.3 (Cloud)”,
“binaryDataMode”: “filesystem”,
“cause”: {
“message”: “Bad request - please check your parameters”,
“timestamp”: 1740763690018,
“name”: “NodeApiError”,
“description”: “Invalid resource id value.”,
“context”: {},
“cause”: {
“message”: “400 - {"error":{"errors":[{"domain":"global","reason":"invalid","message":"Invalid resource id value."}],"code":400,"message":"Invalid resource id value."}}”,
“name”: “AxiosError”,
“stack”: “AxiosError: Request failed with status code 400\n at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:19:12)\n at Unzip.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:599:11)\n at Unzip.emit (node:events:530:35)\n at endReadableNT (node:internal/streams/readable:1698:12)\n at processTicksAndRejections (node:internal/process/task_queues:82:21)\n at Axios.request (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/Axios.js:45:41)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at invokeAxios (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:173:16)\n at proxyRequestToAxios (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:513:26)\n at Object.request (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:1145:50)\n at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:842:20\n at SupplyDataContext.requestOAuth2 (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:792:12)\n at SupplyDataContext.requestOAuth2 (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:1153:20)\n at SupplyDataContext.googleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GenericFunctions.js:38:16)\n at SupplyDataContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GoogleCalendar.node.js:280:40)\n at handleToolInvocation (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/get-input-connection-data.js:41:44)\n at DynamicStructuredTool.func (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/create-node-as-tool.js:78:35)\n at DynamicStructuredTool.call (/usr/local/lib/node_modules/n8n/node_modules/@langchain/core/dist/tools/index.cjs:113:22)\n at /usr/local/lib/node_modules/n8n/node_modules/langchain/dist/agents/executor.cjs:486:27\n at async Promise.all (index 0)\n at AgentExecutor._call (/usr/local/lib/node_modules/n8n/node_modules/langchain/dist/agents/executor.cjs:478:30)\n at AgentExecutor.invoke (/usr/local/lib/node_modules/n8n/node_modules/langchain/dist/chains/base.cjs:58:28)\n at ExecuteContext.toolsAgentExecute (/usr/local/lib/node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/dist/nodes/agents/Agent/agents/ToolsAgent/execute.js:185:30)\n at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/@n8n/n8n-nodes-langchain/dist/nodes/agents/Agent/Agent.node.js:383:20)\n at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:627:19)\n at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:878:51\n at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1211:20”,
“code”: “ERR_BAD_REQUEST”,
“status”: 400
}
}
}
}

Information on your n8n setup

  • n8n version:- 1.79.3
  • **Running n8n via n8n cloud
  • **Operating system:**Win10

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:
  • **n8n version:1.79.3
  • **Database (default: SQLite):default
  • **n8n EXECUTIONS_PROCESS setting default: own,
  • **Running n8n via n8n cloud
  • **Operating system: win10

Hey @marti_martinez, welcome to community!
Are you able to create an event at all? First, test it with the Google Calendar node.

Hey @marti_martinez,

I’ve simplified the workflow so you can have a better starting point.
Copy and paste this and see if it works:

.

:point_right: If my reply solves your problem, please remember to mark it as a solution.

2 Likes

hello! Yes, the only way I could create the event was with the {{$now}} expression. After that, trying to change that variable gave me diferent problems. It started to create events with the rigth date but a year ago, then I forced the promp with the current year, it create the event in ramdom dates. Thank you!

1 Like

Hello and thank you very much! I paste the workflow you provided and couldnt make it work, every time I send a chat message automatically was deleted and could not get the output (I am pre-novice). The great thing happen when I plugged your node calendar into my workflow and worked perfectly fine, rigth day, time, year and even the rigth ID. Now I understand the problem was the espression I was used, since it wasn´t detailed enough. Thank you!

1 Like

I’m glad it worked :muscle:

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