Ketch and Insightly

Set Insightly's own opt-out field directly, verifiable right on the contact's profile, rather than a separate consent record disconnected from the CRM itself.

Insightly

About Insightly

Insightly combines CRM and project management for small and medium-sized businesses, tracking leads, contacts, opportunities, and projects in one platform. Because Insightly already has a native email opt-out field on Contact and Lead records, the most reliable way to enforce consent there is to set that field directly, rather than maintaining a parallel consent record Insightly's own systems and integrations never see.

Ketch connects to Insightly to do exactly that.

Capabilities

How Ketch works with Insightly

The Ketch Insightly integration covers Consent Orchestration and Rights Orchestration (Right to Deletion, Right to Access).

Consent Orchestration

Sets Insightly's own opt-out parameter to true or false directly on the Contact or Lead record, based on a person's actual preferences; this can be verified visually right on the contact's profile, where the Email Opted Out field reflects the current state.

Rights Orchestration

Right to Access returns the full information stored about a Contact or Lead, including custom fields, tags, and linked relationships. Right to Delete removes the Contact or Lead from the connected Insightly instance.

With Ketch, teams can

  • Set Insightly's native email opt-out field directly, verifiable on the contact's own profile rather than in a separate system
  • Fulfill Right to Access and Right to Delete requests against Contact and Lead records, including custom fields and relationship links
  • Confirm both rights and consent changes visually against the Insightly UI as part of standard validation

The gap

The problem this integration solves

A CRM that already has its own opt-out field only benefits from that field if something actually keeps it in sync with real consent decisions:

01. A consent record that lives outside Insightly has no effect on Insightly's own opt-out field, which is what Insightly's own workflows and integrations actually read

02. Manually updating the opt-out field for every consent change doesn't scale to real preference volume

03. Access requests that don't cover custom fields, tags, and relationship links miss real personal data that lives on those parts of the record

Ketch resolves this by writing directly to Insightly's own opt-out field on every consent change, and by returning the full Contact or Lead record, custom fields and relationships included, on an access request.

Why Ketch

Why teams choose Ketch for Insightly privacy compliance

Permissioning infrastructure that governs Insightly the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.

  • Sets Insightly's own field, not a parallel record

    Consent Orchestration writes directly to the Email Opted Out parameter Insightly's own systems already read.

  • Access requests that cover the full record

    Custom fields, tags, and relationship links come back alongside standard contact data.

  • Backed by enforcement precedent

    The California Attorney General reached a $1.55 million settlement with Healthline Media over sharing sensitive data with advertisers without valid consent, a reminder that CRM platforms carry real exposure when a consent choice doesn't actually reach the field governing outreach.

Questions about the Insightly integration

Integrations

Pre-built APIs with 1,000+ systems, apps, and models

Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.

Browse All Integrations

See Insightly permissioning running end to end

Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Insightly yourself.

Get Started Free

Get started in less than 5 min