One question, every account
With LinkedIn, WhatsApp, Instagram, Telegram and your mailboxes connected, the search runs across all of them and returns the message that holds the detail, with its conversation and its date. You stop having to remember where a thing was said in order to find it.
“Where did someone give me the address for Thursday?”
“Find the message where we agreed the price, in any channel.”
Keyword search fails on paraphrase
Searching for price finds every message containing the word and misses the one saying we can do 4,200. Reading the candidate conversations instead of matching strings is what finds the second — it costs more calls and it is the reason the question works at all.
The channel is part of the answer
Knowing that a commitment was made on WhatsApp rather than by email changes what you do with it: one is a written record you can forward, the other is a conversation you may need to confirm. The result carries the conversation it came from, not just the sentence.
Narrow before you widen
Reads count on LinkedIn against a daily budget of about a hundred actions per account, so a search told roughly when or with whom is both cheaper and more accurate than one told to look everywhere. Giving the period you half-remember is usually enough.
Reading is invisible
Nothing is marked read, nothing is answered, nothing moves. The search touches the accounts you connected and leaves no trace for the people you spoke with — which is the minimum you should expect before pointing anything at five private inboxes.
The version people keep using
In practice this becomes a daily reflex rather than an occasional rescue: what did that person say about the deadline, did anyone send the invoice, where is the link to the document. It is the question the apps cannot answer because each of them only knows its own half.
Common questions
Which accounts can it search?
Every account you connected: LinkedIn, WhatsApp, Instagram, Telegram, Gmail, Outlook and any IMAP mailbox.
Is it better than each app’s own search?
For finding a message containing a word, no. For finding what was agreed when you do not remember the words used, yes — it reads the conversations rather than matching strings.
Does it leave a trace?
No. Reading marks nothing as read and sends nothing; every visible action is a separate step you request.
How do I make it faster?
Give it a period or a person. A narrowed search reads fewer conversations, which is both quicker and more accurate.
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.