Hello everyone, I'm encountering two issues while integrating callin.io with Google Calendar, specifically for booking appointments.
Problem 1: Incorrect Booking Time
When I test the payload from callin.io, the lead is added to Google Calendar, but the time is incorrect. Instead of the appointment being scheduled for Friday at 7:00 PM, it's entered as Friday at 5:00 PM. I've reviewed the time zone settings in both callin.io and Google Calendar, but the problem persists. I suspect it might be a time conversion issue, but I'm unsure where the discrepancy lies.
Problem 2: Random Dates in Calendar
When testing the AI assistant for date bookings, random dates are being added to Google Calendar. Even though the assistant successfully arranges a meeting, the calendar becomes populated with these random dates. I'm uncertain if this is an API issue or a synchronization problem between callin.io and Google Calendar.
I have Google Calendar connected within callin.io, but I'm not sure if there are any specific configurations or verifications needed.
Details:
* Time Zone: Europe/Prague (used in callin.io and Google Calendar)
* Error Message: “Failed to map ‘timeMax’: Function ‘addMinutes’ finished with error! Invalid date.”
* Integration: callin.io → Google Calendar (Appointment Reservation)
Could anyone offer some guidance on the potential cause of these issues and how to resolve them? Thank you!
Hello,
Regarding your first issue, it does indeed appear to be a timezone problem. The time you entered (5 PM) seems to be a conversion from Prague time to GMT. Could you please share how the date is displayed in your webhook's output? Also, how did you configure it in GCalendar?
For the second error, can you show us the content of 2.result
? It's possible you might need to use the parseDate
function with the appropriate date pattern so that callin.io can correctly interpret it as a date.
Benjamin
Hello Benjamin, I am currently encountering an issue where, after testing a call with an assistant in callin.io, callin.io indicated success in callin.io, but an incorrect date was entered into my Google Calendar, and it was duplicated several times on the same day, as shown in the screenshot.
I am also attaching a screenshot from callin.io calls, which shows that the function should be operating correctly.
function": {
"name": "Booking",
"arguments": "{"name": "Jozef",n "BookingTime": "2023-10-10T11:00:00"n}"
Could you please advise on where the problem might lie this time?
Hello,
i’m not sure if this is the issue, but perhaps try adding the parseDate
function when you map the date returned by ChatGPT to ensure it's interpreted correctly. This is because ChatGPT returns a string, preventing callin.io from interpreting its value as a date. After using parseDate
with the format of the date returned by ChatGPT, you might need to wrap it with a formatDate
function, specifying the pattern Google Calendar expects.
I don't understand why Calendar is repeating the same appointment multiple times?!?!?!
Benjamin
I've created a new scenario using callin.io. It successfully books time and writes both the name and description into Google Calendar. However, the current issue is that it's unable to determine availability correctly. When I asked about October 16th at 12:00 PM, it indicated the time was free and proceeded to reserve it, even though that slot was already booked.
Could someone please help identify where the problem might be in this setup? I've attached screenshots showing how I've configured it in callin.io.
It’s empty (not colored) because the fields returned by Calendar are dynamic. Therefore, mapping is more complex. When you performed it the first time, this field was present, but not during this execution.
Anyway, is this field an array? You are passing through this filter if the array is not empty; is that your intention?
By the way, it’s very challenging to assist you without testing the scenario, examining the behavior of the different modules, and running/debugging. May I suggest you request consultancy from one of the callin.io partners? I’m confident that if someone reviews your scenario, it will be very helpful.
Kind regards,
Benjamin