Xano1
Database Triggers
You can find database triggers on each table by clicking the settings icon in the top-right corner.Click + Add Database Trigger to create a new database trigger.You can specify what Data Sources the trigger will execute on. If no data source is set, then it will execute on all data sources.Select the actions that will activate this trigger.Inserts
Any time a record is added to the tableUpdates
Any time a record is editedDeletes
Any time a record is deletedTruncates
When the content of the database table is clearedFinally, you can set up custom filters so that the trigger only runs if the record matches certain conditions. For example, if you only want the trigger to run if a new order is created for a user, or a new user is created with a certain role.
Database triggers have predefined inputs that contain all of the information you’ll need to build a workflow based on the database event.
This is the contents of the new record — if you’re adding a record, this will contain the contents of the new record, and if you’re updating a record, this will contain the contents of the updated record. On deletes and truncates, this will be empty.
This is the contents of the old record — if you’re deleting or editing a record, this will contain the contents of the record before the change. On inserts and truncates, this will be empty.
The action that activated the trigger. Valid options are
The datasource this trigger has been executed against
Any time a record is added to the tableUpdates
Any time a record is editedDeletes
Any time a record is deletedTruncates
When the content of the database table is clearedFinally, you can set up custom filters so that the trigger only runs if the record matches certain conditions. For example, if you only want the trigger to run if a new order is created for a user, or a new user is created with a certain role.
Database triggers have predefined inputs that contain all of the information you’ll need to build a workflow based on the database event.
newThis is the contents of the new record — if you’re adding a record, this will contain the contents of the new record, and if you’re updating a record, this will contain the contents of the updated record. On deletes and truncates, this will be empty.
oldThis is the contents of the old record — if you’re deleting or editing a record, this will contain the contents of the record before the change. On inserts and truncates, this will be empty.
new and old are the whole stored record, including columns whose visibility is set to Internal. A password field added in the table editor is Internal by default, so it arrives as its stored hash, never the plain-text password.This is different from the rest of your function stack. A Get Record (db.get) leaves Internal columns out unless you list them in its output, and the record an Add Record returns leaves them out too. The trigger gets them anyway: on an update or a delete, old is the only place left to read a column’s previous value.Neither Internal visibility nor Sensitive Data removes a column from new or old, or from the trigger’s history when history is enabled. If your trigger sends new or old somewhere else (an external API, a log, another table), remove the columns you don’t want to share first.actionThe action that activated the trigger. Valid options are
insert update delete truncatedata sourceThe datasource this trigger has been executed against