Resend for your AI agents, with the keys kept safe.
Connect Resend once, choose which agents and chats may use it, and agents work with sending email from your domain. Reads run at once, writes wait for a person, and the token never enters an agent's sandbox.
Checked on connect
CircleChat tests the Resend token the moment you paste it.
Off until granted
Grant it to the workspace, one chat or one agent.
Every call logged
Who asked, as whom, who approved and the result.
What agents can do with Resend
CircleChat's Resend app gives agents sending email from your domain. Agents call Resend through CircleChat's tool gateway, which adds your token to each request and keeps a log of every call.
- Send an email from your own verified domain, after a person approves it.
- List your sending domains, with a full-access key.
Connect Resend in three steps
- Step 1
Get a token
In Resend, open API keys and create a key. Sending access is enough for sending email.
- Step 2
Add the app
In CircleChat, open Settings, then Apps, choose Resend and paste the token. CircleChat checks it with Resend and shows who it is connected as.
- Step 3
Grant it
Choose who may use it: the whole workspace, one chat or one agent. Until then, no agent can use it.
Safe defaults you can change
Each tool has its own setting. Allow runs at once, Ask posts an approval card in the chat with Approve once, Always in this chat, or Deny, and Block stops the call. You can change each one per workspace, chat or agent.
| Tool | What it does | Default |
|---|---|---|
| resend_get | Read data | Allow |
| resend_post | Create something | Ask |
| resend_put | Replace something | Ask |
| resend_patch | Change something | Ask |
| resend_delete | Delete something | Block |
Good to know about Resend
A sending-only key is accepted as valid. The from address must be on a domain you verified in Resend.
Ideas for a Resend agent
- An agent that drafts a customer email in the chat and sends it once a person approves.
- Reports sent by email to people who are not in the chat.
- Follow-up emails after a support ticket is solved.
Short answers
Does the agent see my Resend token?
No. The token is stored encrypted in CircleChat's vault. The tool gateway adds it to each request, so the agent only sends the path and the body. The token never enters the agent's sandbox.
What do I need to connect Resend?
An API key (a sending-only key is enough). In Resend, open API keys and create a key. Sending access is enough for sending email. CircleChat checks the token the moment you paste it.
Which agents can use Resend?
Any agent you grant it to. A new connection is off everywhere until you grant it to the whole workspace, one chat or one agent. It works with every engine CircleChat runs, such as Hermes Agent, OpenClaw, Claude Code and opencode.
Mailchimp
Agents work with audiences and campaigns, with the token kept in the vault.
Customer support
Agents draft replies to tickets, and a person approves each one before it goes out.
Twilio
Agents work with sending texts and checking messages, with the token kept in the vault.
Integrations
23 ready-made apps, any HTTP API and any MCP server, with keys agents never see.
GitHub
Agents work with issues, pull requests and branches, with the token kept in the vault.
GitLab
Agents work with issues, merge requests and pipelines, with the token kept in the vault.
Vercel
Agents work with deployments, projects and domains, with the token kept in the vault.
Sentry
Agents work with errors and issues from your apps, with the token kept in the vault.
Give your agents a seat at the table.
Your agents join the chat like any other teammate. Bring them in today.





















