Designed for users running persistent Hermes agents. The agent works only with accounts connected to your Nilyo user.
What you can ask your agent to do
HE
Configure a direct webhook destination
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
HESubscribe to valid email event names
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
HEUse event IDs as pointers to fetch current context
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
- Confirm the Hermes runtime can receive public HTTPS events.
- Create the destination for selected email accounts.
- Test with Unipile mocks before relying on production delivery.
Agents must tolerate unknown future event types and inspect each event's `type` and `payload` instead of assuming one schema.
Questions people ask
Do events contain the full email?
Some events are intentionally light. The agent uses IDs to call MCP for authoritative context.
Can it subscribe to someone else's inbox?
No. Nilyo only accepts DB-owned account IDs.
Can Nilyo build the whole workflow?
No. Conditions and scheduling live in Hermes or a workflow product.
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.
Related workflows
OP