Load Capsule-crm data to Supabase

Capsule CRM is a REST API for managing parties, opportunities, and other CRM records. Everything needed to build a working Capsule-crm → Supabase 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 Capsule-crm to Supabase pipeline

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

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 Capsule-crm 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.

---

Capsule-crm API at a glance

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

---

How do I authenticate with the Capsule-crm API?

Send the token in the HTTP header Authorization: Bearer {token}. For JSON requests and responses, include Accept: application/json; for requests with a JSON body, also include Content-Type: application/json.

1. Get your credentials

1. Sign in to your Capsule account. 2. Open your profile/name menu and choose My Preferences. 3. Open API Authentication. 4. Select Generate new API token and copy the token immediately; Capsule only shows the full token at generation time (later it is truncated). 5. Send it on every request as Authorization: Bearer YOUR_TOKEN, with Accept: application/json. For a multi-user application, use Capsule OAuth 2 instead: authorize at https://api.capsulecrm.com/oauth/authorise, exchange at https://api.capsulecrm.com/oauth/token, and use the returned access token as the bearer token. The v2 API does not use the legacy subdomain/API-key authentication model.

2. Add them to .dlt/secrets.toml

Copy
[sources.capsule_crm_source]
api_key = "your_capsule_personal_access_token"

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 Capsule-crm data can I load into Supabase?

These are the Capsule-crm endpoints dlt can load into Supabase:

---

How do I load only new Capsule-crm records?

Capsule-crm exposes updatedAt on parties, 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": "parties", "endpoint": {
    "path": "parties",
    "data_selector": "parties",
    "incremental": {"cursor_path": "updatedAt", "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 Capsule-crm pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading parties and opportunities from the Capsule-crm API into Supabase:

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

@dlt.source
def capsule_crm_source(api_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.capsulecrm.com/api/v2",
            "auth": {"type": "bearer", "token": api_token},
        },
        "resources": [
            {"name": "parties", "endpoint": {"path": "parties", "data_selector": "parties"}},
            {"name": "opportunities", "endpoint": {"path": "opportunities", "data_selector": "opportunities"}}
        ],
    }
    yield from rest_api_resources(config)


def load_capsule_crm_to_supabase_postgres() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="capsule_crm_pipeline",
        destination="postgres",
        dataset_name="capsule_crm_data",
    )
    load_info = pipeline.run(capsule_crm_source())
    print(load_info)


if __name__ == "__main__":
    load_capsule_crm_to_supabase_postgres()

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

---

How do I configure Supabase as the destination?

Supabase is PostgreSQL-compatible, so dlt loads into it through its postgres destination. Install the extra with uv add "dlt[postgres]", then add the Supabase connection string to .dlt/secrets.toml:

Copy
[destination.postgres]
credentials = "postgresql://<user>:<password>@<host>/<database>?sslmode=require"

Supabase shows the connection string in the project's database settings; see connecting to your database. See the dlt postgres destination docs.

---

How do I query Capsule-crm data in Supabase?

After a run, pipeline.dataset() holds the loaded tables, one per resource. A Relation is a query on that dataset, either a whole table or a SQL string, and reading it gives you the data as a Pandas DataFrame, a PyArrow table or Python tuples. Nothing is read until you ask for it.

Copy
import dlt

pipeline = dlt.pipeline("capsule_crm_pipeline")

# Step 1: Get the dataset from the pipeline
dataset = pipeline.dataset()

# Step 2: Get a Relation, either a whole table...
parties = dataset.table("parties")
# ...or any SQL query against Supabase
sample = dataset("SELECT * FROM parties LIMIT 100")

# Step 3: Read the data
df = parties.df()  # or .df(chunk_size=50) for a large table
arrow_table = sample.arrow()  # a PyArrow Table
rows = sample.fetchall()  # a list of Python tuples

# Which tables were loaded, and how big are they?
print(dataset.row_counts().df())
"""
      table_name  row_count
0        parties         13
1  opportunities          3
"""

The columns are the fields the Capsule-crm API returns. Your agent can run the same queries through the MCP server's execute_sql_query tool, and uv run dlthub show opens the Pipeline Dashboard with the schema, load metrics and a query box. See access loaded data in Python and exploring it in marimo notebooks.

---

How do I deploy the Capsule-crm to Supabase 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 Capsule-crm 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 Capsule-crm 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