Google Calendar, "The specified time range is empty."

[Florian_Guillemard]

Hi,

I don’t understand something with the Google Calendar node when I try to get an availability.

I generate two dates, one “five minutes past” and the other “five minutes on the futur”

When I execute the node, I got a message “The specified time range is empty.”

The start time is less than end time.

The worst, when I put the exact same value in TEXT… it works

Thanks for your help,

[MutedJam]

Hi @Florian_Guillemard, I am sorry you are having trouble. Unfortunately it’s not clear to me how exactly you are creating your fields minusfiveminute and plusfiveminute as you didn’t share your workflow.

Quickly running the below workflow dynamically populating the fields with values from 5 minutes ago and 5 minutes in the future is working fine for me on [email protected]:

This is the result:

Perhaps you can share your workflow and the current version of n8n you are using? Alternatively, and assuming your fields are simply based on the current time, perhaps you can use expressions such as {{ $now.minus({ minutes: 5}).toISO() }}?

[Florian_Guillemard]

@MutedJam

{{ $now.minus({ minutes: 5}).toISO() }}

Hi @MutedJam ,

Thanks for your response !

I did not have the notification and thought I have to come back to see if there is someone

Your answer is awesome and this WAS my way of doing MINUS-5 and PLUS-5 :

Your solution works really nice !

By the way, I am on 0.217.1 if it can help…

Thanks a lot,

[sirdavidoff]

Bear in mind that before 0.217.2 the names of the ‘start’ and ‘end’ fields in Google Calendar were very confusing:

How can I get the most recent Google Calendar events when using the "get many" option without getting every single event throughout history?

The start/end options are the wrong way around and should be renamed. This is what they actually do: Start time → Before (at least some part of the event must be before this time) End time → After (at least some part of the event must be after this time) Note that if you have recurring events, they will be returned but with the date of the original occurrence, not the occurrence that happens within your window. Here’s a workflow that fixes this, and also corrects for changes in daylight savi…