React to the event, do not poll
A realtime destination delivers the new LinkedIn message as it happens, with the identifiers needed to read the conversation. Polling would spend the daily budget of about a hundred actions per account, reads included, discovering that nothing changed — and it would still be five minutes late.
Filter before you alert
The event fires on everything, including your own outgoing messages and system events such as a new connection. Keep only real inbound messages — not yours, not an event, not empty — then filter on what deserves interrupting you: a keyword, a known contact, a first message from someone new.
An alert without context is a notification
The event carries identifiers, not the conversation. Reading the last few messages before sending the alert is what makes it actionable: who wrote, what they said, what was said before. Otherwise you get a WhatsApp telling you to go and look at LinkedIn, which is worse than the LinkedIn notification.
“Alert me on WhatsApp when a LinkedIn message mentions pricing or a demo.”
“Tell me when someone I invited finally replies.”
Send it to yourself
The alert goes to your own number — resolved by name from your own conversations, and refused if several contacts could match. Nothing is sent to the person on LinkedIn, and no reply is drafted unless you ask for one separately.
Rare on purpose
An alert that fires ten times a day is a notification you will mute within a week. Set the filter tight enough that each one earns the interruption: a real question, a named account, a reply you were waiting for. The value is in what it does not send.
Then answer from wherever you are
Because the same accounts are reachable from your assistant, the natural follow-up is to answer from the same place: read the thread, draft the reply, send it. The alert stops being a prompt to open LinkedIn and becomes the start of the answer.
Common questions
How does the agent know about a new LinkedIn message?
A realtime destination delivers the event as it happens, so nothing polls the account and the daily budget stays available for the reads that matter.
Will it alert on my own messages?
Not if the filter is in place, and it must be: the event fires on your outgoing messages too, which is the usual cause of a loop.
Can it reply automatically?
Only if you ask for that explicitly. The safe shape is an alert with context, and a reply you request afterwards.
Which number receives the alert?
Your own, resolved by name from your conversations — and if several contacts match, nothing is sent and you are asked.
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.