Insightly

Insightly

CRM platform managing the full sales and project lifecycle. Customer data lives on regional pods; the connection pins the active pod automatically.

Entity Hierarchy

Core CRM

• Contacts — people. Each has integer CONTACT_ID, FIRST_NAME, LAST_NAME, EMAIL_ADDRESS, PHONE, TITLE. Linked to organizations via ORGANISATION_ID. Create, read, update, and delete supported.
• Organisations — companies. ORGANISATION_ID, ORGANISATION_NAME, PHONE, WEBSITE, BACKGROUND. Create, read, update, and delete supported.
• Opportunities — sales deals in pipelines. OPPORTUNITY_ID, OPPORTUNITY_NAME, PIPELINE_ID, STAGE_ID, PROBABILITY (0-100), BID_AMOUNT, BID_CURRENCY, FORECAST_CLOSE_DATE. Create, read, update, and delete supported.
• Notes — text notes linked to any record via NOTELINKS (CONTACT, ORGANISATION, OPPORTUNITY, PROJECT, TASK). NOTE_ID, TITLE, BODY. Create/update supported.

Project Management

• Projects — managed projects. PROJECT_ID, PROJECT_NAME, PIPELINE_ID, STAGE_ID, STATUS (NOT_STARTED/IN_PROGRESS/COMPLETED/DEFERRED/ABANDONED). Create, read, update, and delete supported.
• Tasks — actionable items. TASK_ID, TITLE, DUE_DATE, PRIORITY (1-4), STATUS (NOT_STARTED/IN_PROGRESS/COMPLETED/DEFERRED/WAITING), DETAILS, RESPONSIBLE_USER_ID. Create, read, update, and delete supported.
• Milestones — project milestones with deadlines.
• Events — calendar events with time, description, participants.

Sales Pipeline

• Pipelines — sales or project workflow definitions.
• Pipeline Stages — stages within pipelines (ordered steps).
• Prospects — leads before conversion to contacts/opportunities.
• Lead Sources — attribution channels (web, referral, etc).
• Lead Statuses — lifecycle stages for leads.
• Opportunity Categories — deal classification.
• Opportunity State Reasons — why deals are won/lost/open.

Reference & Config

• Countries, Currencies — reference lookups for forms and records.
• Activity Sets — predefined activity templates for recurring tasks.
• Relationships — links between contacts and organisations.
• Task Categories — task classification.
• Knowledge Articles — help/knowledge base content, organized by categories and folders.
• Teams, Team Members, Users — organizational structure and access.

Workflows

1. Contact management: Enumerate contacts → create new contact (name, email, org link) → update fields → add notes.
2. Deal pipeline: Enumerate pipelines and stages → create opportunity (name, pipeline, stage, probability, amount) → update stage as deal progresses → close (update stage to won/lost).
3. Project tracking: Create project → assign pipeline/stage → create tasks with due dates and owners → update task status → add milestones.
4. Account deep-dive: Enumerate organisations → enumerate contacts (filter by org) → enumerate opportunities for that org → pull notes and emails for context.
5. Lead-to-deal: Enumerate prospects → qualify → create contact + organisation → create opportunity in pipeline.

Pagination

Lists are offset-based: cap each batch (≤500 rows typical), advance with a skip offset, and ask for total counts when you need to know full list size up front.

Gotchas

• All entity IDs are integers, not UUIDs or strings.
• Field names in payloads are UPPER_SNAKE_CASE: FIRST_NAME, CONTACT_ID, ORGANISATION_NAME, etc.
• Partial updates: Only send the entity key plus fields you are changing; other fields stay as-is.
• Pod-specific hosting: Same org can live on different regional pods—the connection carries the right host.
• Rate limits: About 10 ops/sec with plan-based daily caps; slow down when throttling responses appear.
• Search-style lists: Field-based search accepts name/value pairs instead of free text—match the declared filter schema for that read.
• Dates: Bodies use yyyy-MM-dd HH:mm:ss (UTC); range filters follow the parameter format for that query.