One summary instead of five inboxes
Ask your agent what came in since a given time and it reads each connected account for that window: WhatsApp, Telegram and Instagram chats, LinkedIn conversations and your mailboxes. The answer is grouped by person and by what they want, not by app, so the colleague who wrote on WhatsApp and the client who wrote by email sit in the same list.
“What did I receive since yesterday 6 pm on WhatsApp, LinkedIn and email? Summarize what needs me.”
“Give me today’s digest: who wrote, what they want, and what is waiting on me.”
Once or twice a day is the rhythm that sticks
A morning pass catches what arrived overnight, and an end-of-day pass catches what came in while you were in meetings. In ChatGPT, a scheduled task runs the same prompt at the same time every day. In n8n, a schedule trigger can run it and send the summary to your own WhatsApp or mailbox, so the digest reaches you where you already look.
What a useful digest contains
Who wrote, in one line each; what they are asking for; which threads are waiting on an answer from you; and the details that are easy to miss in a long thread, such as a date, a price or a deadline. Everything else is noise, and a digest that lists every message is just another inbox.
An exact window, not “recent”
“Since yesterday 6 pm” means exactly that: the agent reads the chats that were active in the window and keeps the messages from that period, newest first. When there are more active conversations than one pass can read, the digest says so instead of pretending to be complete. LinkedIn reads count against the account’s daily budget, so the digest reads the recent conversations rather than the whole inbox.
Reading sends nothing
Listing and reading are read-only: no reply goes out, and on WhatsApp nothing is marked read for the other person. That is what makes the digest safe to put on a schedule.
From the digest to the reply
The digest ends where the work starts. Ask for a draft for one conversation, check it, and send it from your own account; each send is a separate action you request, and when several people match a name the agent asks which one.
“Draft a reply to Marc from this morning’s digest.”
“Which of these can wait until tomorrow?”
Common questions
Which accounts does the digest cover?
The ones you connected: WhatsApp, Telegram, Instagram, LinkedIn and your mailboxes (Gmail, Outlook or IMAP), in a single summary.
How do I get it every day?
In ChatGPT, turn the prompt into a scheduled task at the time you want. In n8n, use a schedule trigger and send the summary to your own WhatsApp or email. Any agent that can run a prompt on a schedule works the same way.
Does it mark my messages as read?
No. Reading is read-only and, on WhatsApp, nothing is marked read for the other person.
Can it reply for me?
It drafts on request, one conversation at a time, and sends only when you ask.
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.