Keap Integration

How LeadSync Pushes Leads into Keap Contacts

Keap (formerly Infusionsoft) organises customer data into Contacts, applies Tags to drive segmentation, and runs Campaigns -- multi-step automations that fire when a contact gets tagged. LeadSync connects via OAuth, stores a long-lived token pair, and uses Keap's XML-RPC contact API to either create a new Contact or update an existing one for each Facebook, Google, LinkedIn, or TikTok lead.

On lead arrival, LeadSync first calls findByEmail against the Keap contact store. If the email already exists, the integration honours the connection's existed setting: update overwrites the contact's mapped fields with the latest values, and skip declines the duplicate so an existing nurture sequence is not interrupted. New emails create a fresh Contact via the add call.

Tags Trigger Keap Campaigns Automatically

Keap Campaigns are tag-driven -- the entry condition for almost every Campaign is "Contact gets tagged with X". LeadSync supports applying multiple Keap Tags per connection: when a lead lands, the integration calls contacts.addToGroup for each Tag ID configured, and Keap's Campaign engine takes over from there.

For new contacts (not updates), LeadSync also calls emails.optIn with the reason "Contact gave explicit permission" -- which is what Keap expects for paid-social leads who consented via the Facebook lead form. This unlocks email sends through Keap Broadcasts and any email step inside your Campaign sequences. Without explicit opt-in, Keap silently suppresses email steps.

Custom Fields and the 70+ Standard Field Set

Keap has a deep standard contact schema -- 70+ fields covering Phone1 through Phone5 (each with a type), Email, EmailAddress2, EmailAddress3, full address blocks (Address1/2/3), Company, JobTitle, SpouseName, ContactNotes, LeadSourceId, Birthday, Anniversary, and dozens more. The LeadSync field mapping screen lists the full set so you can match lead form questions to whichever Keap field your downstream workflow uses for segmentation or merge-tag personalisation.

Custom fields you have defined in Keap (Settings › Custom Fields) appear alongside the standard fields automatically -- LeadSync queries DataFormField at mapping time to pick them up. Map a lead form question to a Keap custom field once, and every lead through that connection populates the field for use in Campaign decisions or email merge tags.

Frequently Asked Questions

Click Keap in the LeadSync destination list and complete the OAuth flow -- LeadSync redirects to Keap, you authorise, and on return LeadSync stores the token pair. Keap tokens auto-refresh, so you authenticate once and the integration runs indefinitely. No API keys to copy.

Yes. Configure your LeadSync connection to apply the Tag that starts your Campaign. Every lead synced through that connection gets the Tag applied via Keap's addToGroup endpoint, which fires the Campaign immediately. This is the standard pattern for paid-social welcome and nurture sequences in Keap.

Yes. The connection settings let you specify multiple Tag IDs. All Tags are applied to the Contact when LeadSync creates or updates them, which is useful when you want one Tag to trigger a welcome Campaign and another Tag to drop the lead into a sales-team segment for follow-up.

LeadSync calls findByEmail first and honours the connection's "if exists" setting. Update mode overwrites the matching Contact with the latest field values; skip mode declines the duplicate so an existing nurture is not disrupted. Pick whichever fits your re-engagement strategy.

Yes -- for new Contacts only. LeadSync calls Keap's emails.optIn with reason "Contact gave explicit permission", which is what Keap expects for paid-social leads who consented via the lead form. Without explicit opt-in, Keap suppresses email sends including Broadcasts and Campaign email steps.

Over 70 standard fields are available -- Phone1 through Phone5 (with type sub-fields), Email plus two alternates, address blocks, Company, JobTitle, SpouseName, ContactNotes, LeadSourceId, Birthday, Anniversary, and many more. Custom fields you have defined in Keap appear alongside the standard set automatically.

LeadSync queries DataFormField when you open the mapping screen, so any custom field you have defined in Keap (Settings > Custom Fields) appears in the dropdown next to the standard fields. Map a lead form question to it once, and the value flows into Keap on every new lead through that connection.

Yes. Create one LeadSync connection per source and configure different Tags on each. Facebook leads can get tagged "fb-paid-social" while LinkedIn leads get tagged "linkedin-b2b" -- each Tag triggers its own Campaign with channel-specific copy.

Yes. LeadSync supports Keap as a destination for lead forms from Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own connection.

Yes. Keap Pro and Keap Max accounts use the same XML-RPC and REST APIs that Infusionsoft used before the 2019 rebrand. The contact schema, Tag system, and Campaign engine are unchanged, so existing customers do not need to re-do their LeadSync setup.

Available Integrations

How It Works

How LeadSync Pushes Leads into Keap Contacts

Tags Trigger Keap Campaigns Automatically

Custom Fields and the 70+ Standard Field Set

Frequently Asked Questions

Start Syncing Leads to Keap