No triggers at all, so nothing on LinkedIn can ever start a Zap.
A Zapier plan, a LinkedIn account, and page admin rights for company posts
Messages, one way, in.
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.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| 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. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
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. |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: two field mappings and three documented exclusions, each one's note, and the three vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
Two actions and no reads is a publishing tool rather than an integration, and reading it that way makes it genuinely useful for the narrow job it does.
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. Pick one on each side and the grid marks the answer.
Pick one on each side.
| 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 |
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.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
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.
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.
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.
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.
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.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/linkedin-zapier/SKILL.md https://www.reversecontact.com/integrations-hub/skills/linkedin-zapier.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyThere 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.
WhyNo search actions are available either.
Use a data provider with an API for the lookup and keep Zapier for the posting step.
WhyYou 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.
WhyLinkedIn 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.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2021 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
As far as I know, LinkedIn locked down those types of services years ago. You will have better luck with dedicated enrichment providers like ZoomInfo, Clearbit, or Apollo. Most offer mature APIs
r/salesforce·May 2025·7 points
The accurate answer, and it explains the empty column above. Zapier is not failing to offer LinkedIn triggers; LinkedIn is not offering them to Zapier.
lots of leads being registered in my real estate company. Approx 6,000 a month, however when adding contact into sales force manually
r/salesforce·May 2025·7 points
Six thousand records a month is exactly the scale at which somebody searches for a LinkedIn Zapier integration. The honest routing is a data provider for the enrichment and an orchestrator for the plumbing, with LinkedIn in neither role.
I implemented it for my org about a year ago. No complaints so far. It helps with the sales team to get messages out quicker, finding the contacts and giving them a good overview
r/salesforce·May 2021·4 points
Said about the Sales Navigator CRM integration, which is what actually moves LinkedIn data into a system of record. If that is the job, the comparison is between a licence and an extension rather than between Zapier plans.
I believe yes with ZoomInfo you could essentially use the info you have to query for a contact, and potentially scrape the data.
r/salesforce·May 2025·5 points
A reminder of where these conversations go when the official route is empty. Whatever you conclude, it is a different decision from configuring an integration and it belongs with somebody who has read the terms rather than a thread.
Our team has decided to find out if the integration of Sales Navigator with Salesforce makes a powerful mix
r/salesforce·May 2021·14 points
The useful thing this page can do is answer it quickly. For publishing, Zapier works. For anything inbound, it does not exist, and knowing that in a minute is worth more than a thorough comparison of plans.
Nobody discusses this pair, because there is little to discuss. What people discuss is the job they hoped it would do, which is getting LinkedIn data into another system automatically. The answers have been consistent for years: LinkedIn closed those routes, and the alternative is a data provider with an API or the licensed CRM integration.
If you arrived looking for a way to automate LinkedIn, the fastest useful outcome is to stop looking at this pair and start looking at the licensed integration or a data provider.
The useful thing this page can do is stop a project early. A large share of the people searching for a LinkedIn and Zapier integration want a new connection, a message or a lead-gen form submission to start something, and none of that is possible. Zapier says so in one sentence and the sentence is easy to miss between the marketing pages of a dozen third-party tools that imply otherwise. Confirm the trigger exists before designing around it, which is good practice generally and essential here.
Why it is missing is worth knowing, because it predicts the same gap in every other orchestration tool. LinkedIn's sales permissions require approval as a Sales Navigator Application Platform partner and LinkedIn documents that it is not currently accepting new partners. So the publishing API, which uses open permissions, is what the whole iPaaS category connects to. The n8n pairing has exactly the same shape and the same single capability, for exactly the same reason.
If the real requirement is LinkedIn data in a CRM rather than posts on a page, the architecture changes completely and for the better. A provider with its own licensed dataset resolves a profile URL or an email into a person and a company, and Zapier moves that result wherever it needs to go. Nothing in that chain depends on LinkedIn access, a page layout or a user agreement, which is why it keeps working. That is the pattern the data layer exists to describe.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under LinkedIn, Zapier and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
No. Zapier's help centre states plainly that no triggers are available for LinkedIn. A new connection, a message, a profile view or a comment cannot start a Zap, and no setting changes that. Every Zap involving LinkedIn has to be started by something else and use LinkedIn as an action, which is the opposite of what most people picture when they search for this.
Three things. Create Share Update posts to your personal profile. Create Company Update publishes to a company page you administer. API Request, in beta, sends a raw authenticated HTTP request for anything else. That is the whole surface, and it is a publishing integration rather than a prospecting one.
Because you are not an administrator of it. Zapier documents that Create Company Update works only for company pages where you hold an admin role, and the fix is a LinkedIn page admin change rather than anything in Zapier. In most companies the page admin is in marketing and the person building the Zap is not.
Not through this app. It writes posts and reads nothing, because LinkedIn's sales permissions need partner approval that LinkedIn is not currently granting. Teams that need profile data in a CRM use a provider with its own licensed dataset and push that through Zapier instead, which is a different architecture with a different cost and no dependence on LinkedIn access.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.