Please fill in the questionnaire below.
How have you self-hosted Baserow.
Official docker container with separate postgres container
Which version of Baserow are you using.
1.30.1
Describe the problem
EDIT! TLDR from my updates. I worked out that the issue is the webhook is sending the row data to n8n before the formula field is updated.
IE. I have 3 fields:
- “start date”
- “duration”
- “end date” - which is calculated from the “start date” and “duration”
When I update the “start date” my webhook sends the information to n8n before the “end date” is calculated, resulting in the incorrect data being sent. In order to get the correct data sent, I have to make another update (any one will do) to re-trigger the webhook and send the correct “end date” to n8n. this seems to maybe be a timing issue? I’m nt sure how to build in a delay or something before the webhook is triggered
My full journey to come to this conclusion is below for the bored 
It’s another strange one - and probably complex due to the integration of Baserow, n8n and Google Calendar API. However, due to the nature of the issue, I suspect the problem is originating from Baserow and not the other 2 services.
I have Baserow and n8n. I have 2 webhooks from baserow to n8n:
- New-booking-n8n
- Triggered when Rows are created
- POST to my n8n workflow called “Kapt-New-Booking”
- This one basically uses n8n to create a calendar entry in Google Calendar when a new booking comes into my Baserow app. It then writes the Google Cal Id into the a field called “Google-Cal_ID” in the row in BaseRow so it an be used to update the calendar entry if needed later (see next one). It works perfectly fine with no issues.
- Update-booking-n8n
- Triggered when rows are updated
- POST to my n8n workflow called “Kapt-Update_booking”
- This one updates the Google calendar event if a field in the row changes. It uses the “Google-Cal_ID” to know which calendar entry to update.
The strange thing about the 2nd one is it work for most fields. For example, my row has the following fields that can be updated:
- First Name
- Last Name
- Phone
- Package
- Location
- Date
- Time
plus a few others.
If I change any of these fields, the webhook and n8n workflow work fine and the Google Calendar entry is updated - except the “Date”. If I change the date only, the workflow fails and the Google Calendar entry is not updated. However… if I change a different field as well - or I go back in and change a different field (and trigger the webhook again) then the date is updated in Google Calendar.
So I know that everything is mapped correctly and that the webhook is working. But I can’t work out why it doesn’t work if I just change the date.
For example. If I change only date on a row, I’ll see that the workflow failed in n8n and the Google Calendar entry will not update with the new date. Looking at the n8n logs, the part that fails is the “update event” to the Google Cal API, and the error message is: “The specified time range is empty.” However, my time range looks fine:
- Start: 2025-01-19T02:00:00+00:00
- End: 2025-01-18T02:00:00+00:00
To compare it. I’ll trigger the webhook again with the same row. But this time I’ll change the “Location”. Since I changed the date on the previous example, it will update correctly this time. However, the start and end times are exactly the same:
- Start: 2025-01-19T02:00:00+00:00
- End: 2025-01-19T03:00:00+00:00
The only other thing that changed was the location. This is the same no matter what other field I change. Even if I just change the description and the date, it works fine. It will only throw an error if I change only thedate.
I’m at a loss as to how to troubleshoot this as it seems that the data is the same. Have you guys seen anything like this?