Load n8n data to DuckDB

n8n is a workflow automation platform providing a REST API for managing workflows, executions, credentials, and other resources. Everything needed to build a working n8n → 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 n8n 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 n8n 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 n8n 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.

---

n8n API at a glance

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

---

How do I authenticate with the n8n API?

n8n requires authentication using a long-lived API key passed in the 'X-N8N-API-KEY' request header.

1. Get your credentials

To generate an n8n API key, log in to your n8n instance and navigate to Settings > n8n API. Click on Create an API key, assign a label, set an expiration period, and (if using an Enterprise plan) assign the necessary scopes. Copy the API key immediately, as it will not be displayed again. Each API request must include the key in the header named 'X-N8N-API-KEY'.

2. Add them to .dlt/secrets.toml

Copy
[sources.n8n_source]
api_key = "your_api_key_here"
base_url = "https://your-n8n-instance.com/api/v1"

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 n8n data can I load into DuckDB?

These are the n8n endpoints dlt can load into DuckDB:

---

How do I load only new n8n records?

n8n exposes cursor on workflows, 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": "workflows", "endpoint": {
    "path": "workflows",
    "data_selector": "data",
    "incremental": {"cursor_path": "cursor", "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 n8n pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /workflows and /credentials from the n8n API into DuckDB:

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

@dlt.source
def n8n_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://<n8n_host>/api/v1",
            "auth": {"type": "api_key", "api_key": api_key, "name": "X-N8N-API-KEY", "location": "header"},
        },
        "resources": [
            {"name": "workflows", "endpoint": {"path": "workflows", "data_selector": "data"}},
            {"name": "executions", "endpoint": {"path": "executions", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_n8n_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="n8n_pipeline",
        destination="duckdb",
        dataset_name="n8n_data",
    )
    load_info = pipeline.run(n8n_source())
    print(load_info)


if __name__ == "__main__":
    load_n8n_to_duckdb()

Run it with python n8n_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 n8n 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("n8n_pipeline").dataset()
df = data.workflows.df()
print(df.head())

SQL:

Copy
SELECT * FROM n8n_data.workflows LIMIT 10;

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

---

How do I deploy the n8n 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 n8n 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 n8n 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