Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?
SaaS
What are the exact steps to reproduce this issue?
I have a table that is synced with Postgres. During the sync, the rows are properly created. I have two additional calculated columns added to this table only in Baserow (they help me set a status of row processing in n8n).
After the row is created during the sync, the webhook is fired and is properly captured in n8n. The payload is correct - it contains all the keys from the table. However… the JSON fields contain only null values.
It was thinking that maybe for the synced tables, you have separated the event of row creation from the actual insertion of the data, but webhook for row update is not triggered at all. I can think of a workaround for now where the webhook only provides information that row has been created, but I have to call the database anyway to get the data, but I am afraid that sometimes the data might be null as well for a split second.
What information do you need to check why the webhook contains null values instead of those inserted to the database?
Attach screenshots, videos, or logs that demonstrate the issue.
Can you share more information how your sync is set (is it one way data sync or two way? Is it periodic or do you trigger sync manually?) , and how your webhook is being configured?
This is a one-way sync. In this case, this has been triggered manually, but on another account I will use it with 1 hour sync. This is webhook configuration:
I cannot reproduce the issue though. I think this empty webhook might have been a test webhook triggered from Baserow UI. There are, however, two more worrying things discovered now:
The actual webhooks do not work at all for synced tables! Pressing the button on the Baserow UI to test the webhook triggers N8N workflow just fine. But after a sync, when the row is actually created, no webhook is emitted.
Each database sync resets baserow row id. In other words, if the table contained rows 1-99, after both manual and automated re-sync, the same rows have new identifiers, e.g. baserow ids are in the range 100-198. If I had any calculated or otherwise edited fields added to the synced table, their values were lost. Baserow apparently truncates and re-populates the table during resync while keeping its internal auto-increment id field. Please confirm this is how it works and if each sync triggers “row created” for all rows?
