Insightly integration

Insightly lead source, on the right object.

The Lead object in Insightly has a built-in Lead Source field that keeps one choice from a list. Lead Source reads the real channel, entry page and page path as the form goes in. A Zap then creates or updates the object you picked, Lead, Contact or Opportunity, with all of it on board.

Connects via the Insightly Zapier connector Object-driven: Lead, Contact, Opportunity One line of code
Salesforce
HubSpot
Pipedrive
Gmail
Twilio
Google Ads
Gravity Forms
Jotform
Webflow
Wix
Calendly
Typeform
What Insightly captures, and what it misses

The Insightly Lead object keeps one source value.

Insightly is a CRM and a project tool in one, built for small firms that win the job and then do the job. On the Lead object, that field takes one pick from a list you can configure. That is enough to group a pipeline view by channel. The campaign, the entry page and everything browsed ahead of the enquiry have nowhere to go.

What the Insightly field holds

A channel from the list

  • A single value: Web, Referral, Event, Other
  • Chosen when the Lead is saved, by a form or by hand
  • Carries into the project, still just a channel
What it leaves out

What the pick cannot say

  • The ad campaign that paid for the visit
  • The landing page they arrived on
  • The pages they read before submitting, ending on the page that converted them

Lead Source takes the channel, entry page and path at the moment the enquiry form is sent. Zapier files them on the Insightly object you chose, and they stay there when the Lead becomes a project.

How the connection works

Taken at your form. Filed on an Insightly object by Zapier.

The Insightly app on Zapier is live and works by object. Choose Lead, Contact or Opportunity first. Every action after that runs against the one you chose.

  1. 01
    Someone arrives from a Google Ads click on a fit-out campaign. Lead Source notes the channel, the campaign, their first page and each page they open next.
  2. 02
    They send the enquiry. Lead Source keeps the lead for your dashboard and hands it over to Zapier.
  3. 03
    The Zap runs Create Record, or Update Record for someone already on file, against the object you set. For most firms that is Lead. The captured values go into whichever fields that object lists.
  4. 04
    The Lead is in Insightly with its source filled. Win the work, convert it to a project, and the history comes along.

A Lead Source field waits for someone to choose

Insightly holds the field open. Lead Source chooses for it at the form, while the visitor is still on the page and the answer still exists.

Start free →
The captured record

What lands in Insightly.

A sample Insightly Lead, as one enquiry and one Zap run produce it.

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

Install the script once

Any page with an enquiry form needs the Lead Source script in its head, just above </head>. From then on, each visit's channel, entry page and path are noted.

02

Connect Lead Source to Insightly in Zapier

In Zapier, Lead Source is the trigger. For the action, take Insightly Create Record or Update Record, then set the object. Lead is the usual answer.

03

Match fields on your chosen object

Send the captured source to Lead Source on that object and put the campaign and entry page in the fields beside it. Then fill in your own enquiry form with a UTM on the link and look at the new Lead in Insightly.

Checked against the Insightly app on Zapier, 30 June 2026. Create Record, Update Record and Find Record are all there, each run against an object: Lead, Contact, Opportunity and others. Writes to arbitrary custom fields on standard records were not part of the check.

When this isn’t the right fit

When Insightly isn’t the tool you need.

Three cases to rule out first, stated flatly.

  • You have not decided which object leads should land on. Object-driven actions need you to pick Lead, Contact or Opportunity first.
  • The source must go into a custom field someone added to the Lead object. We write to the fields the object lists, and arbitrary custom-field writes are unchecked.
  • Most of your work arrives by phone or word of mouth, never through a form on your site.
Common questions

Questions, answered.

Does Insightly already track lead source?

Yes, on the Lead object, as one pick from a configurable list. That pick is a channel and no more. Lead Source sets it through a Zap from what it read as the enquiry was sent, and passes the campaign and entry page across with it.

Which Insightly object do leads land on?

Whichever you pick. In Zapier, Create Record and Update Record ask for an object first: Lead, Contact or Opportunity. The source then goes into the fields that object offers.

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 →

Free to start · no card