Resources · n8n integration

Adalo n8n integrationAutomate Adalo with n8n.

Your Adalo database can be driven from a workflow instead of by hand. The Adalo n8n integration exposes one resource, Collection, and 5 operations that create, read, update and delete rows. No Adalo trigger ships with n8n, so a schedule or another app starts the run.

Try the Adalo integration on n8nSee the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Adalo n8n integration actually do?

The Adalo n8n integration links the collections behind your Adalo app to the rest of your tools through the Adalo API. n8n ships an Adalo node with one resource, Collection, and five operations covering the whole life of a row: create it, retrieve one, retrieve all, update, delete. You point the node at a collection, give it an API Key and an App ID, and the rows move inside a workflow, a series of steps n8n runs for you.

Take a marketplace app built in Adalo. A form outside the app collects a partner request, n8n writes it straight into the Partners collection with collection.create, and the partner finds the record waiting the next time the app loads. That form can sit in Google Sheets or anywhere else that hands n8n an item to read.

Second pattern, the morning report. A Schedule Trigger wakes up, collection.getAll pulls the Orders collection with Return All switched on, and the count lands in Slack before anyone opens a laptop. Nobody exports a file by hand.

Third, keeping two databases honest. Adalo holds what the app shows, Airtable or Postgres holds what the business reports on. Read every row on one side, compare, then run collection.update on the records that drifted. The comparison logic lives in n8n, not inside either product.

The node carries one resource and five operations. When the Adalo API offers something outside that list, the HTTP Request node calls the endpoint directly and reuses the same Adalo credential through its predefined authentication, so the work stays in one place.

Two things to settle before building. API access on the Adalo side needs a Team or Business plan, so check the plan before you go looking for a key. And there is no Adalo trigger node in n8n: a workflow here starts with a Schedule Trigger running at a fixed interval, an n8n Webhook called by another service, or the trigger of another app. If that starting point is new to you, the n8n training walks through it.

Connect

How do you connect Adalo to n8n?

  1. 01

    Generate the API Key in Adalo

    Open the app editor, select Settings in the left menu, the gear cog icon, then App Access. In the API Key section, select Generate Key and copy the value once it appears. This is the secret n8n will send on every call, so treat it like a password and keep it out of notes and shared documents.

  2. 02

    Copy the App ID from the URL

    The App ID sits in the address bar of the app editor, right after https://app.adalo.com/apps/. With a URL like https://app.adalo.com/apps/b78bdfcf-48dc-4550-a474-dd52c19fc371/app-settings, the App ID is b78bdfcf-48dc-4550-a474-dd52c19fc371. Copy that string exactly, without the slash and without the part that follows it.

  3. 03

    Create the credential in n8n

    In n8n, open the Credentials menu and create an Adalo credential, a saved login n8n reuses on your behalf. Paste the API Key and the App ID into their fields and save. Every Adalo node you drop afterwards offers that credential in its dropdown, and the same entry serves the HTTP Request node when you call the API directly.

Actions

What can the Adalo node do?

The Adalo node exposes 5 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDelete
Collection✓✓✓✓✓

Collection

5 operations
01

Create a row

collection.create

What you see in n8n

Notes & use cases

Adds a new row to one Adalo collection and returns the created record for the next node.

Key parameters

  • Collection ID: the collection you write into. In Adalo, click the three buttons beside the collection name and select API Documentation to read the value.
  • Data to Send: autoMapInputData maps incoming properties onto columns of the same name, defineBelow lets you set each column yourself.
  • Inputs to Ignore: input properties you keep out of the write, separated by commas.
Use cases
a partner signup form fills a Leads collection, one row per submission.
02

Delete a row

collection.delete

What you see in n8n

Notes & use cases

Removes one row from a collection for good. n8n works from the record identifier, not from the name shown on screen in the app.

Key parameters

  • Collection ID: the collection holding the record, read from the API Documentation panel of that collection.
  • Row ID: the identifier of the record to drop, often {{ $json.id }} taken from a Retrieve all rows step placed just before.
