# Resend Connection

> Configure and automate the Backoffice Resend email capability. Use when setting up Resend delivery, inspecting email threads, replying to emails, or debugging Resend webhooks and durable hooks.

- Skill: `rejot-dev/resend-connection` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rejot-dev/resend-connection`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rejot-dev/resend-connection/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: rejot-dev (https://skillmd.com/u/rejot-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rejot-dev/resend-connection

---


# Resend Connection

Use this skill for organization-scoped Resend email delivery, email thread state, and reply
automation.

# Resend configuration

Configuration fields:

- `apiKey`: Resend API key. Secret; required on first setup.
- `defaultFrom`: default sender address; required on first setup.
- `defaultReplyTo`: optional reply-to address or list of addresses.
- `webhookBaseUrl`: public Backoffice origin or tunnel URL used for Resend webhooks.

Setup notes:

- Use a verified sender/domain for `defaultFrom`.
- The webhook base URL must be reachable by Resend.

# Resend events

Cataloged automation events:

- `source`: `resend`, `eventType`: `capability.configured` — fires after Resend is configured for an
  organization for the first time.

Resend maintains email thread state and hook work behind the `resend` hook scope.

The `/resend` filesystem also exposes email thread snapshots as Markdown files, one file per thread.

# Resend tools

Resend tools can:

- list email threads;
- load a thread with messages and a Markdown snapshot;
- send a plain-text reply to an existing thread.

Use codemode first. The `resend` provider exposes thread snapshot, thread listing, and reply
functions. Use `/resend` when reading existing thread context as files is more convenient than
calling provider functions.