Source connector

Insightly connector

Insightly integration for databases, warehouses and BI tools

CRM and lightweight project delivery. Datrise captures Insightly entities such as contacts, organizations, opportunities, projects, and delivery milestones, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Insightly REST API v3.1 authenticates with API key, HTTP Basic, incremental runs key on DATE_UPDATED_UTC, and Insightly caps calls at 10 requests per second per instance, plus a rolling 24-hour daily cap by plan: 1,000/day Free, 20,000/day Legacy, 40,000/day Plus, 60,000/day Professional, 100,000/day Enterprise; exceeding either returns HTTP 429.

Of the 5 objects, 5 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `insightly_contacts`) with a schema derived from the Insightly API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Insightly pipeline page, and join the waitlist to get the Insightly connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Insightly data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
contacts	insightly_contacts	Upsert by primary key, incremental on updated-at
organizations	insightly_organizations	Upsert by primary key, incremental on updated-at
opportunities	insightly_opportunities	Upsert by primary key, incremental on updated-at
projects	insightly_projects	Upsert by primary key, incremental on updated-at
delivery milestones	insightly_delivery_milestones	Upsert by primary key, incremental on updated-at

Insightly API: setup facts for the connector

Verified against the vendor documentation on 2026-09-21. Unknown values are left blank rather than guessed.

API	Insightly REST API v3.1
Authentication	API key, HTTP Basic — HTTP Basic Auth with the user's personal API key (from User Settings) as the Base64-encoded username and the password left blank; the base URL is pod-specific, e.g. `https://api.na1.insightly.com/v3.1/`.
Pagination	offset — List endpoints take `skip` and `top` query params; `top` defaults to 100 and is capped at a maximum of 500 records per response.
Rate limit	10 requests per second per instance, plus a rolling 24-hour daily cap by plan: 1,000/day Free, 20,000/day Legacy, 40,000/day Plus, 60,000/day Professional, 100,000/day Enterprise; exceeding either returns HTTP 429
Incremental cursor	DATE_UPDATED_UTC — Search endpoints accept an `updated_after_utc` filter (ISO 8601, e.g. `2018-04-09T16:58:14Z`) that compares against each record's `DATE_UPDATED_UTC` field.
Webhooks	Yes — Workflow Automation Webhooks (Add Webhook action on a workflow rule)
Bulk export	No
Deletes detectable	No — The REST API documents no deleted flag or tombstone on list/search responses; deleted records move to an in-app Recycle Bin not exposed via the API, so detection requires diffing full ID snapshots between syncs.

Official API reference

What bites when replicating Insightly

List/search responses cap `top` at a maximum of 500 records per page (default 100), so large objects like Contacts or Organisations need many chained requests even before hitting the per-second limit.
The per-second ceiling is a strict 10 requests/second per instance on top of the daily plan cap (1,000/day on Free up to 100,000/day on Enterprise), both enforced via `X-RateLimit-Limit`/`X-RateLimit-Remaining` headers and an HTTP 429 on breach.
Workflow Automation Webhooks retry only twice after an initial failed delivery (three attempts total) and then stop sending, so a receiving endpoint that is briefly down can permanently miss an event with no dead-letter recovery.
There is no documented deleted-record flag or tombstone anywhere in the REST API; a connector must maintain its own ID snapshot and diff it against each sync to infer deletions.

Compare this against every other documented API

Popular destinations for Insightly

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Insightly connector FAQ

What Insightly data does the connector extract?: 5 objects: contacts, organizations, opportunities, projects and delivery milestones. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Insightly integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Insightly data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Insightly → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Insightly pipeline with guided onboarding

Join the waitlist to get priority access for Insightly integrations with guided setup, schema-aware mapping, and production-grade incremental sync.