Resend Email

!Resend Email

Manage Resend from chat — email campaigns, contacts, audiences, domains, templates, and transactional sends via the Resend API.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Resend API access yourself.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│ Resend           │
│   (User Chat)   │     │   (OAuth)    │     │ (Email API)       │
└─────────────────┘     └──────────────┘     └──────────────────┘
          │                       │                       │
          │  1. Install Plugin    │                       │
          │  2. Pair Device      │                       │
          │  3. Connect Resend   │                       │
          │                      │  4. Secure Token       │
          │                      │  5. Proxy Requests    │
          │                      │                       │
          ▼                      ▼                       ▼
    ┌──────────┐          ┌──────────┐          ┌──────────┐
    │  SKILL   │          │ Dashboard│          │ Resend   │
    │  File    │          │ Auth     │          │ Dashboard│
    └──────────┘          └──────────┘          └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Resend again."

Quick Start

# List all contacts
clawlink_call_tool --tool "resend_list_all_contacts" --params '{"limit": 20}'

# List audiences
clawlink_call_tool --tool "resend_list_audiences" --params '{}'

# Send an email
clawlink_call_tool --tool "resend_send_email" --params '{"from": "team@example.com", "to": ["recipient@example.com"], "subject": "Hello", "html": "<p>Hello world</p>"}'

Authentication

All Resend tool calls are authenticated automatically by ClawLink using the user's connected Resend account.

No API key is required in chat. ClawLink stores the credentials securely and injects them into every Resend API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=resend and connect Resend.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for resend in the list.

Verify Connection

clawlink_list_tools --integration resend

Response: Returns the live tool catalog for Resend.

Reconnect

If Resend tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=resend
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration resend

Security & Permissions

• Access is scoped to the Resend account accessible via the connected account.
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (delete contact, delete audience, delete domain) are marked as high-impact and must be confirmed.
• Confirm before sending emails or making broad contact changes — sends are irreversible.

Tool Reference

Audiences & Contacts

Segments & Topics

Domains

Templates

Emails

Webhooks

Broadcasts

Contact Properties

API Keys

Code Examples

List all contacts

clawlink_call_tool --tool "resend_list_all_contacts" \
  --params '{
    "limit": 20
  }'

Create an audience

clawlink_call_tool --tool "resend_create_audience" \
  --params '{
    "name": "Newsletter Subscribers"
  }'

Send an email

clawlink_call_tool --tool "resend_send_email" \
  --params '{
    "from": "team@company.com",
    "to": ["recipient@example.com"],
    "subject": "Welcome to our newsletter",
    "html": "<p>Hello! Thanks for subscribing.</p>"
  }'

Create a contact

clawlink_call_tool --tool "resend_create_contact" \
  --params '{
    "audience_id": "AUDIENCE_ID",
    "email": "newcontact@example.com",
    "first_name": "Jane",
    "last_name": "Doe"
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm Resend is connected.
2. Call clawlink_list_tools --integration resend to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration resend.
5. If no Resend tools appear, direct the user to https://claw-link.dev/dashboard?add=resend.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                      │
│  list → get → retrieve → call                               │
│                                                             │
│  Example: List contacts → Get details → Show results         │
└─────────────────────────────────────────────────────────────┘
                               │
                               ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                     │
│  list → describe → preview → confirm → call                 │
│                                                             │
│  Example: Describe tool → Preview changes → User approves    │
│           → Execute send                                     │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes

• Domain verification requires adding DNS records — allow time for propagation before verifying.
• Emails must have explicit to, cc, or bcc recipients — audience-based sending is not supported.
• Scheduled emails can be cancelled or updated before their scheduled time.
• Batch emails support up to 100 recipients per request.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

```bash

openclaw plugins list

```

1. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
2. If a fresh chat does not help, run:

```bash

openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json

openclaw gateway restart

```

1. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call

1. Ensure the integration slug is exactly resend.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources

• Resend API Documentation
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=resend-mail
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Related Skills

• SendGrid — For Twilio SendGrid email operations

!ClawLink Logo