Use cases
a nightly cleanup clears the test accounts left behind in a Users collection.
03

Retrieve a row

collection.get

What you see in n8n

Notes & use cases

Reads a single record and hands its columns to the rest of the workflow, one item out, so later nodes can branch on a real value.

Key parameters

  • Collection ID: where the record lives. The same identifier appears on the API documentation page of your app.
  • Row ID: the record to read, usually carried over from the previous node with an expression, the n8n syntax that pulls a value out of the incoming item, such as {{ $json.rowId }}.
Use cases
before an order confirmation goes out, pull the customer row to read the address stored today.
04

Retrieve all rows

collection.getAll

What you see in n8n

Notes & use cases

Lists the records of a collection. This is the operation behind exports, counts and any comparison with a second database.

Key parameters

  • Collection ID: the collection to read through.
  • Return All: on, n8n walks the API pages until every row of the collection is out; off, it stops at Limit.
  • Limit: the maximum number of rows returned while Return All stays off, handy on a large collection during testing.
Use cases
a weekly run copies the Orders collection into a spreadsheet for the finance side.
05

Update a row

collection.update

What you see in n8n

Notes & use cases

Writes new values into a record that already exists. The row keeps its identifier, so links from other collections survive.

Key parameters

  • Row ID: which record changes.
  • Fields to Send: the columns and their new values. A field that does not exist in the collection is ignored, and a field that does exist but is left out here is set to null, so list the columns you want to keep.
  • Collection ID: the collection the record belongs to.
Use cases
a payment confirmation flips the status column of an order from pending to paid.
Need help

Need help automating Adalo with n8n?

A person reads every message.

FAQ

Adalo and n8n, the questions that come up

01Is the Adalo n8n integration free?
The node costs nothing. It ships with n8n, on n8n Cloud and on a self-hosted instance under the Community Edition and its Sustainable Use licence, so there is no install step and no add-on to buy. The Adalo side is where the money question sits: API access requires a Team or Business plan, and without one the API Key section shows an upgrade prompt rather than a key. Once the credential exists in n8n you reuse it in every workflow that touches the app, and in the HTTP Request node too, so the plan is the only recurring cost in play.
02What credentials does the Adalo node need?
Two values, an API Key and an App ID. The key comes from the app editor: Settings, the gear cog icon, then App Access, then Generate Key in the API Key section. The App ID is the string that follows app.adalo.com/apps/ in the URL of the editor, before the next slash. Both go into a single Adalo credential created once in the Credentials menu of n8n. From there, every Adalo node offers it in a dropdown, and the same entry authenticates the HTTP Request node through its predefined authentication when you call the API yourself.
03What are the limits of the Adalo node?
The node carries one resource, Collection, with five operations: create, retrieve, retrieve all, update, delete. Anything the Adalo API offers beyond those goes through the HTTP Request node, which reuses the same Adalo credential, so you stay inside the same workflow. On reads, Return All is what stops you from getting a partial picture: leave it off and the run stops at Limit. On writes, remember that a column defined in the collection but absent from Fields to Send comes back as null, which is a real trap during an update.
04Does the Adalo node react in real time?
No, because there is no Adalo trigger node in n8n. A workflow around Adalo starts somewhere else and then calls the node. Three starting points cover most cases: a Schedule Trigger that runs at a fixed interval and reads the collection, an n8n Webhook, a URL that another service calls when something happens on its side, or the trigger of another app already in your setup. So the freshness of the data is whatever your schedule or your caller decides, not a push coming out of Adalo.
05n8n or Make for Adalo?
Both connect to Adalo, and the choice turns on four things rather than on features. Hosting: n8n runs on your own server or on n8n Cloud, Make is hosted only. Data control follows from that, since a self-hosted n8n keeps the app records on infrastructure you own. Cost model: Make bills per operation, which matters when a Retrieve all rows step returns a long collection. Visual logic: both draw the flow on a canvas, with different habits around expressions and branching. Try the same small workflow on each and keep the one your team reads faster.
Same platform

Other docs you might need on this stack.

Browse all integrations