Handle explicit Backendless login requests from chat context
Run a login action when the request includes the needed credentials and clearly asks to authenticate the user.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
User Login
Tool 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".
Why this helps
A support handoff can require a separate login step that interrupts the flow of resolving a customer issue.
- Run the listed Backendless login action for supplied credentials.
- Keep the request and login result together in the automation report.
- Reduce context switching during an explicit authentication task.
Setup
Build it in a few focused steps.
- 1Connect 2chat and Backendless once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to run the Backendless login action only when the submitted request explicitly asks for login and includes the required identity and password.
- 4Choose the notis_webhook trigger and send the request and credentials to its HTTP endpoint.
- 5Choose a report channel, then test with one real example using an appropriate test account.
Questions about this workflow
Can it log in using only an email address from the chat?
The listed action requires an identity and password. Include the credentials needed for the login request.
Does login also validate the session token?
The login action is separate from token validation. This workflow only describes the login action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 2chat to Backendless. A trigger fires from one place; an action lands in another.
2chat triggers
Backendless actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Copy File
Tool to copy a file or directory within backendless file storage. use when duplicating files to a new location after verifying source and destination paths.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Directory
Tool to create a new directory at the specified path. use when you need to organize files under a new folder structure.
Create Backendless Hive
Tool 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'.
Create Backendless Timer
Tool 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.
Delete Directory
Tool to delete a directory at the specified path in backendless file storage. use when you need to remove folders after confirming the path.
Delete File
Tool to delete a file at the specified path in backendless file storage. use after confirming the file's relative path and filename.
Delete Backendless Timer
Tool to delete a backendless timer by name. use when you need to remove a scheduled timer after confirming its name.
Directory Listing
Tool to retrieve a listing of files and directories at a given path. use when browsing or filtering file storage directories.
Connect any two apps with Notis in the middle.
2chat and Backendless, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Backendless.