Linking Insightly as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
This source is currently in alpha. The interface and available tables may change.
The Insightly connector syncs contacts, organisations, opportunities, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Insightly API key to sync your Insightly CRM data.
Find your API key and your API URL in Insightly under User Settings (top-right profile menu). The API URL looks like https://api.na1.insightly.com/v3.1 - the pod is the region token in the middle (na1, eu1,...). Enter just that token, or paste the full API URL.
The API key inherits your Insightly user's permissions, so make sure your user can access the data you want to sync.
You'll be asked for:
- Pod (instance): for example
na1. - API key
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Some Insightly tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
Pod (instance) | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Contacts | People tracked in Insightly, with their contact details and relationships. | Incremental, Full refresh | DATE_UPDATED_UTC | CONTACT_ID |
Organisations | Companies and organisations tracked in Insightly. | Incremental, Full refresh | DATE_UPDATED_UTC | ORGANISATION_ID |
Opportunities | Sales opportunities (deals) tracked through your pipelines. | Incremental, Full refresh | DATE_UPDATED_UTC | OPPORTUNITY_ID |
Leads | Unqualified prospects that can be converted into contacts, organisations, and opportunities. | Incremental, Full refresh | DATE_UPDATED_UTC | LEAD_ID |
Projects | Projects used to manage post-sale work and deliverables. | Incremental, Full refresh | DATE_UPDATED_UTC | PROJECT_ID |
Tasks | To-do items assigned to users and linked to CRM records. | Incremental, Full refresh | DATE_UPDATED_UTC | TASK_ID |
Events | Calendar events and appointments. | Incremental, Full refresh | DATE_UPDATED_UTC | EVENT_ID |
Notes | Free-text notes attached to CRM records. | Incremental, Full refresh | DATE_UPDATED_UTC | NOTE_ID |
Emails | Emails logged against CRM records. | Incremental, Full refresh | DATE_UPDATED_UTC | EMAIL_ID |
Users | Insightly users in your account. | Full refresh | — | USER_ID |
Pipelines | Sales/project pipelines used to organise opportunities and projects into stages. | Full refresh | — | PIPELINE_ID |
PipelineStages | Stages within each pipeline, marking how far an opportunity or project has progressed. | Full refresh | — | STAGE_ID |
LeadSources | Lead source values defined for your Insightly account, referenced by LEAD_SOURCE_ID on leads. | Full refresh | — | LEAD_SOURCE_ID |
LeadStatuses | Lead status values defined for your Insightly account, referenced by LEAD_STATUS_ID on leads. | Full refresh | — | LEAD_STATUS_ID |
OpportunityLineItem | Products on an opportunity, with quantity, pricing, and discount. | Incremental, Full refresh | DATE_UPDATED_UTC | OPPORTUNITY_ITEM_ID |
Ticket | Insightly Service support tickets raised by contacts. | Incremental, Full refresh | DATE_UPDATED_UTC | TICKET_ID |
Quotation | Quotes sent for opportunities, with their totals, status, and addresses. | Incremental, Full refresh | DATE_UPDATED_UTC | QUOTE_ID |
QuotationLineItem | Products on a quote, with quantity, pricing, and discount. | Incremental, Full refresh | DATE_UPDATED_UTC | QUOTATION_ITEM_ID |
Product | Products in your Insightly catalog, referenced by PRODUCT_ID on price book entries. | Incremental, Full refresh | DATE_UPDATED_UTC | PRODUCT_ID |
Pricebook | Price books that group product prices, for example per currency or market. | Incremental, Full refresh | DATE_UPDATED_UTC | PRICEBOOK_ID |
PricebookEntry | The price of a product in a price book, referenced by PRICEBOOK_ENTRY_ID on opportunity and quote line items. | Incremental, Full refresh | DATE_UPDATED_UTC | PRICEBOOK_ENTRY_ID |
OpportunityStateHistory | History of state changes (for example open, won, lost, abandoned) for each opportunity, with the reason given. | Full refresh | — | OPPORTUNITY_ID, DATE_CHANGED_UTC, FOR_OPPORTUNITY_STATE |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.