Pipedrive LinkedIn integration: how to connect LinkedIn outreach with Pipedrive

You keep your deals in Pipedrive and you find your prospects on LinkedIn. You search Pipedrive's settings and its Marketplace for "LinkedIn", hoping for a switch that sends connection requests and puts each reply on the right deal. There isn't one.

Short answer: Pipedrive has no built-in LinkedIn messaging. Its own blog says it "connects with LinkedIn through integrations": a LinkedIn Lead Gen Forms sync for ad leads, plus Marketplace apps from other companies, most of them Chrome extensions that save the profile you're looking at into Pipedrive. What most people want is different: invitations and messages that go out by themselves, and a Pipedrive person and deal created or updated when someone accepts or replies. For that, you connect a LinkedIn outreach tool to Pipedrive's API and webhooks. Below: the options side by side, the exact setup with Kerux, and what it costs.

What Pipedrive offers for LinkedIn today

We read Pipedrive's site, help center, developer docs and Marketplace on November 11, 2026:

• LinkedIn Lead Gen Forms Sync. A Marketplace app listed as "by Outfunnel by Pipedrive". It copies LinkedIn Lead Gen Form submissions (the forms on LinkedIn ads) into Pipedrive as contacts, leads, deals, activities or notes. It is for ad leads, not for messaging.
• Prospector and data enrichment. Prospector (part of the LeadBooster add-on) finds prospects whose contact details "always include a link to the prospect's LinkedIn page". Data enrichment, on Premium and higher, can start from a person's or a company's LinkedIn profile to fill in missing fields.
• Marketplace apps from other companies. Surfe, LinkMatch and LeadCRM are Chrome extensions that sit on top of LinkedIn: you open a profile and save it to Pipedrive. Their listings say they also sync your LinkedIn messages, and Surfe and LeadCRM export Sales Navigator lists. Dux-Soup Connector puts a panel inside Pipedrive that sends connection requests and messages, and needs a Dux-Soup Turbo or Cloud license.

On those pages we didn't find a Pipedrive-built way to send LinkedIn invitations or messages, or a Pipedrive-built Sales Navigator sync. Everything that touches LinkedIn conversations comes from another company's tool.

Five ways to connect LinkedIn and Pipedrive

Option	Sends invitations and messages	What lands in Pipedrive	Best when
Pipedrive's own features	No	LinkedIn ad form leads (Lead Gen Forms Sync); a LinkedIn link on Prospector contacts	You run LinkedIn ads or buy prospect lists
Marketplace Chrome extensions (Surfe, LinkMatch, LeadCRM)	You send them yourself on LinkedIn	The profile you save and, per their listings, your LinkedIn messages	You prospect by hand, a few profiles at a time
Dux-Soup Connector (Marketplace)	Yes, from a panel in Pipedrive, with a Dux-Soup Turbo or Cloud license	People and organizations from LinkedIn; activities for new connections and received messages	You want to work from inside Pipedrive
Zapier or Make	No: Zapier's LinkedIn app posts updates	What another tool hands them: find or create a person, create a deal or a note	You need glue between Pipedrive and a tool without API steps
An outreach tool that calls Pipedrive's API mid-campaign (Kerux)	Yes, by itself, inside each LinkedIn account's limits	A person and a deal when someone accepts or replies; a won or lost deal stops the follow-ups	You want outreach that runs every day and a CRM that stays current

The first three rows are tools you add to Pipedrive or to your browser. The rest of this article is the last row: outreach that runs on its own and writes to Pipedrive at the moment something happens.

The setup with Kerux

Kerux has no native Pipedrive app. It works through Pipedrive's API and webhooks, with steps both tools already have:

Direction	In Pipedrive	In Kerux
A reply or an accept creates the person and the deal	Your API token	Two Webhook / HTTP steps
A won or lost deal stops the follow-ups	A webhook under Tools and apps > Webhooks	A Wait for webhook step
A Pipedrive person or deal starts LinkedIn outreach	An automation with the Webhook action (Growth and higher)	The campaign's trigger URL
Or: no API steps at all	Zapier or Make actions	A webhook endpoint or a rule

1. Connect Pipedrive once

In Pipedrive, click your account name, then Company settings > Personal preferences > API, and copy your API token. The token belongs to one user and reaches what that user can see, so use an account that can create persons and deals. If the API tab is missing, a Pipedrive admin has to allow API use for your permission set.

In Kerux, open Integrations > Connections and click Connect on Custom API: choose API key in a header, header name x-api-token, paste the token, and set the base URL to https://YOUR-COMPANY.pipedrive.com. Click Save, then Test connection.

2. Create the person and the deal when someone replies

A contact who replies leaves the campaign through the When the contact replies box. In that box, add the action Send to another campaign and pick a short campaign, for example "Replied: to Pipedrive". Its steps run for every contact who replies.

Add a Webhook / HTTP step, pick the Pipedrive connection and name it person:

{
  "method": "POST",
  "url": "/api/v2/persons",
  "bodyType": "json",
  "body": {
    "name": "{{contact.full_name}}",
    "emails": [{ "value": "{{email}}", "primary": true, "label": "work" }]
  }
}

Pipedrive answers with the new person and its id. A second Webhook / HTTP step named deal posts to /api/v2/deals with a title and person_id set to {{steps.person.response.body.data.id}}. You can also send owner_id, pipeline_id, stage_id and value, so the deal lands in the right stage with the right owner. The exact deal request (it is sent as text so the id stays a number) is in the Pipedrive setup guide.

Three details that save a failed test:

