Meet NanoCo, maintainers of NanoClaw: we raised $12M to give every member of your team a professional assistant →
Skills
Messaging Official

Resend (Email)

Add email as a messaging channel via Resend. Each thread becomes a conversation, with the bot replying from your domain.

What it does

  • Inbound email via Resend webhooks
  • Outbound email from the bot's verified domain
  • Thread tracking via In-Reply-To and References headers
  • Async — works with longer response expectations
  • Async-friendly delivery model — works for slow conversations

What you'll need

  • NanoClaw installed and running
  • A Resend account with a verified sending domain
  • A publicly reachable HTTPS endpoint for the webhook

Install

/add-resend

How it works

The /add-resend skill turns email into a NanoClaw channel via Resend. Inbound emails arrive at a webhook (email.received event), the agent processes them, and replies are sent through Resend’s API from your verified domain.

Each email thread — identified by In-Reply-To / References headers — becomes its own conversation. The agent has access to the email’s plain text body and HTML.

Setup

In Resend:

  1. Create an account and add your sending domain. Resend walks you through DKIM and SPF DNS records — verification typically takes a few minutes.
  2. Generate an API key under API Keys.
  3. Set up a webhook under Webhooks → Add webhook:
    • URL: https://your-domain/webhook/resend
    • Events: email.received
    • Copy the signing secret.

Add to .env:

RESEND_API_KEY=re_...
RESEND_FROM_ADDRESS=bot@yourdomain.com
RESEND_FROM_NAME=NanoClaw
RESEND_WEBHOOK_SECRET=...

The skill copies the Resend adapter from the channels branch and installs @resend/chat-sdk-adapter.

What you get

  • Inbound parsing — Resend hands the email to NanoClaw with parsed headers, plain text, and HTML.
  • Outbound from your domain — replies come from bot@yourdomain.com (or whatever RESEND_FROM_ADDRESS is).
  • Thread continuity — replies preserve In-Reply-To so email clients keep the conversation threaded.
  • Webhook signature verification rejects forged events.

Tips

  • Email is async — response expectations are minutes-to-hours, not seconds. The agent doesn’t need to be live in the moment, which makes this a good channel for batch tasks or end-of-day summaries.
  • Wire to the same agent group as other personal channels for unified memory across email and chat.
  • The platform ID is your bot’s own from-address. Each external sender gets their own thread.
  • Domain verification is the slowest part of setup. Do it ahead of time — it doesn’t depend on the rest of NanoClaw.