---
name: linkedin-zapier-integration
description: Connect LinkedIn Sales Navigator and Zapier: what syncs, which editions carry it, the setup order, and the failures to expect. Covers messages. Use when the user wants to set up, audit or troubleshoot LinkedIn and Zapier together, or asks why data is not moving between them.
---

# LinkedIn Sales Navigator and Zapier

> Generated from https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-zapier-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A Zapier plan, a LinkedIn account, and page admin rights for company posts

**What moves:** messages, one way, into LinkedIn.
**How it is built:** zapier, make or n8n, marketplace app. **Effort:** minutes.

## The short version

Worth reading before you plan anything, because the headline is a negative. The LinkedIn app on Zapier has no triggers at all: Zapier documents it, and it means no LinkedIn event can ever start an automation. What you get is three actions that publish, two of them posting to a personal profile or a company page you administer and one raw API request for anything else. As a publishing integration it is fine and cheap; as the prospecting integration almost everybody is looking for, it does not exist, and the reason is LinkedIn's partner programme rather than Zapier's roadmap.

## What exists at all, on either side

Rows: Your LinkedIn role. Columns: What you want to do. There is no edition grid worth drawing here, because the constraint is not a tier. It is that most of the integration does not exist. The only access question is whether you administer the page you are posting to.

| Your LinkedIn role | Post to your profile | Post to a company page | React to a LinkedIn event |
|---|---|---|---|
| Any LinkedIn account | Available | Needs the admin role | Does not exist |
| Company page administrator | Available | Available | Does not exist |

- **Available.** A share update, with text, URLs, images and visibility settings.
- **Needs the admin role.** The same for a company page, which needs an administrator role on the page rather than a different plan.
- **Does not exist.** Zapier lists no triggers and no searches for LinkedIn. That column is empty on both rows and no upgrade on either side fills it.

Counted off that grid, of six pairings: three give you available, one gives you needs the admin role, two give you does not exist.

The empty column is why this page exists: people arrive looking for it, and the honest answer is that the thing they want is not sold here at any tier.

## What actually syncs

Direction is written from LinkedIn's point of view: out means out of LinkedIn, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| A post on your profile | One way, in | Create Share Update, with text, links, images and visibility settings, fired by a trigger in some other app. |
| A post on a company page | One way, in | Create Company Update, including mentions and link previews. Only on pages where you are an administrator. |
| Any other API call | One way, in | API Request, in beta, sends a raw authenticated HTTP request. Bounded by whatever permissions your LinkedIn app actually holds. |
| Anything out of LinkedIn | One way, out | Nothing. There are no triggers and no search actions, so a Zap can write to LinkedIn and can never read from it. |

## Which field lands where

This is the shortest field table in the directory, because the integration is two actions. Everything else people expect from it does not exist.

| In LinkedIn | In Zapier | What to know about the match |
|---|---|---|
| A Zap step | A share update on your profile | Text, URLs and images, with visibility settings on the action. |
| A Zap step | An update on a company page | Requires an administrator role on that page. |

**What does not cross:**

- Any trigger. Zapier documents that no triggers are available for LinkedIn, so nothing happening on LinkedIn can start a workflow.
- Any search action. There is no lookup, so a Zap cannot find a person, a company or a post.
- Anything inbound at all. Profile data, connections, messages and engagement are outside this integration entirely.

## Connect it, in this order

**Who has to do it:** Whoever owns the LinkedIn account. For company posts, somebody with an administrator role on the page.
**How long:** Two minutes, and the useful work is deciding whether to bother.

### 1. Check what you are expecting it to do

*Where:* Zapier: the LinkedIn app page

Zapier lists no triggers and no search actions for LinkedIn. That is not a plan limitation or a step you have missed. Nothing on LinkedIn can start a Zap and nothing can be looked up, so any workflow that begins with a LinkedIn event has to begin somewhere else.

### 2. Confirm your page role if you want company posts

*Where:* LinkedIn: company page admin settings

The Create Company Update action requires you to be an administrator of that page. A personal share update does not.

### 3. Add the connection

*Where:* Zapier: Apps, Add connection

