Bug with Rows Updated webhook

monachus · May 27, 2026, 2:16pm

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

2.2.2 (why does this field have to be 10-characters or longer when your version numbers are not?)

If you are self-hosting, which installation method do you use to run Baserow?

Docker 29.1.1

What are the exact steps to reproduce this issue?

create a webhook to fire on Rows are updated and set it to monitor a boolean field
change that boolean field from false to true in baserow via n8n (webhook fires)
update the boolean field again (setting true to true)
webhook triggers with “Rows are updated” even though no data changed

I would expect that “Rows are updated” means “data in the row has changed from A to B.” Poking a field with the exact same value (setting true to true) is not an update and should not trigger the webhook.

I know that I can compare old_items and new_items, but i shouldn’t have to do that. This isn’t an update.

Attach screenshots, videos, or logs that demonstrate the issue.

olgatrykush · May 28, 2026, 9:56am

Hey @monachus

Thanks for pointing this out! I’ve changed the minimum length to 5 characters.

I’ve also forwarded your request to the dev team to take a look.

olgatrykush · May 29, 2026, 11:07am

Hey @monachus, I checked with the development team and this is the current behavior rather than a bug. The “Rows updated” webhook is triggered whenever an update operation is performed, even if the submitted values are identical to the existing values.

We agree that triggering webhooks when no actual data changes can be confusing, so we’ve created an issue to track potential improvements:

github.com/baserow/baserow

Webhooks and automations trigger on row_updated events even when no field values changed

opened 11:07AM - 29 May 26 UTC

mrktbloom

### Feature description Currently, row_updated webhooks and automations are tri…ggered whenever an update operation is performed, even if the submitted values are identical to the existing values. ### Examples - Create a webhook for "Rows updated". - Set a boolean field "true". - Update the same field with true → true. - The webhook is triggered, despite no actual data change. Expected behavior Only trigger row_updated webhooks and automations when at least one field value actually changes. Notes - This is known behavior, not a bug. - Changing it may be a breaking change because existing workflows could rely on the current behavior. - Consider introducing this as an optional setting or part of a future redesign.

For now, if you need to detect real changes, you’ll need to compare old_items and items in the webhook payload.