Handle clear access requests with a Backendless permission grant
Turn a well-specified access request submitted with WhatsApp context into a Backendless permission grant.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Grant Permission to User
Tool 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".
Why this helps
Access requests can stall when the team has to copy details between a conversation and the data management tool.
- Grant a specified permission to a specified user on a specified object.
- Keep the request context available alongside the workflow report.
- Reduce manual steps for clear, well-scoped access changes.
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 grant only the specified permission to the identified user on the identified Backendless data object when the submitted request clearly names all three.
- 4Choose the notis_webhook trigger and send the request and required identifiers to its HTTP endpoint.
- 5Choose a report channel, then test with one real example and verify the permission result.
Questions about this workflow
What information must the request include?
It should include the target user, data object, and permission. The action requires a specific permission on a specific object.
Can the workflow infer the access level from a vague chat?
Use a clear instruction that requires the permission to be explicit. The request needs enough detail to identify the intended grant.
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.