Search for LinkedIn, authenticate, grant access. There is no org-level approval and no app review, because the surface being used is small.

### 4. Build the Zap with LinkedIn at the end

*Where:* The Zap editor

LinkedIn can only be an action step. The trigger will be a schedule, a form, a spreadsheet row or an RSS feed, and LinkedIn is where the Zap finishes.

### 5. Set visibility on each share deliberately

*Where:* The Create Share Update action

The action takes text, URLs and images and carries visibility settings. A scheduled post is the one place a wrong visibility setting runs for months without anybody noticing.

The first step is the whole decision on this pair: if you came looking for a way to get LinkedIn activity into another system, Zapier is not the route, and no amount of configuration changes it.

## How to check it worked

- Look for a LinkedIn trigger in the Zap editor. Confirming the absence yourself is worth more than reading it here.
- Post one share update and check it appears with the visibility you set.
- If you are posting to a company page, have somebody without the admin role try it and watch it fail, so the dependency is known before a handover.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| There is no LinkedIn trigger in the dropdown | There are none. Zapier documents that no triggers are available for LinkedIn. | Trigger the Zap from somewhere else. If the LinkedIn event itself is what you need, this integration cannot provide it. |
| You cannot look up a person or a company | No search actions are available either. | Use a data provider with an API for the lookup and keep Zapier for the posting step. |
| The company update action fails | You are not an administrator of the page. | Get the role, or post from the profile instead. This is a LinkedIn permission rather than a Zapier one. |
| Posts stop going out for no visible reason | LinkedIn applies rate limits to its APIs and does not publish numbers for this surface. | Space the posts out and treat the schedule as a budget. There is no figure to design against, which is itself the answer. |

## What breaks, from the vendors' own docs

- **No triggers, which rules out most of the use cases.** Zapier's own documentation says no triggers are available for LinkedIn. New connections, messages, comments and profile views cannot start a Zap. Any design that begins "when someone connects with me on LinkedIn" is impossible here, and the workaround people reach for, scraping their own inbox with an extension, is the category LinkedIn's user agreement prohibits.
- **Company posts need a page admin role.** Create Company Update works only where you are an administrator of the page. That is a LinkedIn permission rather than a Zapier one, so the person building the automation often cannot test it, and the fix lives with whoever owns the company page.
- **LinkedIn's rate limits apply and are not published.** Zapier notes that LinkedIn's rate limits may affect high-volume workflows and that its pagination limits apply to API requests. LinkedIn sets those limits per endpoint, resets them at midnight UTC and does not publish the standard figures, so the only way to know yours is the Developer Portal or a 429. A posting cadence worth automating is rarely near them; a bulk job would be.
- **A premium-sounding app on a metered plan.** Zapier charges per successful action, so the cost is the posting volume rather than the connection. Nothing on the LinkedIn side costs money. The thing to watch is that a Zap which cannot be triggered by LinkedIn will be triggered by something chattier, and the task count follows that trigger rather than your posting schedule.

## The APIs, if you are building around it instead

### LinkedIn Sales Navigator

- **Base:** `No public API for this workflow`
- **Auth:** CRM Sync is installed as an app, not called as an API.

**Rules that will cost you time if you skip them:**

- **CRM Sync requires Sales Navigator Advanced Plus**, not Advanced. The embedded profile card runs on Advanced and syncs nothing.
- **It does not backfill.** Only new and updated data syncs after switch-on; history needs an uninstall and reinstall.
- **Field mappings cannot be customised.** Every supported field syncs or none do.
- **Read your contract before extracting anything from search results.** The constraint is contractual rather than technical, so it does not announce itself when you cross it. An agent must not automate scraping here.

Docs: https://knowledge.hubspot.com/integrations/connect-hubspot-and-linkedin-crm-sync

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Zapier: how to get started with LinkedIn on Zapier: https://help.zapier.com/hc/en-us/articles/8495987891853-How-to-get-started-with-LinkedIn-on-Zapier
- LinkedIn: API rate limiting: https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits
- LinkedIn: getting access to LinkedIn APIs: https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-zapier-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-zapier-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
