Skip to main content

CRM & Marketing Integrations

What Are Integrations?โ€‹

Integrations let LeadHub push leads into the other tools your business uses. When a new lead arrives in LeadHub, the integration automatically creates or updates the matching record in your CRM, email marketing tool, spreadsheet, or messaging platform.

Think of it this way: LeadHub is the front door โ€” every lead arrives here first, no matter where it came from. Integrations are the pipes that send those leads to wherever your team does its work.

Why use integrations? You might already have HubSpot or Mailchimp or a Google Sheet that your sales team lives in. Rather than forcing everyone to switch to LeadHub, you can keep your existing tools and have LeadHub automatically feed them. No manual exporting, no copy-pasting.


Supported Integrationsโ€‹

LeadHub supports 37 integrations across five categories.

Automation Platformsโ€‹

These platforms connect LeadHub to thousands of other apps via no-code workflows.

IntegrationWhat it does
ZapierSends leads to 5,000+ apps via Zapier webhook triggers
Make (Integromat)Connect to Make webhook modules
n8nAutomate workflows with n8n webhook nodes
Pabbly ConnectSend leads to Pabbly Connect workflows
ActivepiecesTrigger Activepieces flows on new leads
WorkatoSend leads to Workato automation recipes

CRM Systemsโ€‹

These integrations create or update contact/lead records in your CRM.

IntegrationWhat it does
HubSpot CRMCreates/updates Contacts and Deals in HubSpot
SalesforcePushes leads as Salesforce Leads or Contacts
PipedriveCreates Persons and Deals in Pipedrive
Zoho CRMCreates Leads in Zoho CRM
FreshsalesCreates Contacts and Deals in Freshsales
Monday.comCreates Items in Monday.com boards
Copper CRMCreates Leads/Persons in Copper
Close CRMCreates Leads and Contacts in Close
StreakCreates Boxes in Streak pipelines (Gmail CRM)
InsightlyCreates Leads or Contacts in Insightly
Bitrix24Creates CRM Leads in Bitrix24
SugarCRMCreates Lead records in SugarCRM
VtigerCreates Lead records in Vtiger
IntercomCreates/updates Contacts in Intercom
ZendeskCreates Tickets or Contacts in Zendesk

Email Marketing Platformsโ€‹

These integrations subscribe the lead to your email lists.

IntegrationWhat it does
MailchimpSubscribes leads to Mailchimp audiences
ActiveCampaignAdds contacts to ActiveCampaign lists
KlaviyoAdds profiles to Klaviyo lists
Brevo (Sendinblue)Creates/updates Brevo contacts
ConvertKitSubscribes leads to ConvertKit sequences
DripCreates/updates subscribers in Drip
GetResponseAdds contacts to GetResponse lists
MoosendSubscribes leads to Moosend mailing lists
MailerLiteAdds subscribers to MailerLite groups

Communication and Messagingโ€‹

These integrations send notifications or messages when a lead arrives.

IntegrationWhat it does
SlackPosts lead cards to Slack channels
Microsoft TeamsPosts lead cards to Teams channels
TwilioSends SMS notifications via Twilio
Vonage/NexmoSends SMS notifications via Vonage

Data and Productivity Toolsโ€‹

These integrations put lead data into databases and spreadsheets.

IntegrationWhat it does
Google SheetsAppends lead data as new rows in a Google Sheet
NotionCreates pages in Notion databases
AirtableCreates records in Airtable bases
Generic WebhookSends leads to any URL with a custom JSON payload
REST API PushPOSTs lead data to a REST API endpoint

Creating an Integrationโ€‹

  1. Go to Integrations > Integrations in the left sidebar.
  2. Click New Integration.
  3. Choose the integration type from the dropdown (e.g. HubSpot, Mailchimp, Google Sheets).
  4. Give it a Name (e.g. "HubSpot โ€“ Main Account" or "Mailchimp โ€“ Newsletter List").
  5. Fill in the required credentials for the integration type (see below).
  6. Toggle Enabled on.
  7. Click Create.

The integration is now active. Every time a new lead is created or updated in LeadHub, it will be pushed to the connected platform.


Credentials Required by Integration Typeโ€‹

Webhook-Based Integrations (Zapier, Make, n8n, Pabbly, Activepieces, Workato, Bitrix24)โ€‹

  • Webhook URL โ€” paste the webhook URL from the automation platform

