Load HubSpot data to Snowflake

HubSpot is a CRM platform providing REST APIs for managing objects, properties, and other customer data. Everything needed to build a working HubSpot → Snowflake 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 HubSpot to Snowflake 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 HubSpot 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.

---

HubSpot API at a glance

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

---

How do I authenticate with the HubSpot API?

HubSpot APIs require an Authorization HTTP header with a Bearer token. This applies to both OAuth access tokens and private app access tokens.

1. Get your credentials

1. Log in to your HubSpot account. 2. Navigate to Settings (gear icon in top navigation). 3. In the left sidebar, go to Integrations > Private Apps. 4. Click 'Create a private app'. 5. Provide a name and optional description. 6. Click the 'Scopes' tab and select the necessary permissions (e.g., crm.objects.contacts.read). 7. Click 'Create app' to generate the access token. 8. Click 'Show token' to reveal and copy your access token immediately; it will not be displayed again.

2. Add them to .dlt/secrets.toml

Copy
[sources.hubspot_source]
api_key = "your_private_app_access_token_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 HubSpot data can I load into Snowflake?

These are the HubSpot endpoints dlt can load into Snowflake:

---

How do I load only new HubSpot records?

HubSpot exposes paging.next.after on crm/objects/2026-03/{objectTypeId}, 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": "crm_objects", "endpoint": {
    "path": "crm/objects/2026-03/{objectTypeId}",
    "data_selector": "results",
    "incremental": {"cursor_path": "paging.next.after", "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 HubSpot pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /crm/v3/objects/contacts and /crm/v3/objects/deals from the HubSpot API into Snowflake:

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

@dlt.source
def hubspot_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.hubapi.com",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "crm_objects", "endpoint": {"path": "crm/objects/2026-03/{objectTypeId}", "data_selector": "results"}},
            {"name": "crm_search", "endpoint": {"path": "crm/objects/2026-03/{objectTypeId}/search", "data_selector": "results"}}
        ],
    }
    yield from rest_api_resources(config)


def load_hubspot_to_snowflake() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="hubspot_pipeline",
        destination="snowflake",
        dataset_name="hubspot_data",
    )
    load_info = pipeline.run(hubspot_source())
    print(load_info)


if __name__ == "__main__":
    load_hubspot_to_snowflake()

Run it with uv run python hubspot_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 HubSpot data in Snowflake?

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("hubspot_pipeline").dataset()
df = data.crm_objects.df()
print(df.head())

SQL:

Copy
SELECT * FROM hubspot_data.crm_objects LIMIT 10;

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

---

How do I deploy the HubSpot to Snowflake 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 HubSpot 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 HubSpot 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