Check a customer profile while handling chat context
Bring a Backendless user lookup into a workflow started with submitted WhatsApp chat details and a known object ID.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Find User by ID
Tool to retrieve user information by id. use when you need to fetch details for a specific user after you have their objectid.
Why this helps
Switching from a customer chat to a separate profile lookup can slow down the response and break focus.
- Retrieve a user profile using a supplied object ID.
- Keep chat context and the lookup result together in the run report.
- Avoid opening a separate tool just to check a known user record.
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 retrieve the Backendless user identified by the supplied object ID and summarize relevant profile details for the submitted chat.
- 4Choose the notis_webhook trigger and send the chat context and object ID to its HTTP endpoint.
- 5Choose a report channel, then test with one real example and check the result against the profile.
Questions about this workflow
Can this find a user from only a phone number in a chat?
The listed action retrieves a user by ID. Supply the Backendless object ID in the webhook request; a phone number lookup is not specified by this action.
Does the workflow authenticate the user?
No. This action finds a user by ID. Authentication is a separate action and requires credentials.
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.