How to Handle Missing start.dateTime in n8n’s Google Calendar 'Get Many' Node?

Below is a summary of the issue:

Issue Description

When using the Google Calendar node’s “Get Many” operation (with OAuth authentication), the workflow crashes with the error:

PLAINTEXTCopied
Cannot read properties of undefined (reading ‘dateTime’)

Error Details

The error indicates that the node is attempting to read the “dateTime” property of an undefined value. In this case, one of your calendars appears to have events without the expected structure. While most of your calendars return events with a valid start.dateTime, the problematic calendar is returning one or more events where the start parameter is missing the dateTime property. This may occur when an event is created as an all-day event or if the event data does not include a time-specific start value.

The stack trace points to the function eventExtendYearIntoFuture within the GenericFunctions.js file, where the node expects a valid dateTime value.

What This Means

• The error message is:

  JSONCopied
  {
    "errorMessage": "Cannot read properties of undefined (reading ‘dateTime’)",
    "errorDetails": {},
    "n8nDetails": {
      "n8nVersion": "1.76.1 (Self Hosted)",
      "binaryDataMode": "default",
      "stackTrace": [
         "TypeError: Cannot read properties of undefined (reading ‘dateTime’)",
         " at /usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GenericFunctions.js:172:40",
         " at Array.some ()",
         " at eventExtendYearIntoFuture (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GenericFunctions.js:169:17)",
         " at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GoogleCalendar.node.js:427:102)",
         " at processTicksAndRejections (node:internal/process/task_queues:95:5)",
         " at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:632:19)",
         " at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:890:51",
         " at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1224:20"
      ]
    }
  }

• The root cause is that some events do not include the expected start.dateTime field, leading the workflow to crash when it tries to extend the event dates.

Potential Resolution Steps

1. Inspect the Event Data:
   Check if the events in that calendar contain alternative date fields (for example, start.date for all-day events). Adjust the workflow or add a condition to handle cases where start.dateTime is missing.

2. Error Handling:
   Consider adding a conditional check in your workflow to bypass or handle events without start.dateTime, ensuring that the workflow does not crash when encountering incomplete event data.

3. Review Calendar Settings:
   Verify if the problematic calendar is set up differently (e.g., all-day events vs. timed events) compared to the others.

By ensuring that your workflow accounts for events that might only have a start.date field and not a start.dateTime, you can prevent the crash and allow your workflow to process all events successfully, regardless of their format.