Resources · Make integration

Backendless Make integrationAutomate Backendless with Make.

Want your Backendless app to react on its own when users sign up or data changes? The Backendless Make integration gives you 18 modules, 10 of them instant triggers. This guide links your app and walks you through a first working scenario.

Try the Backendless integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Backendless Make integration automate?

The Backendless Make integration links your Backendless application to Make, a visual tool where you build a scenario: the automation itself, made of modules placed one after another. Backendless tells Make when a user registers, logs in or when a record changes, and Make can write back to your database, create users or send messages.

Welcome every new user. Watch a Registered User fires the moment someone signs up, and Send an Email answers with one of your own Backendless templates. Nothing to code on the server side.

Keep two tables in step. When Watch an Updated Object reports a change, Find Objects in the Database looks up the related records and Update an Object in the Database corrects them. Handy for a product team whose app stores orders and stock in separate tables.

Tidy up after a departure. Watch a Removed User tells Make that an account is gone; Delete an Object from the Database can then clear the leftovers that point to it, and a push notification can warn an admin.

The listed modules do not cover the whole Backendless API. For anything else, Make an API Call reuses the same connection to reach any endpoint. If a run fails and you are stuck, the Make troubleshooting guide lists the usual fixes, and the Make training starts from the basics. Weighing another tool? The n8n vs Make comparison puts both side by side.

Connect

How do you connect Backendless to Make?

  1. 01

    Copy your two keys from Backendless

    Open the main dashboard of your Backendless application and click the Manage icon in the menu on the left. In App Settings, copy the Application ID, then the key labeled REST API Key. Keep both at hand.

  2. 02

    Add a Backendless module in Make

    In your scenario, add any Backendless module and click Create a connection. A connection is your Backendless account linked to Make once, then reused by every Backendless module. You can name it in Connection name, which helps when you run several apps.

  3. 03

    Paste the keys and save

    Paste the Application ID and the REST API Key you copied, or follow the instructions Make shows on screen, then save. Once it works, Make can list your data tables in the module fields, so you pick them instead of typing names.

First scenario

Your first scenario: a welcome email for every sign-up

GoalWhen a new user registers in your Backendless app, Make sends them a welcome email built from one of your Backendless templates.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + to place the first module. Everything you build next hangs off this first brick.

  2. 02

    Pick the sign-up trigger

    Search for Backendless and choose Watch a Registered User. Click Create a webhook, then Create a connection and paste your Application ID and REST API Key.

  3. 03

    Add the email action

    Click the + on the right of the trigger and pick Send an Email. Choose your welcome template, then map the new user's data that arrives from the trigger.

  4. 04

    Test it with Run once

    Click Run once, then register a test account in your app. Each module shows the bundle it received, that is the item passed along, here the new user. Check the email landed.

  5. 05

    Switch the scenario on

    When the test looks right, switch the scenario on. From then on, each sign-up in Backendless calls Make through the webhook and the welcome email goes out without you.

Triggers

What can start a Backendless scenario?

10 modules start a scenario when something happens in Backendless. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Backendless as soon as it happens.

Backendless1Watch a Created Object

Watch a Created Object

Instant trigger

In Make“Triggers when a new object is created in chosen data table.”

Every new record saved in the data table you choose reaches your scenario as a bundle, so a new order, request or booking row can set off the next steps without anyone copying it by hand. It is the broadest starting point of the app.

How it fires
instant, Backendless calls Make through a webhook as soon as the record is created.
When to use it
a table where your app stores incoming requests, and the team wants each one routed somewhere else right away.
Watch out
the trigger follows the table you pick in its settings, so rows saved in another table will not reach this scenario.
Backendless2Watch a Logged In User

Watch a Logged In User

Instant trigger

In Make“Triggers when a registered user logs into your Backendless application.”

Know the moment a registered user opens a session in your Backendless application. Make receives that user as a bundle, ready to feed a log table, a counter or a message to someone on your side.

How it fires
instant, Backendless calls Make through a webhook as soon as the login happens.
When to use it
you run a client portal and want to record who comes back, or greet someone on their first return.
Watch out
every login is one run of the scenario, and each module in it spends an operation, the unit Make counts on your plan. A busy app burns through those fast.
Backendless3Watch a Logged Out User

Watch a Logged Out User

Instant trigger

In Make“Triggers when a logged in user logs out.”

This trigger closes the loop on sessions: it hands Make the user who just signed out of your app. Paired with the login trigger, it gives you both ends of a visit to work with in the same place.

How it fires
instant, Backendless calls Make through a webhook as soon as the user logs out.
When to use it
you want to save the end of a session in a table, or trigger a follow-up once someone leaves a shared workspace.
Watch out
it only concerns users who were logged in first, so visitors without an account never show up here. Pair it with the login trigger if you need the full picture.
Backendless4Watch a New File

