Install and authenticate
On n8n Cloud, search Nilyo in the nodes panel and drop it on the canvas: the package is a verified community node, so there is nothing to install. On self-hosted n8n, add n8n-nodes-nilyo from Settings then Community nodes. Create a personal token in Nilyo under Agent access and store it in an n8n credential named Nilyo API.
“Search LinkedIn people at a company and write the matches to a sheet.”
“Resolve a LinkedIn profile URL captured earlier in the workflow.”
What the built-in node cannot do
The official LinkedIn node exposes a single operation, creating a post as a person or an organization. It cannot read a profile, search, list your network or send a message, because the marketing API does not expose them. Nilyo acts as your connected account instead, which is what an outreach or research workflow actually needs.
Resolve identifiers before any write
A LinkedIn URL or a display name is not an identifier. Chain a profile resolution or a search step first, keep the returned stable id, then feed it into the invitation or message step. The node returns corrective errors that name the step to call again when an id is stale.
Pacing is enforced for you
Workflows loop quickly, accounts do not. Nilyo serializes calls per account and applies a daily budget of roughly one hundred LinkedIn actions including live reads, so a runaway workflow cannot burn the account. When the budget is reached the node returns an explicit limit error rather than retrying.
A realistic workflow
A form captures a company name, a search step lists people matching the role, an LLM node ranks them, a human approval step selects two, and only then an invitation step runs with the resolved identifiers.
Common questions
Does this replace the official LinkedIn node in n8n?
It complements it. Keep the official node for publishing a company post; use Nilyo for everything that belongs to your own account, such as search, profiles, invitations and conversations.
Is this browser automation or scraping?
No. Nilyo goes through a connection layer that speaks the provider protocols directly, so there is no headless browser to break, and pacing is applied per account.
Do I need Sales Navigator or Recruiter?
No. A standard LinkedIn account works. Sales Navigator and Recruiter stay separate explicit capabilities when the connected account has them, because their inboxes and searches are different products.
Can the n8n AI Agent use these actions?
Yes. The Nilyo node can be attached to an AI Agent node as a tool, so the agent picks the action and the arguments itself.
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.