How the trigger registers
Publishing the workflow registers an event destination in Nilyo pointing at the n8n webhook URL; unpublishing removes it. There is nothing to configure by hand and nothing left behind when a workflow is disabled — which also means a workflow you never published is not receiving anything, and that is the first thing to check when nothing fires.
What the event carries, and what it does not
Events carry identifiers and metadata, not always the content. A new message event tells you the account, the chat and the message; a new email event carries the full email, so no extra read is needed there. Knowing which is which is what stops a workflow from making a call it did not need, or from assuming a body that is not in the payload.
Why polling costs more than it looks
On LinkedIn the daily budget of about a hundred actions per account includes reads, so a workflow listing conversations every five minutes spends the whole budget discovering nothing changed. On a mailbox it costs n8n executions rather than quota, but it still answers up to five minutes late. Events remove both.
“Alert me on WhatsApp when a LinkedIn message mentions pricing.”
“Draft a reply when an email arrives from a client domain.”
Filter at the start, not at the end
A trigger fires on everything you subscribed to, including your own outgoing messages and system events such as a new connection. Filter immediately: not your own, not an event, not empty. A workflow that skips that check answers its own messages, and the loop is not obvious until it has run twenty times.
One destination, several providers
The trigger can watch LinkedIn, WhatsApp, Instagram, Telegram and mailboxes at once, or a single provider. One workflow can therefore handle whatever arrives and branch on the provider, which is usually simpler than five workflows that drift apart over time.
Common questions
Do I need to expose a public URL?
n8n provides the webhook URL; the trigger registers it for you on publish. On self-hosted instances that URL has to be reachable from the internet.
What happens when I disable the workflow?
The destination is removed, so nothing is delivered and nothing accumulates. Re-publishing registers it again.
Does the event include the message text?
A new email event carries the full email. A new message event carries identifiers, so the workflow reads the conversation — which is also the right moment to check the thread was not already answered.
Will it fire on my own messages?
Yes, unless you filter them out, which the first node of every template does. It is the most common cause of a workflow answering itself.
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.