CRM integration guide
Insightly + UbiGrowth workflows
Insightly is a CRM that combines pipeline management with project delivery, so the same record carries a deal and the work that follows it. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Insightly part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a CRM workflow around Insightly with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Contact, Organisation, Opportunity, Project, Task, and Pipeline. Insightly carries both Opportunity and Project against the same Organisation, and the handoff between them is where records diverge: a won Opportunity does not automatically become the Project that delivers it.
Insightly is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
The recurring failure with a Insightly integration is not connectivity. It is that the CRM ends up holding a record of what someone remembered to log, while the work itself happened in an inbox, a call, a spreadsheet, and a separate AI tool that never saw the account.
When that gap exists, everything built on top of it inherits it. Forecasts describe logged activity rather than real activity, outreach is written without the reply history that would make it relevant, and the team spends its day reconciling systems instead of working accounts.
You're likely here because
- Pipeline data is only as current as the last time someone logged activity
- Outreach is generated without the account history that would ground it
- The same account context is rebuilt in several tools each day
Record model
What a Insightly integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Insightly's.
Identity and matching
Insightly carries both Opportunity and Project against the same Organisation, and the handoff between them is where records diverge: a won Opportunity does not automatically become the Project that delivers it.
Start here
Detect won Opportunities with no linked Project after a defined interval and stage the delivery handoff with the sold scope attached.
What this will not do
It will not manage delivery. Insightly tracks that project work exists; the operating detail lives in whatever the delivery team actually uses.
The constraint to plan around
Pipelines and Activity Sets are configured per instance and referenced by id, so a workflow written against one Insightly account will not transfer without remapping.
Build notes
What you actually have to reason about in Insightly.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| PIPELINE_ID / STAGE_ID | both configured per instance and referenced by numeric id, so nothing transfers between accounts |
| OPPORTUNITY_STATE | open, won, abandoned, or suspended — four states where most CRMs have three |
| PROJECT_ID | the delivery link, and the field that is null exactly when the sales-to-delivery handoff failed |
| ACTUAL_CLOSE_DATE | distinct from the forecast date, which is what makes slippage measurable here |
| CATEGORY_ID | segmentation that reporting depends on and that nothing enforces at entry |
Authentication
API key over HTTP Basic, tied to a user and therefore to that user's permissions. The key appears in the request rather than in a token exchange, which makes rotation a deliberate act nobody schedules by default.
Events and delivery
Webhook support is limited compared with larger CRMs, so most integrations here are poll-based against the updated timestamp. Design for polling from the start rather than discovering it after building for events.
Workflow
How the Insightly workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read the pipeline as it stands
The workflow starts from live Insightly accounts, contacts, and opportunities rather than an export, so prioritization reflects today's pipeline.
Step 02
Assemble the account context
Reply history, documents, and prior activity are brought together so the next action is grounded in what actually happened with the account.
Step 03
Decide the next action
ARIA proposes the specific next step for the account, with the supporting context attached, instead of producing a message with no stated reason.
Step 04
Execute through Grow
Outreach, reply handling, and scheduling run against the same record, staged for review while the motion is being proven.
Design decisions
The CRM decisions this connection forces.
Each of these has to be settled before the Insightly workflow is allowed to write anything.
Step 01
Resolve the account identity
Decide how a person and a company are matched between Insightly and the rest of the stack before any write happens. Most CRM integration damage is duplicate records created by a weak match rule.
Step 02
Keep execution attached to the opportunity
Outreach, replies, meetings, and stage changes should resolve back to the same opportunity, so the CRM reflects what actually happened rather than a parallel activity log.
Implementation path
How to implement the Insightly workflow.
- 01
Decide which fields Insightly owns and which the workflow may write, and write that decision down before enabling anything.
- 02
Define the identity match rule for contacts and companies, including what happens on an ambiguous match.
- 03
Start read-only. Prove that the workflow reads the right records before it is allowed to change any of them.
- 04
Once the handoff gap is visible, extend into delivery: surface projects whose scope no longer matches what was sold.
Governance
Controls that matter.
Control 01
CRM write scopes are limited to the specific objects the workflow needs, never blanket admin access.
Control 02
Duplicate creation is treated as a defect, not an acceptable side effect of syncing.
Control 03
Stage changes and closed-won updates stay under human control; automation prepares them rather than deciding them.
Failure modes
How a Insightly integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Opportunities are created into the wrong pipeline.
Cause
Pipeline and stage are numeric ids that differ per instance and the write still succeeds.
Fix
Resolve pipeline and stage by name at startup and refuse to run if either does not resolve.
Symptom 02
Won deals never produce a delivery project.
Cause
The Opportunity-to-Project handoff is manual and nothing enforces it.
Fix
Detect won opportunities with no linked project after a defined interval and route the gap, rather than assuming the link.
Symptom 03
Incremental sync misses records.
Cause
Polling on an updated timestamp without overlap loses records modified during the query window.
Fix
Overlap the window and deduplicate on id, which is cheaper than the records you would otherwise miss.
What changes at scale
API limits are per instance and modest, so polling frequency is the constraint. Batch reads and a generous poll interval scale better than near-real-time ambitions here.
Examples
What a working Insightly workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Pipeline operations
With Insightly connected, ARIA works from live account, contact, and opportunity records instead of an export, so prioritization reflects the pipeline as it stands today.
Grounded outbound
Grow drafts outreach against the account history already in Insightly, so the message references what actually happened with the account rather than a generic template.
Limitations and considerations
What to validate before you depend on this.
- Pipelines and Activity Sets are configured per instance and referenced by id, so a workflow written against one Insightly account will not transfer without remapping.
- Writing an Opportunity into the wrong pipeline is easy because ids are numeric and instance-specific, and the record still saves. The stage then means something different from what the report assumes.
- When the project side is the real requirement. Insightly tracks that delivery exists; a team whose constraint is delivery execution needs a system built for it.
- If Insightly data is incomplete, the workflow inherits that gap. Connected context is not automatically accurate context.
- Custom objects, custom fields, and heavily-customized permission models change what an integration can safely do; validate them against your own instance rather than the vendor default.
FAQ
Insightly integration questions.
What records does a Insightly integration actually work with?
The primary records are Contact, Organisation, Opportunity, Project, Task, and Pipeline. Insightly carries both Opportunity and Project against the same Organisation, and the handoff between them is where records diverge: a won Opportunity does not automatically become the Project that delivers it.
What should the first Insightly workflow be?
Detect won Opportunities with no linked Project after a defined interval and stage the delivery handoff with the sold scope attached.
What will a Insightly integration not do?
It will not manage delivery. Insightly tracks that project work exists; the operating detail lives in whatever the delivery team actually uses.
What is the main constraint to plan around?
Pipelines and Activity Sets are configured per instance and referenced by id, so a workflow written against one Insightly account will not transfer without remapping.
What changes about a Insightly integration at scale?
API limits are per instance and modest, so polling frequency is the constraint. Batch reads and a generous poll interval scale better than near-real-time ambitions here.
How does authentication work for Insightly?
API key over HTTP Basic, tied to a user and therefore to that user's permissions. The key appears in the request rather than in a token exchange, which makes rotation a deliberate act nobody schedules by default.
Does Insightly support webhooks, and can they be trusted?
Webhook support is limited compared with larger CRMs, so most integrations here are poll-based against the updated timestamp. Design for polling from the start rather than discovering it after building for events.
What is the risk of writing to Insightly?
Writing an Opportunity into the wrong pipeline is easy because ids are numeric and instance-specific, and the record still saves. The stage then means something different from what the report assumes.
When is connecting Insightly the wrong call?
When the project side is the real requirement. Insightly tracks that delivery exists; a team whose constraint is delivery execution needs a system built for it.
What should a Insightly integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Insightly to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Will this create duplicate records in Insightly?
Only if the identity match rule is weak. Define how people and companies are matched, and how ambiguous matches are handled, before enabling any write path.
Does Insightly stay the system of record?
Yes. The design assumption is that Insightly remains authoritative for the objects it owns and the workflow builds around it rather than replacing it.
Can pipeline stages be updated automatically?
Stage progression should stay under human control. Automation can prepare and propose the update, but deciding that a deal moved is a judgment call.
How this access is governed
What ARIA is allowed to do in Insightly, and who decides.
Connecting Insightly is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.