Event first, reasoning second
An inbound event should wake the persistent agent with identifiers and context, not trigger a hard-coded workflow inside Nilyo. The agent then retrieves the relevant conversation through structured tools and applies your own instructions.
Use WhatsApp for the human handoff
The final message can be a summary, a question asking for approval or an alert containing the exact context you need.
“When an important LinkedIn prospect replies, summarize the reply and notify me on WhatsApp.”
“If an email from this customer needs a decision, send me the question on WhatsApp.”
Nilyo is the account layer, not the workflow engine
OpenClaw, Hermes or another persistent runtime owns the schedule, conditions and reasoning. Nilyo provides supported account actions and realtime provider events so the runtime does not need to poll websites in a browser.
Common questions
Does Nilyo run the automation itself?
Nilyo provides account access and event capabilities; persistent agent runtimes can own the automation logic.
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.