--- title: "Adalo Integration" description: "Read and write records in your Adalo app collections through the Adalo Collections API. Authenticates with a Bearer API key scoped to a specific Adalo App ID." url: https://flowrunner.ai/integrations/adalo date_modified: 2026-08-01T02:40:32-07:00 --- # Adalo [Web Platform](https://flowrunner.ai/integrations/category/developer-infrastructure) Read and write records in your Adalo app collections through the Adalo Collections API. Authenticates with a Bearer API key scoped to a specific Adalo App ID. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 5 actions · API key · available [Adalo website](https://adalo.com/) · [Platform Documentation](https://help.adalo.com/integrations/the-adalo-api) · Capability data verified 2026-07-14 1. A record changes in an external system that Adalo should reflect 2. Agent reads the source data and the matching Adalo record with Get Record 3. Agent confirms the fields it is about to write against the collection's field keys 4. Agent classifies whether the write is a routine sync or a change live app users will see 5. Agent applies the routine sync with Update Record 6. Agent posts the record change to the operations channel 7. A write that alters what live app users experience waits for a person to confirm ## What This Integration Enables FlowRunner agents use Adalo to keep a no-code app's database in step with the systems around it. An agent can list records in a collection with pagination, retrieve a single record by its ID, create a new record from a fields object, apply a partial update to an existing record, and delete a record by ID. Reads drive reporting, notifications, and conditional logic without touching the app. Writes keep the collection current when a CRM, a spreadsheet, or a form submission changes upstream. What the connector does not do is push every write straight into your live app unchecked. When a write changes what app users will see, the agent runs what is routine and asks a person before the rest. ### Without FlowRunner **Copied between systems by hand**: Someone re-keys external records into Adalo to keep the app current **Stale collection data**: The app shows records that drifted out of sync with the source system **Every write treated the same**: A cosmetic sync runs on the same path as a change that affects live users ### With FlowRunner **Records synced in the workflow**: The agent reads the source and writes the matching Adalo record automatically **Collection stays current**: The app reflects the source system without a person copying data across **User-facing writes confirmed**: A change live app users will see waits for a human confirmation first ## Use Case Scenarios ### One-Way Sync Into Adalo An external system changes, for example a new row lands in a source base or a form is submitted. The agent reads the incoming data, uses Get Record or List Records to find the matching Adalo record, and applies the change with Update Record. If no record exists yet, it uses Create Record. The Adalo app stays current without anyone copying data between systems. ### Reading Adalo To Power Downstream Work On a schedule, the agent calls List Records to pull the current state of a collection, reads the fields it needs, and feeds them into a report, a notification, or another integration. Nothing in the Adalo database changes. The app's data drives downstream work while remaining the single source the app itself renders. ### Confirmed User-Facing Change An agent is about to write a change that live app users will immediately see, such as flipping a status field that gates access or deleting a record that a user's screen depends on. Reading the current record and preparing the write happens automatically. The write itself does not. The agent holds it for a person to confirm, then calls Update Record or Delete Record once the confirmation comes back. ## Human-in-Loop Highlight When a workflow reaches a write that changes what live Adalo app users will experience, such as deleting a record a user's screen depends on or flipping a status field that controls access, the agent does not run it on its own. It pauses and routes to the responsible person through their preferred channel: "The workflow wants to run \[action\] on record \[id\] in the \[collection\] collection, which app users will see as \[effect\]. Current values: \[fields\]. Confirm the write, or hold?" The person confirms, and only then does the agent call the action. Reads and routine syncs keep running automatically; the writes that reach live users get a human first. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 5 actions ### Records 5 - **List Records** Lists records in an Adalo collection with pagination. Used to read the current state of a collection into a report, a notification, or a downstream step. - **Get Record** Retrieves a single record from a collection by its record ID. Used to load the exact record a workflow needs before acting on it. - **Create Record** Creates a new record from a fields object whose keys are the collection's field names or numeric property IDs. Used to seed or sync a new entry into an Adalo collection. - **Update Record** Applies a partial update to an existing record; only the fields you supply change, and omitted fields are left unchanged. Used to keep a record aligned with a source system. - **Delete Record** Deletes a record from a collection by its record ID. Used to remove an entry, and one of the writes worth a human confirmation because live app users may depend on it. ## Frequently Asked Questions ### What can FlowRunner do with Adalo? FlowRunner agents can run List Records, Get Record, and Create Record in Adalo, plus 2 more actions. ### Does connecting Adalo to FlowRunner require OAuth? No. Adalo connects to FlowRunner with an API key, no OAuth flow required. ### Can Adalo trigger a FlowRunner workflow automatically? Adalo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Adalo?** This integration exposes Adalo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/adalo. Site index: https://flowrunner.ai/llms.txt