How to connect
On the Zapier Apps page add an MCP Client connection: Server URL https://nilyo.com/mcp, Transport Streamable HTTP, OAuth Yes. A browser window opens to authorize, using the same Nilyo sign-in ChatGPT and Claude use — no Zapier-specific account, and one connection covers every account you connected in Nilyo.
What the built-in app cannot do
The official LinkedIn integration creates a share as a person or a company page. It cannot read a profile, search people, list your connections, send an invitation or answer a message, because the marketing API does not expose them. That is not a Zapier limitation — it is the scope of the API every LinkedIn integration is built on.
Resolve before you write
A LinkedIn URL is not an identifier and a name is not an identity. Chain a resolution step first, keep the returned stable id, then feed it into the invitation or message step. When several people match, the resolution returns the candidates rather than choosing, which is your cue to add a filter instead of letting the Zap guess.
Pacing is what saves the account
Zaps fire on every trigger; a LinkedIn account tolerates about a hundred actions a day. Calls are serialized per account with a short delay and the daily budget is enforced server-side, so a Zap looping over a spreadsheet gets an explicit limit error instead of burning the account. Turn off automatic retries on write steps: a retried invitation cannot be taken back.
A realistic Zap
A new row lands in a sheet; the Zap resolves the person on LinkedIn, checks whether a conversation already exists, and either drafts a message for you to approve or notifies you. The write step sits behind a filter, never straight after the trigger.
“When a row is added, resolve the person and draft an invitation for approval.”
“When someone accepts an invitation, notify me with the conversation history.”
Common questions
Can a Zap send a LinkedIn message or invitation?
Yes, on your own connected account, after resolving the person to a stable identifier. Put it behind a filter and disable retries.
Does this replace Zapier’s LinkedIn app?
It complements it: keep the official app for publishing a company post, use Nilyo for everything that belongs to your own account.
What happens when the daily limit is hit?
The step returns an explicit limit error rather than retrying, and the budget resets. Pushing through it is what actually endangers a LinkedIn account.
How LinkedIn works with Nilyo
Connection. Secure hosted sign-in (your LinkedIn credentials go to LinkedIn, never to the agent). Sales Navigator and Recruiter are detected automatically when your account has them.
What your agent can do. People and company search, profile lookup from a name or URL, your network and invitations, private conversations (classic, Sales Navigator, Recruiter inboxes), posts, comments and reactions, job postings and applicants, Recruiter projects.
Pacing and safety. About 100 actions per day per account, profile views and searches included; calls are serialized so an agent can never run LinkedIn requests in parallel.
- Profile URLs are resolved to stable profile IDs before any action.
- Invitations carry an optional note of up to 300 characters.
- Private or restricted profiles return an explicit “not accessible” result instead of a retry loop.
All LinkedIn guides
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.