Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More
Memberships
AI Productivity Hub (Plus)
Private โข 140 โข $699/m
AI Automation Society
Public โข 3.7k โข Free
AI Automation Society Plus
Private โข 128 โข $59/m
2 contributions to AI Automation Society
8d ago inย
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?
2
10
New comment 1d ago
1 like โข 7d
@James Walls Sometimes it feels like black magic
2 likes โข 7d
So what I found out, is, that there are basically two ways to query recurring events: Standard and with `singleEvents` set `true`. There even is an UI option in the node for that (see attached image). In **Standard mode** you get the parent instance of a recurring event with it's `start` and `end` and the RRULE in the `recurrence` string. You basically have all you need to calculate all other instances and n8n even calculates the `nextOccurence` from the datetime of the query, with its own `start` and `end` child objects. Unfortunately, the function is a little buggy, but you can still calculate it yourself. In **SingleEvent mode** the API returns all matching instances of the recurring event. You will lose the `recurring` field to calculate other events, but instead you get the `recurringEventId`, the eventID of the parent instance and the `originalStartTime` the datetime of start of the parent instance (might differ, when the current instance's `start` was changed in an exception). So, which mode you choose heavily depends on the purpose of your workflow. I hope this is helpful for somebody.
21d ago inย
I need some assistance
Good Morning All, I hope you are doing great this morning. I need some assistance with a project I am working on - I am new to n8n and still learning the ropes. I am the HR Manager of a company with a staff compliment of 300 employees, I want to build something where I can retrieve employee details fast. So there are different columns in the spreadsheet I have. The total amount of columns are 16 in total and it ranges from employee first name to org. unit. How can i make the workflow in such a way that I can retrieve specific information of an employee. Please assist and your help is much appreciated.
0
11
New comment 21d ago
1 like โข 21d
You might also have a look at Nates Video I linked in this post. You can skip most and concentrate on the retrieving from contact database by name and adjust the prompting to match your task.
1-2 of 2
