Designed for people running persistent personal agents. The agent works only with accounts connected to your Nilyo user.
What you can ask your agent to do
HE
Select a connected Telegram account
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
HEList and read chats
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
HESend text or supported native media
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
- Connect Telegram in your Nilyo account.
- Connect your runtime to the common MCP endpoint.
- Ask for a read-only review first, then approve specific sends.
Realtime delivery goes directly from Unipile to your runtime. Nilyo configures the destination but does not become a generic event relay.
Questions people ask
Does Telegram use a separate MCP?
No. Every runtime and provider uses the common Nilyo MCP.
Can it delete chats?
Provider limitations are explicit; Telegram chat deletion is not presented as universally supported.
Can OpenClaw react to new messages?
A persistent runtime can receive direct Unipile webhook events when it exposes a public receiver.
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.