The recipient is resolved before anything is written
A name is not an identity and a profile URL is not an identifier. Paste a URL and it is resolved to the real profile first; give a name and a company and you get a ranked set of candidates. Only a stable identifier reaches the send action. Skipping that step is how a message meant for a client lands on a stranger with the same name.
“Message this profile and say I enjoyed their talk: linkedin.com/in/…”
Two matches means nothing is sent
When several people could be the one you meant, the agent does not pick the most likely: it stops and shows you the candidates. That is a deliberate refusal, and it is the behaviour you want — an ambiguous send is not a small mistake on LinkedIn, it is a message in someone’s inbox with your name on it.
Reply in the thread, do not start a second one
If a conversation already exists, answering inside it keeps the history where your correspondent expects it. Starting a new one splits the thread and looks like you forgot the previous exchange. So the agent looks for the existing conversation first and only starts one when there is genuinely none.
“Read my conversation with John and send the follow-up we discussed.”
An ambiguous failure is never retried
A send that times out may or may not have gone through. Retrying is how people end up sending twice. The agent reads the conversation back to see whether the message is there, and reports rather than guessing. This is the single most valuable rule when an assistant writes on your behalf.
Which inbox sends it
A Sales Navigator seat has its own inbox and its own InMail, and a Recruiter contract another. Starting a conversation names the inbox explicitly, so an InMail is sent as an InMail and a Classic message as a Classic one. Nothing silently downgrades.
Common questions
Can ChatGPT send a LinkedIn message?
Yes, on your own connected account, where the action is supported. The recipient is resolved first and the send is an explicit action you ask for.
What if two people have the same name?
Nothing is sent. The candidates come back and you choose — an ambiguous write is refused rather than guessed.
Can I just paste a LinkedIn URL?
Yes, that is the natural input. The URL is resolved to the profile and its stable identifier before the message is sent; the URL itself is never used as an identifier.
Will it send the same message twice?
A failed or ambiguous send is not retried. The conversation is read back to check whether the message arrived, and the result is reported instead of guessed.
Is there a limit?
Yes, a daily budget of roughly a hundred LinkedIn actions per account, reads included, with calls serialized and spaced. It is what keeps an assistant from behaving like a bot on your 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.