Field-Level Filtering for Entity Automations

Currently, Entity Automations fire on every update to an entity — regardless of which field was changed. There is no way to restrict an automation to only trigger when specific fields are updated.

Use Case: In our app, we have an entity that receives frequent time and date updates via webhook integrations. We have an automation that should only run when “item_synced” is set to “false” — but because Base44 has no field-level filtering, the automation fires on every single update, including comlpetely irrelevant changes.

Even with an early exit check in the function code, each invocation still costs 1 Integration Credit. With high-frequency updates to this enity, this resulted in more than 20,000 unnecessary automation runs and significant credit loss for our app in the last couple of hours(!).

Requested Feature: Allow Entity Automations to filter by specific field changes, e.g.:

• Only trigger when field X changes

• Only trigger when field X equals value Y

• Only trigger when field X changes from value A to value B

This will make automations efficient and cost-effective for apps with high-frequency entity updates.