Insightly integration

Insightly lead source, on the right object.

Insightly has a Lead Source field on its Lead object. It holds one picked value. Capture the real source, landing page and full page journey instead, and let Zapier create or update the right Insightly object with the source attached.

Track your Insightly leads free → See the setup
Connects via the Insightly Zapier connector Object-driven: Lead, Contact, Opportunity One line of code
What Insightly captures, and what it misses

Insightly has a Lead Source field. It holds one value.

Insightly pairs a CRM with project delivery, so SMBs that sell and then deliver the work run both in one place. Its Lead object carries a Lead Source field, a single value from a configurable list. It answers the channel question for a pipeline view. It does not record the campaign, the entry page, or the route the lead took before they got in touch.

What the Insightly field holds

A channel from the list

  • A single value: Web, Referral, Event, Other
  • Set on creation, by a form map or a rep
  • Carries into the project, still just a channel
What it leaves out

The detail behind the channel

  • The campaign behind the click
  • The landing page they arrived on
  • The pages they read before submitting, ending on the page that converted them

In plain terms: Lead Source records the source, landing page and journey as the form is submitted, then passes the lead to Zapier so the right Insightly object carries the real story.

How the connection works

Captured on your site. Written into Insightly through Zapier.

Insightly has a live Zapier connector, and it is object-driven: you choose the Insightly object, Lead, Contact or Opportunity, and the action works against that object.

  1. 01
    From the first visit, Lead Source records the real source, campaign, landing page and full page journey.
  2. 02
    On submission, Lead Source keeps the lead in your dashboard and sends it to Zapier.
  3. 03
    Your Zap runs Insightly’s Create Record or Update Record action and you choose the object, usually Lead. You map the captured source into the fields that object exposes.
  4. 04
    The record lands in Insightly with the source set at submission, ready to convert into a project later with the history intact.
The captured record

What lands in Insightly.

Sample data, not a real customer. The shape of the record created when a form is submitted and the Zap fires.

SAMPLE · captured lead → Insightly Lead at submission
Insightly record created
Tom Castellano
PM · Northline Builders
Lead SourceGoogle Ads
campaignCommercial fit-out
landed/commercial
journey/commercial → /projects → /contact
objectLead
Real source on the record, ready to carry into the project.
Safe setup pattern

The setup, end to end.

Only the verified Insightly Zapier actions, run against the object you choose.

01

Add the snippet

Put the Lead Source script in the page head, before the closing </head>, on any page with a form. It records the source, landing page and journey for every visitor.

02

Connect Lead Source to Insightly in Zapier

Create a Zap with Lead Source as the trigger and Insightly’s Create Record or Update Record action as the step. Choose the object, usually Lead.

03

Map the source onto the object

Map the captured source into the Lead Source field, with the campaign and landing page alongside. Send a test submission with a UTM and confirm the record arrives with the real source.

Integration details verified against the Insightly Zapier connector on 30 June 2026. We confirmed the Create Record, Update Record and Find Record actions exist and are object-driven (Lead, Contact, Opportunity and more). We did not verify writes to arbitrary custom fields on standard records.

When this isn’t the right fit

When Insightly isn’t the tool you need.

A couple of cases where this is the wrong fit, put bluntly.

  • You have not decided which object leads should land on. Object-driven actions need you to pick Lead, Contact or Opportunity first.
  • You need the source written to a specific bespoke custom field. We map into the fields the object exposes; arbitrary custom-field writes are not verified.
  • Your leads come in mostly by phone or referral rather than a web form.
Related

Where to go next.

CRM lead source tracking
The pillar guide. How lead source works in every CRM
Every CRM’s source field
How each CRM captures source, side by side
monday CRM
Board-based CRM, also connected via Zapier
Lead source examples
What a captured record looks like, channel by channel
Common questions

Questions, answered.

Does Insightly already track lead source?

Yes. Insightly's Lead object carries a Lead Source field, a single value from a configurable list, so it records the channel only. Lead Source fills it through Zapier with the real source captured at form submission, along with the campaign and landing page.

Which Insightly object do leads land on?

You choose. The Insightly connector is object-driven: the Create Record and Update Record actions let you target the Lead, Contact, or Opportunity object, and the source maps into the fields that object exposes.

Does the captured source carry into the project?

The source lives on the record you create. Because Insightly pairs CRM with project delivery, converting that lead keeps its history, so the project that follows inherits the real source rather than losing it at handover.

See your real Insightly lead sources.

Free to start. Connect Insightly through Zapier in minutes.

Track your Insightly leads free &rarr;

Free to start &middot; no card