CRM

Insightly

Pull Insightly lead statuses and opportunity stages into OrcLink outcomes, matched back to the ad click.

Built, not yet tested liveBuilt. Not yet tested against a live Insightly account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

Dashboard > Integrations > Insightly: paste Insightly API key (put your pod first if your API URL has one, like na1:KEY), then Connect. It is stored encrypted and never shown again.
Paste your Insightly API key, with your pod first if your API URL has one (na1:KEY).

What OrcLink reads

Lead statuses and opportunity stages, every 10 minutes while the scheduled jobs crm-sync and jobs run (your OrcLink operator schedules them).

What OrcLink writes back

Nothing. You create the text custom field "OrcLink_Click_Id" on Leads (and Opportunities).
Write-back of source and campaign to Insightly: not available yet.

Never stored

Raw email addresses and phone numbers: hashed (SHA-256) the moment they arrive.
The raw payload: only its SHA-256, for provenance.
Your credentials and webhook secrets in clear: they are stored encrypted (AES-256-GCM).

Known limits

Matching needs the OrcLink click id (olid) in a CRM field, filled from the hidden form field named olid; without it OrcLink matches by the hashed email or phone of a lead an earlier visit tied to a click.
A very large first import can stop at the page budget; the settings page says so (upload the history as a CSV instead).