Watch a New File

Instant trigger

In Make“Triggers when a new file is uploaded.”

Uploads to your Backendless storage stop sitting unnoticed: each new file starts the scenario, and Make passes its details along so the next module can act on them.

How it fires
instant, Backendless calls Make through a webhook as soon as the upload completes.
When to use it
your users send documents or photos through the app and someone needs to review each one, or you want to log every upload in a data table with Save a New Object in the Database.
Watch out
on the Free plan, Make handles files of up to 5 MB. If your users send heavier documents, check your plan before you rely on this trigger.
Backendless5Watch an Updated Object

Watch an Updated Object

Instant trigger

In Make“Triggers when an object is updated in the selected table.”

Catch a change as soon as a record is edited in the table you select: a status that moves to paid, an address that gets corrected, a stock level that drops. The updated object arrives in Make as a bundle.

How it fires
instant, Backendless calls Make through a webhook as soon as the object is updated.
When to use it
a change in one table has to ripple into another table or out to a person, for instance an order marked shipped.
Watch out
if the same scenario runs Update an Object in the Database on that table, its own edit can wake the trigger again. Write the result to another table instead, and watch the first runs with Run once.
Backendless6Watch an Updated User

Watch an Updated User

Instant trigger

In Make“Triggers when a user data is updated.”

Profiles change all the time, and this trigger tells Make each time a user's data is edited in your app, so other systems do not keep an old email or a stale plan.

How it fires
instant, Backendless calls Make through a webhook as soon as the user data changes.
When to use it
your marketing list or your support desk must follow the profile a customer just edited in the app.
Watch out
it reacts to users, not to the other tables. For changes in any other table, Watch an Updated Object is the right trigger. Test with a real edit and Run once to see which data comes through.
Backendless7Watch a Registered User

Watch a Registered User

Instant trigger

In Make“Triggers when a new user is registered in your Backendless application.”

Turn each sign-up into a starting point: as soon as a new user registers in your Backendless application, Make gets that person as a bundle and can welcome, notify or file them.

How it fires
instant, Backendless calls Make through a webhook as soon as the registration goes through.
When to use it
onboarding, the classic case. Send an Email with your welcome template, or alert the sales team about a new account.
Watch out
if another scenario creates accounts with Register a User, those new users may reach this trigger as well. Check with Run once so nobody gets welcomed twice.
Backendless8Watch a Removed Object

Watch a Removed Object

Instant trigger

In Make“Triggers when an object is removed from the data table.”

Deletions leave no trace unless something records them. This trigger reports each object removed from the data table you choose, so you keep a history or clean up what depended on it.

How it fires
instant, Backendless calls Make through a webhook as soon as the object is removed.
When to use it
an archive table that should keep a copy of every deleted booking, or a shared sheet that must lose the same row.
Watch out
the object no longer exists in Backendless, so copy whatever you need from the bundle the trigger delivers rather than looking it up again.
Backendless9Watch a Removed User

Watch a Removed User

Instant trigger

In Make“Triggers when a user is removed.”

When an account disappears from your app, other tools often still hold that person. This trigger tells Make about each removed user so you can close the matching records elsewhere.

How it fires
instant, Backendless calls Make through a webhook as soon as the user is removed.
When to use it
a customer asks to delete their account and you want the mailing list, the CRM and the related tables to follow.
Watch out
treat what follows with care. A Delete an Object from the Database module placed after it cannot be undone, so run the chain once on a test user before switching it on.
Backendless10Watch Deleted Files or Directories

Watch Deleted Files or Directories

Instant trigger

In Make“Triggers when a file or directory is deleted in your Backendless application.”

Keep an eye on your storage from the other side: this trigger fires when a file or a whole directory is deleted in your Backendless application, and passes what was removed to the next module.

How it fires
instant, Backendless calls Make through a webhook as soon as the deletion happens.
When to use it
you log file activity for an audit, or you need to remove the database records that pointed to a deleted document.
Watch out
this module is a trigger, not an action. It does not delete anything itself; it only reports deletions that happen in your Backendless application.
Modules

What can Make do in Backendless?

Backendless gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Backendless1

Delete an Object from the Database

Action

In Make“Deletes an object from a specified table by ObjectId.”

Removes one record from the table you name, identified by its ObjectId, the unique identifier Backendless gives every object. Useful to close the loop when something ends elsewhere.

When to use it
a cancellation in another app must wipe the matching booking in Backendless.
Watch out
a deletion does not come back. Map the ObjectId from a previous module rather than typing it, and test on a dummy record.
Backendless2

Make an API Call

Action

In Make“With this module you can build your own request.”

