Designed for operators of persistent agents. The agent works only with accounts connected to your Nilyo user.
What you can ask your agent to do
OP
Get runtime-specific setup guidance
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
OPChoose exact event types
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
OPCreate a destination limited to your owned accounts
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
How this workflow works
- Expose the public HTTPS receiver supported by your OpenClaw version.
- Ask Nilyo for the event catalog and create a destination.
- Generate a real-format Unipile Development Mock event and inspect delivery logs.
Webhook endpoint CRUD uses the Service key only as a controlled exception. Account IDs are rebuilt from local ownership before every remote change.
Questions people ask
Does Nilyo relay every event?
No. Unipile delivers directly to the runtime; Nilyo is the secure control plane.
Can new accounts be added automatically?
Yes, `auto_include_new_accounts` recomputes only that user's matching account set.
What if my OpenClaw version has no receiver?
The setup guide must say so rather than inventing an endpoint.
Why use Nilyo for this?
Nilyo gives your chosen agent access only to the accounts you connect. Your provider passwords are never shown to the agent, and reading information does not silently authorize sending, inviting or deleting.
If several accounts, people or companies match, the agent asks you to clarify. If the result of an important action is uncertain, it checks what happened before attempting it again.
