Resend Connection
SkillCommunicationConfigure 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Resend Connection skill
What this skill tells your AI
The instructions your AI receives, as published by rejot-dev/fragno in apps/backoffice/content/static/skills/resend-connection/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 61
- Forks
- 6
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
resend-connection- Source
- github.com/rejot-dev/fragno