Backendless is a comprehensive backend-as-a-service (BaaS) platform providing scalable backend functionality for mobile and web applications, including user authentication, data persistence, file storage, and custom API services.
Backendless is a comprehensive backend-as-a-service (BaaS) platform providing scalable backend functionality for mobile and web applications, including user authentication, data persistence, file storage, and custom API services. On Nagent, Backendless is exposed as a fully-configurable developer tools integration that any agent can call — 30 actions, and API key authentication. No code is required to wire Backendless into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Backendless to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Backendless into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Backendless, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BACKENDLESS_COPY_FILETool to copy a file or directory within Backendless file storage. Use when duplicating files to a new location after verifying source and destination paths.
Input parameters
Absolute path of the file or directory to copy. Must start with a leading slash ('/') and point to an existing resource.
Destination directory path where the source will be copied. Must start with a leading slash ('/'). Will be created if it does not exist.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_CREATE_DIRECTORYTool to create a new directory at the specified path. Use when you need to organize files under a new folder structure.
Input parameters
Authorization token for secure file service. Required only if security is enabled.
Full path of the directory to create, without leading slash. Multi-level directories will be created automatically if they don't exist.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_CREATE_HIVETool to create a new Hive. Use when you need to provision a new Hive resource before performing Hive operations. Example: Create a hive named 'groceryStore'.
Input parameters
Name of the hive to create. Must be URL-safe, without slashes. Allowed characters: letters, numbers, underscore, hyphen.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_CREATE_TIMERTool to create a new timer with schedule and code. Use when scheduling recurring or one-off tasks to run server-side logic after confirming parameters.
Input parameters
Unique name for the timer
Expiration date/time in Unix epoch milliseconds. Timer will stop after this
Schedule and repeat configuration for the timer
Start date/time in Unix epoch milliseconds. Defaults to now if omitted
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_DELETE_DIRECTORYTool to delete a directory at the specified path in Backendless file storage. Use when you need to remove folders after confirming the path.
Input parameters
Optional user authentication token. If provided, the delete operation will be executed under that user's security policies.
Relative path of the directory to delete in file storage. Do not include a leading slash.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_DELETE_FILEDeletes a file from Backendless file storage at the specified path. Use this tool when you need to remove files from storage. The operation is permanent and cannot be undone. Ensure the file path is correct before deletion.
Input parameters
Optional user-token obtained from login. When provided, the delete operation executes with the authenticated user's permissions and security policies.
Path to the file in Backendless file storage. Can be provided with or without a leading slash. Examples: 'txtfiles/test.txt' or '/txtfiles/test.txt' or 'test.txt'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_DELETE_TIMERDeletes a Backendless timer by its unique name. Use this tool to permanently remove a scheduled timer from your Backendless application. The timer must exist and you must provide its exact name. Once deleted, the timer's scheduled executions will stop immediately and cannot be recovered. Note: Requires access to Backendless Console Management API (available with Plus or Enterprise plans).
Input parameters
Unique name of the timer to delete. Must match an existing timer name exactly.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_DIRECTORY_LISTINGTool to retrieve a listing of files and directories at a given path. Use when browsing or filtering file storage directories.
Input parameters
If true, list directories recursively.
Path of the directory to list. Must start with '/'.
Index of the first item to return for pagination.
Wildcard pattern to filter results; '*' matches any substring, '?' matches a single character.
Maximum number of items to return.
User token for security policies. If provided, the request will be executed with user permissions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_GENERAL_OBJECT_RETRIEVALTool to retrieve objects from a specified Backendless table with filtering, sorting, and pagination. Use after confirming the table name and query options. Example: "Get Users where age > 30 sorted by created desc".
Input parameters
Comma-separated list of properties to include, e.g., 'name,email'
SQL-like condition to filter objects, e.g., 'age > 25'
Condition to filter groups after aggregation, e.g., 'COUNT(*) > 1'
Number of objects to skip before returning results. Default is 0 if not specified.
Comma-separated list of properties to sort by (append 'desc' for descending), e.g., 'created desc'
Comma-separated list of properties to group by, e.g., 'department'
Column name to return distinct values for, e.g., 'city'
Number of objects to return per page. Default is 10 if not specified.
Name of the data table to query, e.g., 'Users'
User authentication token to apply user-level security policies
Comma-separated list of properties to exclude, e.g., 'password'
Comma-separated list of related properties to include, e.g., 'profile,address'
Depth of related objects to include. Default is 1 if not specified.
Number of related objects to return per page. Default is 10 if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_GET_ALL_VALUESTool to retrieve all values from a map in a specified Hive. Use when you need to fetch the entire contents of a Hive map at once.
Input parameters
Key name identifying the map.
Name of the Hive where the map is stored.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_GET_COUNTER_VALUETool to retrieve the current value of a Backendless counter. Use when you need to inspect an atomic counter's value.
Input parameters
Optional user-token for enforcing user-level security policies.
Name of the counter to retrieve the value of.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_GET_FILE_COUNTTool to get the count of files in a Backendless directory. Use when you need to determine how many items match a filter or include subdirectories.
Input parameters
If true, include files in subdirectories recursively.
Path of the directory to count files in. Must start with '/'.
Optional glob or regex pattern to filter files (prefix with 'glob:' or 'regex:').
Optional user-token header for authenticated operations. Enforces user security policies if provided.
If true, include directories in the count as well.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_GET_KEY_ITEMSTool to retrieve values for a specified key in a list (all, single, or range). Use when you need specific elements or the entire list from a Hive key. Supports single index retrieval, range retrieval, or full list.
Input parameters
Key name identifying the list to retrieve.
Zero-based index to retrieve a single element. Mutually exclusive with from_index and to_index.
Zero-based end index for range retrieval. Must be provided together with from_index.
Name of the Hive where the list is stored.
Zero-based start index for range retrieval. Must be provided together with to_index.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_GET_TIMERTool to retrieve information about a specific timer. Use when you need to inspect a timer's schedule and next run details by name.
Input parameters
Name of the timer to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_MAP_PUTTool to set or update key-value pairs in a Hive map. Use when you need to add or update multiple entries in a Hive map.
Input parameters
Key-value pairs to set in the map.
Key name identifying the map.
Name of the Hive where the map is stored.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_MOVE_FILETool to move a file or directory within Backendless file storage. Use when relocating resources to a new path after verifying source and destination.
Input parameters
Absolute path of the file or directory to move. Must start with a leading slash ('/') and point to an existing resource.
Destination directory path where the source will be moved. Must start with a leading slash ('/'). Will be created if it does not exist.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_PUBLISH_MESSAGETool to publish a message to a specified messaging channel. Use when you need to send notifications or events to subscribers after confirming channel and payload.
Input parameters
Additional message headers for delivery filtering.
Content of the message to publish; must be a valid JSON type.
Unix timestamp in milliseconds when the message should be delivered.
Optional user token for security context; sent as 'user-token' header.
Unique identifier of the message publisher; optional.
Frequency in seconds for repeating delivery.
Name of the channel to publish the message to.
Unix timestamp in milliseconds when repeating should stop.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_RESET_COUNTERTool to reset a Backendless counter back to zero. Use when you need to reinitialize a counter before starting a new sequence.
Input parameters
Optional user-token for enforcing user-level security policies.
Name of the counter to reset to zero.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_SET_COUNTER_VALUETool to set a Backendless counter to a specific value conditionally. Use when you need to ensure the counter only updates if it currently matches an expected value.
Input parameters
The expected current value of the counter
Optional user-token for enforcing user-level security policies.
Name of the counter to update
The new value to set if the current counter equals the expected value
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_UPDATE_TIMERTool to update schedule or code of an existing timer. Use when you need to modify a timer's configuration after retrieval.
Input parameters
Updated code to execute when the timer runs
Name of the timer to update
New expiration date/time in Unix epoch milliseconds
Updated schedule and repeat configuration for the timer
New start date/time in Unix epoch milliseconds
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_DELETETool to delete a user by user ID. Use when removing a user account after confirming permissions.
Input parameters
The unique ID (objectId) of the user to delete.
Optional user authentication token. If provided, the operation uses the user's security context.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_FINDTool to retrieve user information by ID. Use when you need to fetch details for a specific user after you have their objectId.
Input parameters
The unique objectId of the user to retrieve.
Optional user authentication token. If provided, the request uses the user's security context.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_GRANT_PERMISSIONTool to grant a permission to a user on a specific data object. Use when precise access rights must be assigned after verifying the table and object IDs. Example: "Grant FIND permission to a user for a Person record".
Input parameters
Object ID of the user to whom the permission is being granted.
Unique identifier of the data object whose permissions are to be modified.
Type of permission to grant. Use '*' to grant all permissions.
Name of the data table containing the object.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_LOGINTool to log in a registered user with identity and password. Use when you need to authenticate a user before making subsequent requests. Example: "Login alice@wonderland.com with password wonderland".
Input parameters
Value for the property marked as identity (e.g., email).
User's password (case-sensitive).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_LOGOUTTool to log out the currently authenticated user. Use when you need to terminate the user session after operations.
Input parameters
Session token for the user. Use as 'user-token' header to authenticate the request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_PASSWORD_RECOVERYTool to initiate password recovery for a user. Use when a user requests a password reset after forgetting their password. Triggers an email with recovery instructions.
Input parameters
Value of the property marked as identity on the Users table (by default this is an email). Must be URL-encoded in the request path.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_REGISTRATIONTool to register a new user with email and password. Use when creating a user account or converting a guest account to a registered one after collecting credentials. Example: Register 'alice@wonderland.com' with password 'wonderland'.
Input parameters
User's email address used as identity in Backendless
Optional objectId of a guest user to convert into a registered user
Password for the new user (case-sensitive)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_REVOKE_PERMISSIONTool to revoke a permission from a specified user or role on a specific data object. Use when you need to deny a previously granted operation for a user or role on a data object after verifying the table and object IDs.
Input parameters
Name of the role to revoke the permission for. Ignored if 'user' is provided.
ObjectId of the user in the Users table. Provide this to revoke for a specific user.
Unique identifier of the data object whose permissions are to be modified
Type of permission to revoke. Use '*' to revoke all permissions.
Name of the data table containing the object
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_USER_UPDATETool to update properties of an existing Backendless user. Use when you need to modify user profile fields after login. Example: Update phoneNumber to "5551212".
Input parameters
ObjectId of the user to update
Key-value pairs of user properties to update
Session token obtained from a successful login. If provided, the update will be performed under that user's owner policy.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BACKENDLESS_VALIDATE_USER_TOKENTool to validate a user session token. Use after obtaining a token from login to confirm the session is active.
Input parameters
The session token to validate, returned by user login
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 77 agents privately built on Nagent that already use Backendless.
Build on Nagent
Connect Backendless to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Backendless, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Backendless is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Backendless is connected, you configure its 30 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Backendless steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Backendless event fires, the agent kicks off automatically.
Every Backendless action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Backendless ships with 30 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Backendless together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Backendless-based workflows tailored to your business.