Database Trigger
This feature triggers Actionflows when data changes (insert, update, or delete), enhancing automation within the project.
Last updated
This feature triggers Actionflows when data changes (insert, update, or delete), enhancing automation within the project.
Last updated
This feature triggers Actionflows when data changes (insert, update, or delete), enhancing automation within the project.
Common use cases include:
Automatically upgrading to VIP when a user's payment exceeds a specified amount
Automatically sending a notification when an order is completed
Automatically generating an operation record when user points change, for easier tracking
Here’s how to set it up using an example: When a user’s payment exceeds $1000, the system will automatically upgrade them to VIP.
Add Actionflow
Set the input parameter account_id.
Add a "Get Payment mount" node to calculate the total payment for the user.
Add an "Update account" node to update the user to "VIP."
Add Trigger
A trigger can only be added after the Actionflow is saved.
Select Operation Type and Data Table There are 4 types of supported operations:
On Data Insert
On Data Update
On Data Delete
On Data Insert or Update
Set Conditions and Actionflow Parameters
Triggers allow access to both the previous and updated data values.
View the history of triggers in the log system (currently unavailable).
Automated behavior flows (triggered by scheduled tasks or database changes) have usage limits:
Free Tier (resets monthly):
Free plan: 1000 executions/month
Basic plan: 10000 executions/month
Pro plan: 50000 executions/month
Paid Option (valid indefinitely):
Cost: 10000 executions for $ 10
Cyclic Trigger Prevention
The system ensures that each trigger in a chain is only triggered once. For example, in the sequence: Trigger A → Actionflow A → Trigger B → Actionflow B → Trigger A, the second Trigger A will not be triggered because it has already been executed.
Avoid Concurrent Modifications to the Same Data
Simultaneous updates from multiple Actionflows to the same data may cause deadlock.
Data Imports May Trigger Multiple Events
If a "On data insert" trigger is set on a table and data is imported, each imported record will trigger the flow separately.
