Backendless Triggers¶
Zapier Triggers initiate a workflow in Zapier. Backendless/Zapier integration provides support for the following triggers:
Trigger/Event |
Triggered when.. |
Values delivered |
---|---|---|
User Logged In |
A registered user logs in to your app. |
All user properties defined in the Users table except for user's password. |
User Registered |
A new user is registered with your app. |
All user properties defined in the Users table except for user's password. |
Object Created |
A new object is saved in your Backendless database. You must specify the database table for which the trigger is created. |
All properties/column values for the created object. |
Object Updated |
An existing object is updated in your Backendless database. You must specify the database table for which the trigger is created. |
All properties/column values for the updated object. |
Object Removed |
An existing object is removed from your Backendless database. You must specify the database table for which the trigger is created. |
All properties/column values for the deleted object. |
New File |
A new file is stored in the Backendless file storage of your app. You must specify the folder to monitor for file creation. There is also an option to specify "all root folders". |
Name of the created file/folder. |
Trigger Rules¶
There are several constraints to keep in mind when configuring a Backendless trigger:
- Triggers are fired off only when a corresponding API call is used
- When a user is registered directly in the Backendless Console, the
User Registered
trigger does not fire. - When an object is created/updated/deleted directly in the Backendless Console. the
Object Created/Updated/Deleted
trigger does not fire. - When a file is uploaded directly in the Backendless Console, the
New File
trigger does not fire.
Implementation Details¶
Backendless Triggers are implemented via Backendless Cloud Code. Typically each trigger requires at least one Cloud Code scripts (API events handlers). The Cloud Code scripts is a limited resources - the quantity of available Cloud Code scripts varies between Backendless Pricing plans. It is possible to expand any of the pricing plans to have unlimited Cloud Code scripts through a purchase of the corresponding function pack from the Backendless Marketplace.
At the present moment the Backendless/Zapier Integration is available only for Backendless Cloud.