Reaches any part of the Backendless API the other modules leave out, while reusing the connection you already made. You write the request yourself, so it is the one module here that needs a look at the Backendless API reference.

When to use it
you need an operation none of the 18 modules offers.
Watch out
test the request with Run once and read the output bundle before mapping anything into the next module.
Backendless3

Register a User

Action

In Make“Registers a new user in your Backendless application. This creates a new user record in the 'Users' data table.”

Creates an account in your Backendless application from data that lives somewhere else, and adds the new person to the Users data table like any sign-up would.

When to use it
a purchase, a form or an invitation handled outside the app should give that person access without a manual step.
Watch out
a scenario built on Watch a Registered User may pick up these accounts too, so check that the welcome is not sent twice.
Backendless4

Save a New Object in the Database

Action

In Make“Saves a new object in the database in the chosen data table.”

Writes a fresh record into the data table you choose. Once the connection exists, Make lists your tables, so you pick one and map the values coming from earlier modules.

When to use it
keep a log of events from other tools, such as payments, form answers or uploads, inside your own Backendless database.
Watch out
if the same scenario also starts on Watch a Created Object for that table, it can feed itself.
Backendless5

Send an Email

Action

In Make“Sends an email from your custom templates. To manage email templates, log in to Backendless Console and navigate to Messaging->Emails and then select "Create new template" in the Templates dropdown.”

Sends a message built from one of your Backendless email templates, so the wording and layout stay in Backendless while Make decides when it goes out.

When to use it
a welcome message, a receipt or a reminder tied to an event in your scenario.
Watch out
the template must exist first. Create it in Backendless Console under Messaging, then Emails, with Create new template in the Templates list.
Backendless6

Send a Push Notification

Action

In Make“Sends a push notification from a push notification template. To manage your Push Notification templates, log in to Backendless console, and navigate to Messaging->Push Notifications.”

Pushes a notification to your app's users from one of your Backendless push templates, which keeps the message short, consistent and ready to reuse across scenarios.

When to use it
an order changes status, a file is ready, or a teammate needs a nudge on their phone.
Watch out
Make only picks a template, it does not write one. Prepare it in Backendless Console under Messaging, then Push Notifications, before building the scenario.
Backendless7

Update an Object in the Database

Action

In Make“Updates an object in a specified data table.”

Changes the values of an existing record in the table you specify, so a status, an amount or a date stays accurate without anyone editing it by hand in the console.

When to use it
a payment confirmed in another tool should mark the matching order as paid.
Watch out
you need the record first. Put Find Objects in the Database before it to get the right object, and check Run once returns only one.
Backendless8

Find Objects in the Database

Search

In Make“Runs a query to the database to retrieve objects.”

Runs a query against your Backendless database and brings back the matching objects, one bundle each, for the modules that follow.

When to use it
before an update or a deletion, to fetch the exact record, or to pull a list of users meeting a condition.
Watch out
a search can return zero, one or many objects. Each one runs the next modules separately, so a loose query multiplies the work and the operations.
Need help

Need help automating Backendless with Make?

A person reads every message.

FAQ

Backendless and Make: common questions

01Is the Backendless Make integration free?
Yes, Backendless is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits and count usage in credits, meaning operations, each month. Your Backendless subscription is separate and depends on Backendless.
02What do you need to connect Backendless to Make?
You need an active Backendless account and an application with its API key. In your Backendless dashboard, click Manage, then copy the Application ID and the REST API Key from App Settings. In Make, add a Backendless module, click Create a connection, and paste both values. For an instant module, click Create a webhook first. The connection is then shared by every Backendless module of your account. You set it up once, then reuse it in every scenario you build.
03Do Backendless triggers in Make fire in real time?
Yes. All 10 Backendless triggers are instant: Backendless calls Make through a webhook as soon as the event happens, whether a user registers, an object changes or a file is uploaded. There is no polling interval to set on these modules. Remember to switch the scenario on after testing with Run once, otherwise nothing runs. Each event still counts as operations on your plan. The 15-minute interval a new scenario shows by default applies to scheduled triggers, not to these, which react to Backendless calling in.
04What if a Backendless module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Backendless API with the connection you already set up, so you are not limited to the 18 listed modules. You write the request yourself, which means reading the Backendless API reference for the part you need. Test the call with Run once and check the answer in the output bundle before mapping its values into the next modules. The operations it uses count like any other module.
05Should you use Make or n8n for Backendless?
It depends on what you need. On Make, Backendless comes with 18 ready modules, including 10 instant triggers on users, objects and files, plus Make an API Call for the rest of the API. n8n often has a node for the same apps, so look there to see whether Backendless is covered and how far. List the events and actions your project needs, then check which tool covers them, starting with the modules named on this page.
Same platform

Other docs you might need on this stack.

Browse all integrations