Skip to content
Notis

Turn a WhatsApp profile request into a Backendless update

Use a submitted customer request to update agreed profile details in Backendless, with the user identity and changes specified in the instruction.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Update User

Tool to update properties of an existing backendless user. use when you need to modify user profile fields after login. example: update phonenumber to "5551212".

Why this helps

Re-entering a customer's requested profile change after a chat creates avoidable admin and errors.

  • Apply specified profile changes to an existing Backendless user.
  • Keep the user's request and update run together for review.
  • Reduce manual re-entry of details from customer conversations.

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 update only the specified properties of the identified Backendless user when the submitted request clearly asks for that change.
  • 4Choose the notis_webhook trigger and send the request, user identity, and intended details to its HTTP endpoint.
  • 5Choose a report channel, then test with one real example and verify the updated profile.

Questions about this workflow

Can Notis update any property it finds in the chat?

Specify which properties may be changed and provide the user identity and requested values. The action updates properties on an existing Backendless user.

Will it change a profile based on an ambiguous request?

Make the instruction require a clear request and specified values. Test with an example so the expected update behavior is clear.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Directory

Tool to create a new directory at the specified path. use when you need to organize files under a new folder structure.

ActionInstant

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'.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Delete Backendless Timer

Tool to delete a backendless timer by name. use when you need to remove a scheduled timer after confirming its name.

ActionInstant

Directory Listing

Tool to retrieve a listing of files and directories at a given path. use when browsing or filtering file storage directories.

ActionInstant

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.