Load Insightful data to DuckDB
Build a Insightful to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Insightful API base URL, auth, endpoints, and incremental loading.
Insightful is a RESTful time-tracking, productivity and employee monitoring platform that exposes its data and actions via a JSON HTTP API. Everything needed to build a working Insightful → 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 Insightful to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Insightful 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 Insightful 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.
Insightful API at a glance
| Base URL | https://api.insightful.io |
| Example endpoint | GET issues |
| Records found at | items |
| Authentication | all requests require a Bearer token for authentication — sent in the Authorization header, prefixed Bearer |
| Pagination | Cursor-based via cursor, next cursor at next_page_token, page size via limit (default 20, max 1000). Cursor/token-based pagination uses a query parameter (e.g., cursor) to request the next page, and a response field (e.g., next_page_token) to carry the token forward. The AIP-158-style pattern also describes maxPageSize behavior (max 1000, values above coerced) and requires passing the page token while keeping other list parameters unchanged. |
| Incremental field | updated_at |
| Record id | id |
| API reference | https://developers.insightful.io/ |
These values come from the Insightful API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the Insightful API?
Insightful uses Bearer token authentication. Requests must include an 'Authorization' header with the value 'Bearer '.
1. Get your credentials
- Log in to your Insightful organization account as an Administrator at https://app.insightful.io/. 2. Navigate to Settings, then select API Tokens. 3. Click the Create new Token button. 4. Enter a descriptive name for the token. 5. Click the button to generate the token. 6. Copy the token immediately and store it securely; it is displayed only once.
2. Add them to .dlt/secrets.toml
[sources.insightful_source] api_token = "your_insightful_bearer_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 Insightful data can I load into DuckDB?
These are the Insightful endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| users | /users | GET | users | Retrieves a list of users. |
| issues | /issues | GET | Retrieves issues, supports incremental filtering. | |
| comments | /issues/{number}/comments | GET | Fetches comments for a specific issue. | |
| organizations | /orgs | GET | Lists organizations. | |
| repositories | /repos | GET | Retrieves repository information. |
How do I load only new Insightful records?
Insightful exposes updated_at on issues, 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": "issues", "endpoint": { "path": "issues", "data_selector": "items", "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 Insightful pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading v2/employees and v2/teams from the Insightful API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def insightful_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.insightful.io", "auth": {"type": "bearer", "token": api_token}, }, "resources": [ {"name": "issues", "endpoint": {"path": "issues", "data_selector": "items"}}, {"name": "comments", "endpoint": {"path": "issues/{resources.issues.number}/comments", "data_selector": "comments"}} ], } yield from rest_api_resources(config) def load_insightful_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="insightful_pipeline", destination="duckdb", dataset_name="insightful_data", ) load_info = pipeline.run(insightful_source()) print(load_info) if __name__ == "__main__": load_insightful_to_duckdb()
Run it with python insightful_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 Insightful 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("insightful_pipeline").dataset() df = data.issues.df() print(df.head())
SQL:
SELECT * FROM insightful_data.issues LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Insightful 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 Insightful 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 Insightful 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 Insightful to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.