Channels: Email (AgentMail)
Email via AgentMail is a Tier 1 channel. AgentMail provides a hosted inbox and an API, so you do not run your own mail server. You provide an API key and the inbox address, then point AgentMail’s webhook at Wayland.
Before you start (prerequisites and accounts)
Section titled “Before you start (prerequisites and accounts)”- An AgentMail account with an inbox.
- The Wayland desktop app running with a model provider connected.
Create the credentials (on the provider side)
Section titled “Create the credentials (on the provider side)”- In AgentMail, create or choose an inbox and note its inbox address.
- Create an API key.
- Choose a webhook secret to authenticate inbound delivery, if AgentMail asks for one.
Connect it in Wayland (Settings > Channels > Email)
Section titled “Connect it in Wayland (Settings > Channels > Email)”- Open Settings > Channels and choose Email (AgentMail).
- Enter the API key.
- Enter the Inbox address.
- Enter the Webhook secret if you use one.
- Save.
- In AgentMail, set the inbound webhook to the inbound URL Wayland exposes.
In the Wayland Core CLI, configure the same channel in your Core channel config with the API key, Inbox address, and optional Webhook secret, then point the AgentMail inbound webhook at the URL Core exposes.
Verify (status goes from idle to connected, send a test message)
Section titled “Verify (status goes from idle to connected, send a test message)”After saving, the status moves from idle to connected. Send an email to the inbox address and confirm a reply.
Route to an assistant or team
Section titled “Route to an assistant or team”Set the assistant and default model on the page. Inbound mail routes to that assistant.
Troubleshooting
Section titled “Troubleshooting”If mail does not arrive, confirm the API key, the inbox address, and the webhook configuration in AgentMail. See Channel Connection Issues.