← Back to marketplace
Resend -- Email Integration Expert
SkillSkill
Your Resend expert that builds transactional emails, manages domains, and automates email workflows.
MarketingAll platformsv3
About
name: resend description: > Build transactional email with Resend: templates, domain verification, and webhooks. USE WHEN: User needs transactional email setup, domain DNS configuration, email templates, webhook handling, or multi-tenant email architecture with Resend. DON'T USE WHEN: User needs email marketing sequences. Use Ghost Writer for email copy. Use Signal for email campaign analytics. OUTPUTS: Email templates, domain configurations, webhook handlers, batch sending pipelines, multi-tenant architectures, deliverability audits. version: 1.1.0 author: SpookyJuice tags: [resend, email, react-email, transactional, deliverability] price: 14 author_url: "https://www.shopclawmart.com" support: "brian@gorzelic.net" license: proprietary osps_version: "0.1" content_hash: "sha256:fa844189e8b7487c4f96782810a038e80788947cbc5f75c83c1c7754de94b68e"
# Resend
Version: 1.1.0 Price: $14 Type: Skill
Description
Production email infrastructure with Resend — beyond resend.emails.send(). The API is clean but the hard part isn't sending one email — it's building the infrastructure around it: DNS records that actually pass authentication checks, webhook pipelines that handle retry behavior, React Email templates that render in every client, and multi-tenant isolation that protects your deliverability.
Prerequisites
- Resend account with API access
- API key:
RESEND_API_KEY - Domain you control (for custom sender domains)
- Access to domain DNS records (for SPF, DKIM, DMARC)
Setup
- Copy
SKILL.mdinto your OpenClaw skills directory - Set environment variables:
export RESEND_API_KEY="re_..." - Reload OpenClaw
Commands
- "Set up transactional email with Resend"
- "Verify my domain for Resend"
- "Build a React Email template for [type]"
- "Set up webhook handling for delivery events"
- "Implement batch sending with rate limiting"
- "Design multi-tenant email for [SaaS app]"
- "Debug deliverability issues"
Workflow
Domain Verification
- Domain registration — add your sending domain in Resend dashboard or via API. This generates the DNS records you need to add.
- SPF record — add the TXT record for SPF. If you already have an SPF record, append Resend's include directive — don't create a duplicate SPF record (only one allowed per domain).
- DKIM records — add the CNAME records for DKIM signing. These allow Resend to sign emails on behalf of your domain. Propagation takes 1-72 hours depending on registrar.
- DMARC policy — if you don't have DMARC, add a basic policy:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. Start withp=none(monitoring), then move top=quarantine, thenp=rejectonce you're confident. - Verification polling — check verification status via API or dashboard. Common failures: CNAME vs. TXT record confusion at the registrar, trailing dots in record values, and CDN/proxy interference.
- Deliverability test — send a test email to Gmail, Outlook, and Apple Mail. Check headers for SPF=pass, DKIM=pass, and DMARC=pass. Use mail-tester.com for a comprehensive deliverability score.
React Email Templates
- Template architecture — organize templates by type: transactional (receipt, password reset), notification (new message, status change), and marketing (welcome, re-engagement). Share common components across templates.
- Component design — build reusable components:
<EmailHeader>,<EmailButton>,<EmailFooter>,<EmailCard>. Use React Email primitives:<Html>,<Head>,<Body>,<Container>,<Section>,<Text>,<Button>,<Img>. - Styling — use inline styles (email clients strip
<style>tags). React Email handles this with thestyleprop. For consistent rendering: use table layouts for complex structures, system fonts as fallbacks, and test in multiple clients. - Preview and testing — use
email devto preview templates locally with hot reload. Test rendering in: Gmail (web and mobile), Outlook (web and desktop — they render differently), Apple Mail, and Yahoo Mail. - Dynamic content — templates accept props for personalization: recipient name, order details, action URLs. Define a TypeScript interface for each template's props to catch missing data at compile time.
- Template versioning — version templates alongside your application code. Breaking template changes get a new template, not an edit to the existing one. This prevents sending broken emails during deployments.
Webhook Handling
- Endpoint setup — create a webhook endpoint in your API that accepts POST requests. Register the URL in Resend dashboard with the events you want:
email.sent,email.delivered,email.bounced,email.complained,email.opened,email.clicked. - Signature verification — verify the
svix-signatureheader using the Resend webhook secret. Reject unverified webhooks. Use thesvixlibrary for verification. - Event handling — implement handlers for each event type:
email.delivered— update delivery status in your databaseemail.bounced— add to suppression list, stop sending to this addressemail.complained— immediate suppression, investigate the email that triggered the complaintemail.opened/email.clicked— track engagement metrics
- Suppression list management — maintain a suppression list of bounced and complained addresses. Check against this list before every send. Continuing to send to bounced addresses destroys sender reputation.
- Idempotent processing — store processed webhook IDs. Resend retries failed webhook deliveries — your handler will see duplicates. Process each event exactly once.
- Alerting — set up alerts for: bounce rate exceeding 2% (danger zone), complaint rate exceeding 0.1% (critical), and delivery rate dropping below 95%
Output Format
📧 RESEND — [IMPLEMENTATION TYPE]
Project: [Name]
Domain: [sending domain]
Date: [YYYY-MM-DD]
═══ DOMAIN STATUS ═══
| Record | Type | Status | Value |
|--------|------|--------|-------|
| SPF | TXT | ✅ Pass | [record] |
| DKIM | CNAME | ✅ Pass | [record] |
| DMARC | TXT | ✅ Pass | [record] |
═══ TEMPLATES ═══
| Template | Type | Props | Tested |
|----------|------|-------|--------|
| [name] | [transactional/notification] | [prop list] | [clients tested] |
═══ WEBHOOK EVENTS ═══
| Event | Handler | Action | Alert Threshold |
|-------|---------|--------|----------------|
| email.bounced | handleBounce | Suppress address | >2% bounce rate |
═══ DELIVERABILITY ═══
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Delivery Rate | [%] | >98% | 🟢/🟡/🔴 |
| Bounce Rate | [%] | <2% | 🟢/🟡/🔴 |
| Complaint Rate | [%] | <0.1% | 🟢/🟡/🔴 |
Common Pitfalls
- Duplicate SPF records — only one SPF TXT record is allowed per domain. If you already have one, append Resend's include — don't create a second record.
- Not checking suppression lists — sending to previously bounced addresses destroys sender reputation. Always check your suppression list before sending.
- Outlook rendering — Outlook uses Word's HTML renderer, which supports approximately 1998-era HTML. Test every template in Outlook specifically and use table layouts for complex structures.
- Missing unsubscribe headers — transactional emails don't require unsubscribe, but marketing emails do. Include
List-Unsubscribeheaders to avoid spam filters. - Rate limit handling — Resend has per-second and per-day send limits by tier. Implement a send queue with rate limiting rather than firing all emails at once.
Guardrails
- Never sends without domain verification. Emails from unverified domains have terrible deliverability. Verify domain first, send second.
- Suppression lists are enforced. Every send checks against the suppression list. Bounced and complained addresses are never emailed again without explicit review.
- Rate limits respected. All batch operations use rate-limited queues. No burst sending that could trigger throttling or account suspension.
- Templates tested before production. Every template is previewed in Gmail, Outlook, and Apple Mail before first production send. No "it works in my email client" deployments.
- Webhook signatures verified. Unverified webhook payloads are rejected. No processing of potentially spoofed delivery events.
- Deliverability monitoring. Bounce and complaint rates are tracked with alerts. Reputation damage is caught early, not after Gmail starts rejecting your emails.
- Test mode enforced in development. Development and staging environments use Resend's test API key or a sandboxed domain. No production emails are ever sent from local or CI environments.
Support
Questions or issues with this skill? Contact brian@gorzelic.net Published by SpookyJuice — https://www.shopclawmart.com
Core Capabilities
- resend
- react-email
- transactional
- deliverability
Customer ratings
0 reviews
No ratings yet
- 5 star0
- 4 star0
- 3 star0
- 2 star0
- 1 star0
No reviews yet. Be the first buyer to share feedback.
Version History
This skill is actively maintained.
Version 3Latest
March 8, 2026
v2.1.0 — improved frontmatter descriptions for better OpenClaw display
Version 2
March 1, 2026
v2.1.0 — improved frontmatter descriptions for better OpenClaw display
Version 1
February 27, 2026
v1.1.0 — expanded from stub to full skill: domain verification, React Email templates, webhook handling
One-time purchase
$14
By continuing, you agree to the Buyer Terms of Service.
Creator
SpookyJuice.ai
An AI platform that builds, monitors, and evolves itself
Multiple AI agents and one human collaborate around the clock — writing code, deploying infrastructure, and growing a shared knowledge graph. This page is a live dashboard of the running system. Everything you see is real data, updated in real time.
View creator profile →Details
- Type
- Skill
- Category
- Marketing
- Price
- $14
- Version
- 3
- License
- One-time purchase
Works With
OpenClawRaw FilesClaude ProjectsCustom GPTsCursor
Works with OpenClaw, Claude Projects, Custom GPTs, Cursor and other instruction-friendly AI tools.
Works great with
Personas that pair well with this skill.