Slackโ€‹

  • Webhook URL โ€” the Incoming Webhook URL from your Slack workspace
  • Message Template โ€” optional custom message using placeholders like {{lead.email}}, {{lead.first_name}}, etc.

Microsoft Teamsโ€‹

  • Webhook URL โ€” the Incoming Webhook URL from your Teams channel
  • Message Template โ€” optional custom message

HubSpot CRMโ€‹

  • OAuth Connection โ€” click "Connect via OAuth" to authorize (see OAuth section below), or enter an Access Token manually
  • OAuth Client ID and OAuth Client Secret โ€” from your HubSpot developer app
  • Create Deal on Sync โ€” choose Yes/No
  • Deal Pipeline ID and Deal Stage ID โ€” optional, to place deals in a specific pipeline

Salesforceโ€‹

  • OAuth Connection โ€” click "Connect via OAuth" to authorize, or enter credentials manually
  • Instance URL โ€” your Salesforce org URL, e.g. https://yourorg.salesforce.com
  • Object Type โ€” Lead or Contact

Pipedriveโ€‹

  • API Key โ€” from your Pipedrive account settings

Zoho CRMโ€‹

  • OAuth Connection โ€” click "Connect via OAuth" to authorize
  • Region โ€” your Zoho region (com, eu, in, or com.au)

Freshsalesโ€‹

  • API Key โ€” from your Freshsales account
  • Subdomain โ€” your Freshsales subdomain, e.g. yourcompany
  • Create Deal on Contact Sync โ€” Yes/No

Monday.comโ€‹

  • API Key โ€” from your Monday.com account
  • Board ID โ€” the ID of the board where items should be created

Copper CRMโ€‹

  • API Key โ€” from your Copper account
  • User Email โ€” the email address of your Copper account

Close CRM / Insightlyโ€‹

  • API Key โ€” from your Close or Insightly account

Streakโ€‹

  • API Key โ€” from your Streak account
  • Pipeline Key โ€” the key of the Streak pipeline to create boxes in

SugarCRM / Vtigerโ€‹

  • Access Token โ€” from your SugarCRM or Vtiger instance
  • Instance URL โ€” the URL of your CRM instance

Mailchimpโ€‹

  • API Key โ€” from your Mailchimp account
  • Audience ID โ€” the ID of the list/audience to subscribe leads to
  • Data Center โ€” your Mailchimp data center, e.g. us1
  • Tags โ€” optional comma-separated tags to apply in Mailchimp

ActiveCampaignโ€‹

  • API Key โ€” from your ActiveCampaign account
  • API URL โ€” your ActiveCampaign API URL, e.g. https://youraccount.api-us1.com
  • List ID โ€” optional, to add contacts to a specific list

Klaviyoโ€‹

  • Private API Key โ€” from your Klaviyo account
  • List ID โ€” optional, to add profiles to a specific list

Brevoโ€‹

  • API Key โ€” from your Brevo account
  • List ID โ€” optional

ConvertKitโ€‹

  • API Key (Public) โ€” from your ConvertKit account
  • Form / Sequence ID โ€” the ID of the form or sequence to subscribe to

Dripโ€‹

  • API Token โ€” from your Drip account
  • Account ID โ€” your Drip account ID

GetResponseโ€‹

  • API Key โ€” from your GetResponse account
  • Campaign ID โ€” optional, the ID of the campaign to add contacts to

Moosendโ€‹

  • API Key โ€” from your Moosend account
  • Mailing List ID โ€” optional

MailerLiteโ€‹

  • API Key โ€” from your MailerLite account
  • Group ID โ€” optional, the ID of the group to add subscribers to

Twilioโ€‹

  • Account SID โ€” from your Twilio account
  • Auth Token โ€” from your Twilio account
  • From Number โ€” the Twilio phone number to send SMS from
  • SMS Template โ€” message text using {{lead.first_name}}, {{lead.email}}, etc.

Vonage/Nexmoโ€‹

  • API Key and API Secret โ€” from your Vonage account
  • From Number โ€” your Vonage number
  • SMS Template โ€” message text

Intercomโ€‹

  • Access Token โ€” from your Intercom developer app

Zendeskโ€‹

  • Subdomain โ€” your Zendesk subdomain, e.g. yourcompany
  • Admin Email โ€” your Zendesk admin email
  • API Token โ€” from your Zendesk account
  • Create as Ticket or Contact โ€” choose whether to create a ticket or an end-user contact

Google Sheetsโ€‹

  • OAuth Connection โ€” click "Connect via OAuth" to authorize
  • Spreadsheet ID โ€” the ID from the Google Sheets URL
  • Sheet Name โ€” the tab name within the spreadsheet, e.g. Sheet1

Notionโ€‹

  • Integration Token โ€” from your Notion integration settings
  • Database ID โ€” the ID of the Notion database to create pages in
  • Property Mapping โ€” optional JSON to map lead fields to Notion properties

Airtableโ€‹

  • Personal Access Token โ€” from your Airtable account
  • Base ID โ€” the ID of your Airtable base
  • Table Name โ€” the name of the table to create records in

Generic Webhook / REST API Pushโ€‹

  • Webhook URL โ€” the URL to send data to
  • HTTP Method โ€” POST, PUT, or PATCH
  • Auth Type โ€” None, Bearer Token, API Key Header, or Basic Auth
  • Auth Token / Key Value โ€” your authentication credential
  • JSON Body Template โ€” custom JSON body using placeholders like {{lead.email}}, {{lead.first_name}}, etc.
  • Custom Headers โ€” optional additional HTTP headers

OAuth Integrationsโ€‹

Some integrations (HubSpot, Salesforce, Zoho CRM, Google Sheets) use OAuth to connect securely. This means you authorize LeadHub by logging in to the platform โ€” no API keys to copy.

How OAuth works:

  1. Create the integration and fill in your OAuth Client ID and Client Secret (you get these from the platform's developer settings).
  2. Click Create to save.
  3. Return to the Integrations list.
  4. Click the Connect via OAuth button on the integration row.
  5. You are redirected to the platform's login page (HubSpot, Google, Salesforce, etc.).
  6. Log in and click Allow or Authorize.
  7. You are sent back to LeadHub. The integration status changes to Connected.

Your access token is stored automatically and refreshed in the background when it expires.


Sync Behaviorโ€‹

When a lead is created in LeadHub (from any source โ€” ad platform, form, manual entry, import), LeadHub immediately queues a sync to all enabled integrations.

When a lead is updated (status changed, stage changed, new field filled in), LeadHub also queues a sync. The integration will update the existing record if it can find it by email address.

Syncs happen in the background so they do not slow down your normal use of LeadHub. Most integrations sync within a few seconds of the lead arriving.


Sync Logsโ€‹

Every sync attempt is logged so you can see what happened.

  1. Go to Integrations > Integrations.
  2. Click the eye (view) icon on any integration.
  3. Open the Sync Logs tab.

For each sync you can see:

  • Which lead was synced
  • When it happened
  • Whether it succeeded or failed
  • The error message if it failed

If syncs are failing, common reasons include:

  • An API key has expired or been revoked โ€” update your credentials
  • The list ID or board ID no longer exists โ€” update the configuration
  • The platform's API is temporarily down โ€” the sync will retry

Outbound Webhooksโ€‹

Outbound webhooks are different from integrations. Instead of pushing to a specific tool, they send raw lead data to any URL you choose whenever a specific event occurs.

Use outbound webhooks to connect LeadHub to custom applications, internal systems, or any tool that can receive an HTTP request.

Creating an Outbound Webhookโ€‹

  1. Go to Integrations > Outbound Webhooks in the sidebar.
  2. Click New Outbound Webhook.
  3. Fill in:
    • Name โ€” a descriptive name, e.g. "Push to Internal CRM".
    • URL โ€” the URL that will receive the data.
    • Events โ€” choose which events trigger this webhook:
      • Lead Created
      • Lead Updated
      • Lead Deleted
      • Lead Stage Changed
      • Form Submitted
      • Automation Triggered
    • Filters โ€” optional. Restrict the webhook to fire only for leads matching specific criteria (e.g. only leads from a specific source, only leads with a specific tag).
  4. Click Create.

Webhook Deliveryโ€‹

Every time a subscribed event occurs, LeadHub sends an HTTP POST request to your URL with the lead data in JSON format. A secret key (automatically generated) is included in the X-Signature header so you can verify the request is genuine.

Webhook Delivery Logsโ€‹

Go to the outbound webhook's detail view to see every delivery attempt:

  • Timestamp
  • Which event triggered it
  • Which lead it was for
  • The HTTP response code (200 = success, 4xx/5xx = failure)
  • The full response body

If deliveries are failing, check that your URL is publicly accessible and is responding with a 2xx status code.