• Contacts without an email. Kerux never sends an empty variable, so a contact with no email waits on the person step until you add one. If most of your LinkedIn contacts have no email, remove the emails line: Pipedrive only requires name.
• Duplicates. POST /api/v2/persons adds a new person on every call. If the person may already be in Pipedrive, search first with GET /api/v2/persons/search (term set to the email, fields=email) and branch on the result.
• The LinkedIn profile. Create a person custom field in Pipedrive for the LinkedIn URL and send {{contact.linkedin_url}} under custom_fields, with the field's key from Pipedrive.

Want every new connection in Pipedrive, not only people who answer? Put the same two steps on the accepted path of the campaign's Connect step. A third step can add a note (POST /api/v1/notes with content and the deal_id) or a follow-up task for the deal's owner (POST /api/v2/activities).

The API cost is small: Pipedrive gives each account 30,000 API tokens a day per seat on Lite (more on higher plans), and adding a person and a deal takes 10.

3. Let a won or lost deal stop the follow-ups

After the deal step, add a Wait for webhook step, choose One shared URL + a match rule, and match the deal id in Pipedrive's payload to {{steps.deal.response.body.data.id}}. Click Listen for test event.

In Pipedrive, open Tools and apps > Webhooks, create a webhook for deal changes and paste the Kerux URL. Pipedrive sends every change as meta (what happened and the deal's id), data (the deal now) and previous (the fields that changed). Change a test deal so Kerux receives a sample, then pick the id and the status from it. A Condition step on the status sends won deals to a thank-you message and lost deals to a tag and the end.

Regular webhooks are on every Pipedrive plan. One thing to know: Pipedrive deletes a webhook that had no successful delivery for 3 days in a row, so don't remove the Kerux step and leave the webhook behind.

4. Start LinkedIn outreach from Pipedrive

This direction needs Pipedrive's Growth plan or higher, because it uses the Webhook action in Automations.

In Kerux, open the campaign, click + Add on the Trigger half of the start box, choose Incoming webhook (API) and click Copy link.

In Pipedrive, a global admin opens Tools and apps > Webhooks, clicks + Webhooks and picks Automated webhook. Paste the Kerux link as the endpoint URL and add a ? at the end: Pipedrive asks that the URL end with /, &, ? or =, and the Kerux link works with ? (a trailing slash doesn't). Then build an automation, for example when a deal reaches a stage, add the Webhook action, pick that webhook, method POST, and a Raw body. Each value is a Pipedrive field you insert with the field button:

{
  "linkedin_url": "the person's LinkedIn profile field",
  "first_name": "the person's first name field",
  "last_name": "the person's last name field",
  "email": "the person's email field",
  "company": "the organization's name field"
}

linkedin_url is required: Kerux can't invite someone without their profile. Kerux matches contacts by LinkedIn URL, so an automation that fires twice never adds the same person twice. Check the first run in Pipedrive under Automations > History, which shows the body that was sent.

The campaign then sends the invitation, waits for the accept and sends your messages, with every LinkedIn account kept inside its daily and weekly limits (see LinkedIn invitation limits). A deal stage that moves 200 people at once doesn't mean 200 invitations today.

On Pipedrive Lite, or if you'd rather not touch automations, a Zap or a Make scenario that watches Pipedrive can POST the same JSON to the trigger URL. Code works too: POST /v1/workflows/{id}/enrollments on the Kerux API.

Prefer Zapier or Make to API steps?

Kerux can also just announce what happened and let Zapier or Make write to Pipedrive. In Integrations > Developers, add your Zap's or scenario's webhook address under Webhooks and pick the events, for example linkedin.invitation_accepted, linkedin.message_received or reply.positive. Each one carries a lead object with email, first_name, last_name, company, title and linkedin_url, signed and retried 7 times over about two days. Zapier's Pipedrive app then runs Find or Create Person and Create Deal.

To send only one campaign's contacts, use a rule: Integrations > Rules > New rule, When an invitation is accepted, Where while the contact is in that campaign, Then send to a webhook endpoint.

What it costs

• Pipedrive (its pricing page, per seat per month, billed annually): Lite US$14, Growth US$39, Premium US$59, Ultimate US$79. The API token and regular webhooks (steps 1 to 3) work from Lite. The Webhook action in Automations (step 4) starts at Growth.
• Kerux: connections, Webhook / HTTP steps, trigger URLs, webhooks and the API are part of Pro (US$69 per LinkedIn account a month) and Agency (US$45 per account, from 15 accounts), and of the 10-day free trial with no card.

One LinkedIn account on Kerux Pro plus one Pipedrive Lite seat is US$83 a month (Pipedrive billed annually); with a Growth seat, so Pipedrive can start campaigns itself, US$108. See the pricing page.

Where this isn't the right fit

• You prospect by hand. If you open a few profiles a day and want a "save to Pipedrive" button on LinkedIn, a Chrome extension from the Marketplace is the simpler tool. A campaign tool is more than you need.
• Your leads come from LinkedIn ads. That is what LinkedIn Lead Gen Forms Sync is for.
• You want every LinkedIn message logged in Pipedrive. With this setup the conversation stays in the Kerux inbox, and Pipedrive gets the person, the deal and the notes you choose to write. The extensions above say they sync messages into Pipedrive.
• You want one click. This is a paste-the-JSON setup with an API token. It works on Kerux Pro and Agency, not on Starter.

More on the pattern behind steps 2 and 3 (call an app, wait for its answer, continue) in Outreach webhooks. The Pipedrive integration page shows the flow, the help center covers webhook steps, trigger URLs and webhooks, and every tool Kerux works with is on Integrations.