BUG: n8n Google Calendar node with recurring events
I was very disappointed after building my first workflow with an AI Tool Agent node. No matter what LLM I tested, the agent responded with wrong event times. How could it be that neither 4o, o1, nor sonnet 3.5 could solve such a simple task. Investigating a little further, I noticed the Google Calendar node doesn't respond with sufficient information for recurring events. Here is a (redacted) example output: ```json [ { "kind": "calendar#event", // ... redacted ... "start": { "dateTime": "2023-09-07T09:30:00+02:00", "timeZone": "Europe/Berlin" }, "end": { "dateTime": "2023-09-07T11:00:00+02:00", "timeZone": "Europe/Berlin" }, // ... redacted ... "recurrence": [ "RRULE:FREQ=WEEKLY;UNTIL=20300101T225959Z;BYDAY=TH" ], // ... redacted ... "nextOccurrence": { "start": { "dateTime": "2024-12-19T08:42:42+00:00", "timeZone": "Europe/Berlin" }, "end": { "dateTime": "2024-12-19T10:12:42+00:00", "timeZone": "Europe/Berlin" } } } ] ``` As you can see, the time part of `nextOccurrence.start` and `nextOccurrence.end` differ from `start` and `end`. In fact 08:42:42 (`nextOccurrence.start`) was the time I queried the Google Calendar API. As a person who heavily works with recurring events, this is a showstopper. I wonder if Iām just being dense or missing something obvious. As nobody mentioned such a behavior before. Or is there anybody who has worked out a workaround?