Reference · built on requestConnectorCRM & sales

Insightly CRM

Contacts, organisations, leads, opportunities, projects, and tasks from Insightly CRM through the v3.1 REST API.

Request accessPricing ↗

About

Insightly CRM holds contacts, organisations, leads, opportunities, projects, and tasks for sales and delivery teams, plus quotes, products, and price books. The v3.1 REST API exposes each object with GET, POST, PUT, and DELETE, an updated_after_utc filter for incremental reads, and Search endpoints keyed by field name and value. Requests go to the pod your instance runs on, such as api.na1.insightly.com.

Through Fibric, an operator reads pipeline stage, task state, and record dates, then proposes changes: move an opportunity to its next stage, log a note on the contact, or open a task for the owner. You approve it. The connector sends one request to your Insightly instance and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Insightly CRM and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Contacts, Organisations, and Leads through GET /Contacts, /Organisations, and /Leads, with Search endpoints by field_name and field_value
  • Opportunities with their Pipelines and PipelineStages, and quotes through the Quotation and QuotationLineItem endpoints
  • Projects and Milestones, and Tasks with their Comments and Links to other records
  • Notes, Events, and Emails attached to a Contact, Organisation, Opportunity, or Project
  • Records changed since a timestamp through the updated_after_utc filter, paged with top and skip
  • Users, Teams, and Permissions, and the Custom Fields and Custom Objects defined in your instance

Proposed actions

  • Target capability: propose moving an opportunity to a pipeline stage through PUT /Opportunities/{id}/PipelineStage
  • Target capability: propose adding a note through POST /Contacts/{id}/Notes or POST /Opportunities/{id}/Notes
  • Target capability: propose creating or updating a task through POST /Tasks and PUT /Tasks
  • Target capability: propose updating record fields through PUT with the record id and only the fields to change, guarded by If-Match

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Move stalled opportunities

    Opportunities that have not changed stage or been updated within your window are listed with their owner. The operator proposes a task for the owner or a stage move, for approval.

    With Stale Pipeline

  • Answer new leads on time

    New Leads are read on a short schedule. The operator drafts the first reply and proposes a task and a note on the lead so the response is recorded.

    With Lead Response, Duplicate Lead

  • Turn a quote into an order

    When a Quotation is accepted, the operator syncs it to its Opportunity and proposes the order in your commerce or ERP system, with the line items from QuotationLineItem.

    With Quote to Order

  • Hand a won deal to delivery

    On a stage move to won, the operator proposes a Project with tasks from the activity set assigned to the opportunity, so delivery starts from the record sales closed.

    With Deal Handoff

Requirements

  • An Insightly CRM instance and the API key of a user whose permissions cover the records the connector reads
  • The pod your instance runs on, shown in User Settings, to form the base URL such as https://api.na1.insightly.com/v3.1/
  • A plan with enough daily requests for your record volume: Plus 40,000, Professional 60,000, Enterprise 100,000
Authentication
HTTP Basic authentication with a per-user API key from User Settings, Base64-encoded as the username with an empty password.

Limits

  • No more than 10 requests per second; daily request limits depend on plan, and exceeding them returns HTTP 429.
  • The v3.1 API documentation describes no webhooks; the connector reads changes with updated_after_utc on a schedule.
  • A response holds 100 records by default and 500 at most; larger reads page with top and skip.
  • Only application/json is accepted as a content type; responses can be GZIP or DEFLATE compressed.

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Insightly CRM ↗

Questions and answers

Does Insightly CRM send webhooks?
Not in the v3.1 REST API documentation this listing is written from. The connector reads changed records with the updated_after_utc filter on each object and the Search endpoints, paged with top and skip, and keeps within the 10 requests per second limit.
How does the connector avoid overwriting a record someone edits at the same time?
Responses carry an ETag. A PUT can send that value in an If-Match header, and Insightly rejects the update if the record changed in between. PUT also accepts the record id with only the fields to change.
How many requests does a day allow?
The documentation lists 1,000 per day on the free plan, 20,000 on legacy plans, 40,000 on Plus, 60,000 on Professional, and 100,000 on Enterprise, with a ceiling of 10 per second. Over the limit, requests return HTTP 429 until the window resets.
Ask about Insightly CRM

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Insightly CRM through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy