Row triggers

Trigger Budibase automations whenever table rows are created, deleted or updated.

Row created

This trigger type allows users to create automations based on newly created rows. When a row is created, the entire row’s object will be passed to the automation and referenced through trigger Bindings. Various steps can be added to manipulate the data, such as updating information in another table or sending the data to a REST API endpoint.

Table selection that the automation will watch for new rows being created

Row deleted

This trigger works similarly to created rows. It will pass in a row’s object whenever a row is deleted. This can then be used to do other operations e.g. removing it from an API or deleting a related row elsewhere within Budibase.

Deleted row trigger image of inital step

Row updated

Like the other two triggers listed above, this automation will run whenever a row within the chosen table is updated.

Updated row automation trigger

It will provide both the old row's object (before the change). Additionally you also have access to the current values these are displayed as Bindings the names will reflect the columns of your table.

Image showing the old trigger row

With the addition of the oldRow object, you can now perform more complex operations, such as testing if a specific value has changed and then continuing or ending the automation based on that condition.

This trigger can also be used similarly to the creation and deletion triggers, such as updating additional related records or posting updates to an API or query.