HubSpot LinkedIn integration: connect LinkedIn outreach to your HubSpot contacts
Published November 18, 2026
Your contacts live in HubSpot and your prospects answer on LinkedIn. You install the LinkedIn Sales Navigator app, add a "connection request" step to a sequence, and find out that the step is a reminder. Someone still has to open LinkedIn and click.
Short answer: HubSpot's LinkedIn integration shows LinkedIn data on your records and creates tasks that remind you to send a connection request or an InMail. It doesn't send them. If you want invitations and messages that go out by themselves, and a HubSpot contact that is created or updated when someone accepts or replies, you connect a LinkedIn outreach tool to HubSpot's API. Below is what HubSpot offers today, the options next to each other, and the exact setup with Kerux, including the API key change HubSpot made in October 2026.
What HubSpot offers for LinkedIn today
We read HubSpot's knowledge base and developer docs on November 18, 2026:
- The LinkedIn Sales Navigator app. Install it from the HubSpot Marketplace and a Sales Navigator card shows up on contact and company records: the person's LinkedIn title, company, time in the role, location and industry, people at the company you're already connected with, company news, and a Send InMail button. Each user needs an assigned Sales Hub Professional or Enterprise seat, and some features need a Sales Navigator Team or Advanced Plus contract.
- LinkedIn tasks in sequences. With that app, a sequence can include a Sales Navigator - Connection request task or an InMail task. HubSpot's own words: a task reminder "to manually send" it. The message you type in the task notes doesn't fill in the LinkedIn box for you.
- CRM Sync. A separate LinkedIn app saves HubSpot contacts in Sales Navigator lists, logs Sales Navigator activity on HubSpot records, and creates or updates HubSpot contacts from Sales Navigator.
- A LinkedIn URL property. Every HubSpot contact has a LinkedIn URL property (internal name
hs_linkedin_url). Fill it and any tool can find the person on LinkedIn.
On those pages we didn't find a HubSpot-built way to send LinkedIn invitations or messages on their own. HubSpot gives you context and reminders, and a person does the sending.
Four ways to connect LinkedIn and HubSpot
| Option | Sends invitations and messages | What lands in HubSpot | Best when |
|---|---|---|---|
| Sales Navigator app + sequence tasks | No: a task reminds a rep to send it by hand | LinkedIn details on the record; the task when it's done | A few reps work a short list each day |
| CRM Sync | No | Sales Navigator activity; contacts created from Sales Navigator | Your team already lives in Sales Navigator |
| Zapier or Make | No | Whatever another tool hands them | You need glue between HubSpot and a tool with no API steps |
| An outreach tool that calls HubSpot's API mid-campaign (Kerux) | Yes, by itself, inside each LinkedIn account's limits | A contact created or updated when someone accepts or replies | You want outreach that runs every day and a CRM that stays current |
The rest of this article is the last row.
The setup with Kerux
Kerux has no one-click HubSpot app today. It works through HubSpot's API, with steps both tools already have:
| Direction | In HubSpot | In Kerux |
|---|---|---|
| An accept or a reply creates or updates the contact | A service key | A Webhook / HTTP step |
| HubSpot answers back, for example when a deal moves | A workflow with Send a webhook | A Wait for webhook step |
| A HubSpot contact starts LinkedIn outreach | A workflow with Send a webhook | The campaign's trigger URL |
| Or: no API steps at all | Zapier or Make | A webhook endpoint or a rule |
1. Connect HubSpot once
HubSpot stopped letting accounts create new private apps on October 26, 2026. Private apps you already have keep working, and their token goes in the same place below. For a new connection, HubSpot now uses service keys.
In HubSpot, go to Development > Keys > Service keys and click Create service key. Name it "Kerux", click
Add new scope and tick crm.objects.contacts.read and crm.objects.contacts.write, then click Create.
Open the key, click Show and Copy. Only super admins and users with the Developer tools access
permission see this screen.
In Kerux, open Integrations > Connections and click Connect on Custom API. Choose Bearer token,
paste the key and set the base URL to https://api.hubapi.com. Click Save, then Test connection.
2. Create or update the contact 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 HubSpot". Its steps run for every contact who replies.
Add a Webhook / HTTP step, pick the HubSpot connection and name it hubspot:
{
"method": "POST",
"url": "/crm/v3/objects/contacts/batch/upsert",
"bodyType": "json",
"body": {
"inputs": [
{
"idProperty": "email",
"id": "{{email}}",
"properties": {
"email": "{{email}}",
"firstname": "{{contact.first_name}}",
"lastname": "{{contact.last_name}}",
"company": "{{contact.company}}",
"jobtitle": "{{contact.title}}",
"hs_linkedin_url": "{{contact.linkedin_url}}"
}
}
]
}
}
This is HubSpot's upsert: when a contact with that email exists, HubSpot updates it, and when there's none it creates
one. That's why we use it here instead of a plain create, which would add a duplicate every time a known person
replies. HubSpot answers with the contact, and later steps read its id as
{{steps.hubspot.response.body.results.0.id}}.
Two details that save a failed test:
- Contacts without an email. The upsert matches on email, and Kerux never sends an empty variable. A contact with no email waits on the step until one is added. If many of your LinkedIn contacts have no email, put an email finder step in front (Icypeas is a ready-made one) and take the path where an email was found.
- Empty fields. The same rule applies to every variable in the body. If you don't always have a job title or a company, remove those lines so the step doesn't wait for them.
Want every new connection in HubSpot, and not only people who answer? Put the same step on the accepted path of the campaign's Connect step.
3. Let HubSpot answer back
After the hubspot step, add a Wait for
webhook step, choose one shared link, and match on the email field. Set a time limit, for example 7 days.
In HubSpot, build a workflow that fires when the thing you care about happens, for example a deal for the contact reaches Closed won, or the contact's lifecycle stage changes. Add Send a webhook, method POST, the Kerux link, and a request body with the contact's email and the field you want. Back in Kerux, click Listen for test event and trigger the workflow once so you can pick the fields.
The contact then goes on through received (a thank-you message, a tag, the end) or timed out (a short follow-up on LinkedIn). The Send a webhook action needs HubSpot's Data Hub Professional or Enterprise.
4. Start LinkedIn outreach from HubSpot
In Kerux, open the campaign, click + Add on the Trigger half of the start box, choose Incoming webhook (API) and click Copy link.
In HubSpot, create a contact-based workflow, for example when a contact joins a list or reaches a lifecycle stage. Add Send a webhook, method POST, the Kerux link, tick Customize request body and add these keys, each set to the matching HubSpot property:
{
"linkedin_url": "LinkedIn URL",
"first_name": "First name",
"last_name": "Last name",
"email": "Email",
"company": "Company name"
}
linkedin_url is required, because Kerux can't invite someone without their profile. Kerux matches contacts by
LinkedIn URL, so a workflow that fires twice never adds the same person twice. 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 list that adds 300 people
at once doesn't mean 300 invitations today.
Getting leads from HubSpot forms? A HubSpot forms URL reads HubSpot's own field names, and people who left no LinkedIn profile still come in by email. Without Data Hub Professional, a Zap or a Make scenario that watches HubSpot can POST the same JSON to the trigger URL.
Prefer Zapier or Make to API steps?
Kerux can also announce what happened and let Zapier or Make write to HubSpot. 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
over about two days. Zapier's HubSpot app then creates or updates the contact.
What you need
- HubSpot: a service key works for the contact steps above (steps 1 and 2). The Send a webhook workflow action (steps 3 and 4) needs Data Hub Professional or Enterprise. The Sales Navigator app needs Sales Hub Professional or Enterprise seats, and you don't need it for this setup.
- Kerux: connections, Webhook / HTTP steps, Wait for webhook, 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. See the pricing page.
Where this isn't the right fit
- Your reps send a handful of requests a day by hand. The Sales Navigator app and sequence tasks keep them in HubSpot, and that may be all you need.
- You want every LinkedIn message logged on the HubSpot timeline. With this setup the conversation stays in the Kerux inbox, and HubSpot gets the contact and the fields you choose to send.
- You want one click. This is a paste-the-JSON setup with an API key.
The pattern behind steps 2 and 3 (call an app, wait for its answer, continue) is explained in Outreach webhooks. The same setup for another CRM is in Pipedrive LinkedIn integration, and adding email after LinkedIn is in LinkedIn and email in one sequence. The help center covers webhook steps, trigger URLs and webhooks, and the HubSpot integration page shows the flow.
Frequently asked questions
Does HubSpot integrate with LinkedIn?
Yes, for data and reminders. HubSpot's LinkedIn Sales Navigator app shows LinkedIn details on contact and company records and lets you send InMails from them, and sequences can include tasks that remind a rep to send a connection request or an InMail by hand. On November 18, 2026, we didn't find a HubSpot-built way to send LinkedIn invitations or messages by themselves.
Can HubSpot sequences send LinkedIn connection requests?
Not by themselves. A sequence's Sales Navigator connection request step is a task reminder to send the request manually, and the message in the task notes isn't filled in for you. To send requests automatically, a LinkedIn outreach tool sends them from your own account and writes the result to HubSpot.
How do I sync LinkedIn leads to HubSpot automatically?
Have your outreach tool call HubSpot's API when someone accepts or replies: POST /crm/v3/objects/contacts/batch/upsert with idProperty set to email creates the contact, or updates it if that email already exists. Send the profile in the hs_linkedin_url property.
HubSpot won't let me create a private app. What do I use?
HubSpot stopped new private apps on October 26, 2026 (September 28 for new accounts). Existing ones keep working. For a new connection, create a service key under Development > Keys > Service keys and send it as a bearer token.
Do I need Sales Navigator to connect LinkedIn outreach with HubSpot?
No. Sales Navigator is needed for HubSpot's own Sales Navigator card and tasks. An outreach tool connected through HubSpot's API works with regular LinkedIn accounts, and Kerux can also search Sales Navigator from an account that has it.
Which plans do I need for Kerux and HubSpot?
On Kerux, Pro (US$69 per LinkedIn account a month), Agency or the 10-day free trial. On HubSpot, a service key is enough to create and update contacts. Workflows that send data back to Kerux or start a campaign use the Send a webhook action, which needs Data Hub Professional or Enterprise.