What connecting actually does
You are sent to a hosted sign-in page and you authenticate with LinkedIn, not with us. What comes back is a session held by the connection layer, not your password: the credential never travels to the agent, never appears in a tool argument, and is never returned by any API response. Each workspace gets its own isolated scope and its own encrypted key, so one customer’s agent has no path to another customer’s accounts — that isolation is structural, not a permission checkbox.
Two-factor and checkpoints are part of the flow
LinkedIn regularly asks for more than a password: a code sent by email or SMS, a confirmation in the mobile app, sometimes a challenge after a sign-in from a new place. These are surfaced as an explicit step rather than a silent failure — the connection pauses, you are asked for the code, and it resumes. It is the same reason a connection can ask you to confirm from your phone: we are driving your real account, and your real account has real security.
When a session expires, you reconnect the same account
Sessions do not last forever. An account carries a state — running, waiting for credentials, disconnected, or in error — and when it stops being usable the agent gets a clear error naming the account instead of an empty result that looks like “you have no messages”. Reconnecting reuses the existing account rather than creating a second one, so your history, your identifiers and anything built on them keep working. A disconnected account is the single most common reason an agent suddenly “cannot find” a conversation it read yesterday.
Several accounts, and knowing which one to use
You can connect more than one LinkedIn account, and most people eventually do: a personal one, one for a second company, a seat with Sales Navigator or Recruiter. Every action names the account it runs on, and when a request could apply to several the agent asks instead of picking. The same rule covers people: if two contacts could match the name you gave, nothing is sent and the candidates come back for you to choose — an invitation to the wrong Alex Chen is not a recoverable mistake.
“Which LinkedIn accounts do I have connected?”
“Use my company account for this one, not my personal.”
What the agent can see, and what it cannot
An agent only ever reaches the accounts you connected and authorized, and reading never silently grants writing: sending, inviting or posting are separate actions with their own confirmation. Your LinkedIn password is never shown to the agent or to us. Access can be revoked from your account page at any moment, which cuts every agent at once. And if your company pays for the workspace, that pays for seats — it does not give an administrator a way to read a member’s messages, profile or calendar.
Connect once, use from every agent
The connection belongs to your Nilyo account, not to a particular tool. Connect LinkedIn today from ChatGPT and it is already there tomorrow in Claude, in Cursor, in an n8n workflow or in a Make scenario, with the same identifiers and the same state. This is the practical difference with per-tool integrations: you are not re-authorizing LinkedIn in five places, and you are not maintaining five sessions that expire on five different days.
“Read my unanswered LinkedIn conversations from this week.”
“Who do I already know at this company before I ask for an intro?”
Common questions
Can an AI agent use my own LinkedIn account?
Yes, once you connect it. The agent acts as you, on the account you authorized, with the same visibility you have — not on a public scrape and not through a separate bot identity.
Do I give my LinkedIn password to Nilyo?
You sign in on a hosted page and the session is kept by the connection layer. The password is never returned to the agent, never stored in a tool argument, and never visible in an API response.
What happens if LinkedIn asks for a verification code?
The connection pauses and asks you for it, then resumes. Codes by email or SMS and confirmations in the mobile app are handled as an explicit step in the flow.
My agent says it cannot see my messages any more. Why?
Almost always a session that expired. The account state says so and the error names the account to reconnect; reconnecting reuses the same account rather than creating a duplicate.
Can I connect a second LinkedIn account?
Yes. Each action names the account it runs on, and the agent asks which one to use when a request is ambiguous rather than guessing.
Can my employer read my messages if they pay?
No. Company billing covers seats. It does not give an administrator access to a member’s messages, mailboxes or calendars, and you can disconnect an account at any time.
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.