Actions¶
Zapier Action for Backendless executes an operation within your Backendless application. All available Actions correspond to an API request. All Backendless actions in Zapier accept arguments required to completion the operation. When configuring an action you must select an application (a list of apps is pulled from your Backendless account) and an API key. The application is where the action will be executed. The API key is used by Backendless to determine the user role associated with the request.
The following actions are available:
Action |
Description |
Action arguments |
---|---|---|
Register User |
Creates a new user account in your Backendless application. User accounts are stored in the Users data table in the Backendless database. |
|
Save New Object |
Stores a new object in the Backendless database. |
|
Update Object |
Updates an existing object in the Backendless database. |
|
Delete Object |
Deletes an existing object from the Backendless database. |
|
Send Email |
Sends an email generated from a Backendless email template to one or more recipients specified in the TO, CC and or BCC address lists. If the template uses templated substitution variables, the action arguments can specify the values for those. The email addresses the message is sent to can be pulled from the users registered with the application - i.e. the user records in the Users data table. The addresses can be set explicitly, provided through the results from the Zap's trigger or previous actions or set through the Criteria argument which is a where clause ran against the Users table. |
|
Send Push Notification |
Sends a mobile push notification generated from a Backendless Push Template. |
|