Load Adalo data to DuckDB

The Adalo API allows developers to programmatically manage collection records and trigger push notifications for apps built on the Adalo platform. Everything needed to build a working Adalo → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Adalo to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Adalo to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Adalo API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Adalo API at a glance

These values come from the Adalo API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Adalo API?

All requests to the Adalo API require an 'Authorization' header with a 'Bearer' token format (e.g., 'Authorization: Bearer [Your_App_API_Key]') and a 'Content-Type: application/json' header.

1. Get your credentials

1. Log in to your Adalo application dashboard.
2. In the left-hand navigation menu of the editor, click the 'Settings' gear icon.
3. Select 'App Access'.
4. Locate the 'API Key' section and click 'Generate Key'. If you have already generated one, you can view or regenerate it here.
5. Securely store your API Key, as it is required for all authenticated requests to the Adalo REST API.
6. To find your App ID, check the URL in your browser while in the app editor. It appears after 'https://app.adalo.com/apps/'. For example, if your URL is 'https://app.adalo.com/apps/12345-abcd-6789/app-settings', your App ID is '12345-abcd-6789' (the segment between /apps/ and the next slash).

2. Add them to .dlt/secrets.toml

Copy
[sources.adalo_source]
api_key = "your_adalo_api_key_here"
app_id = "your_adalo_app_id_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Adalo data can I load into DuckDB?

These are the Adalo endpoints dlt can load into DuckDB:

---

How do I load only new Adalo records?

Adalo exposes offset on apps/{app_id}/collections/{collection_id}/records, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "collections_records", "endpoint": {
    "path": "apps/{app_id}/collections/{collection_id}/records",
    "data_selector": "records",
    "incremental": {"cursor_path": "offset", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Adalo pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading collection_records and collection_record from the Adalo API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def adalo_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.adalo.com/v0",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "collections_records", "endpoint": {"path": "apps/{app_id}/collections/{collection_id}/records", "data_selector": "records"}},
            {"name": "record", "endpoint": {"path": "apps/{app_id}/collections/{collection_id}/records/{record_id", "data_selector": "id"}}
        ],
    }
    yield from rest_api_resources(config)


def load_adalo_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="adalo_pipeline",
        destination="duckdb",
        dataset_name="adalo_data",
    )
    load_info = pipeline.run(adalo_source())
    print(load_info)


if __name__ == "__main__":
    load_adalo_to_duckdb()

Run it with python adalo_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Adalo data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("adalo_pipeline").dataset()
df = data.collections_records.df()
print(df.head())

SQL:

Copy
SELECT * FROM adalo_data.collections_records LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Adalo to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Adalo loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Adalo data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack