Load Insightly data to DuckDB
Build a Insightly to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Insightly API base URL, auth, endpoints, and incremental loading.
Insightly is a CRM platform for managing contacts, organizations, leads, opportunities, projects, tasks, and other business data via a REST API. Everything needed to build a working Insightly → 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 Insightly to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Insightly 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 Insightly 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.
Insightly API at a glance
| Base URL | https://api.{pod}.insightly.com/v3.1/ |
| Example endpoint | GET contacts |
| Authentication | all requests require HTTP Basic authentication using the API key as the username |
| Pagination | Offset-based page size via top |
| Incremental field | updated_at |
| API reference | https://api.insightly.com/v3.1/Help#! |
These values come from the Insightly API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the Insightly API?
Insightly uses HTTP Basic authentication. The API key must be Base64-encoded as the username with an empty password, and passed in the Authorization header.
1. Get your credentials
- Log in to your Insightly CRM account.
- Click on the profile icon in the top-right corner of the dashboard and select User Settings.
- In the left-hand navigation pane, locate and click the API tab.
- Your unique API Key and API URL (which indicates your pod, e.g., na1) will be displayed here. Copy these values. Note that the API key acts as the username for HTTP Basic authentication, with a blank password.
2. Add them to .dlt/secrets.toml
[sources.insightly_source] api_key = "your_insightly_api_key_here" pod = "your_pod_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 Insightly data can I load into DuckDB?
These are the Insightly endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| contacts | contacts | GET | Retrieves a list of contacts | |
| leads | leads | GET | Retrieves a list of leads | |
| organizations | organisations | GET | Retrieves a list of organizations | |
| opportunities | opportunities | GET | Retrieves a list of opportunities | |
| projects | projects | GET | Retrieves a list of projects |
How do I load only new Insightly records?
Insightly exposes updated_at on contacts, 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.
{"name": "contacts", "endpoint": { "path": "contacts", "incremental": {"cursor_path": "updated_at", "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 Insightly pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading Contacts and Organisations from the Insightly API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def insightly_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.{pod}.insightly.com/v3.1/", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key}, }, "resources": [ {"name": "contacts", "endpoint": {"path": "contacts"}}, {"name": "leads", "endpoint": {"path": "leads"}} ], } yield from rest_api_resources(config) def load_insightly_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="insightly_pipeline", destination="duckdb", dataset_name="insightly_data", ) load_info = pipeline.run(insightly_source()) print(load_info) if __name__ == "__main__": load_insightly_to_duckdb()
Run it with python insightly_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 Insightly 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):
import dlt data = dlt.pipeline("insightly_pipeline").dataset() df = data.contacts.df() print(df.head())
SQL:
SELECT * FROM insightly_data.contacts LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Insightly 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 Insightly loads into governed, documented models.
- Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.
What other destinations can I load Insightly data to?
dlt loads into any of these — only the destination argument changes:
| Destination | Example value |
|---|---|
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
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
Was this page helpful?
Community Hub
Need more dlt context for Insightly to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.