> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peachjam.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Resend

> Connect Resend so PeachJam projects can use your workspace Resend account for product email workflows.

> Connect Resend so PeachJam projects can use your workspace Resend account for product email workflows.

> Status: Available. This page documents the workspace connector setup flow and production review responsibilities.

## What the connector does

Resend is an app and chat connector. Workspace admins connect a Resend API key once, then PeachJam stores it as a managed workspace-level connection.

Use Resend when a project needs product email such as invitations, receipts, notifications, onboarding messages, order updates, booking confirmations, or opt-in digests.

## How Resend connections work

Each Resend connection uses one Resend API key. You can create multiple connections when you need separate credentials for staging, production, customers, or sender identities.

Connections belong to the workspace, not to individual end users of the generated app. Resend usage and billing stay with your Resend account.

> The connector setup flow stores and validates credentials. Review and test any generated email workflow before using it for production sends.

## Before you start

Create or choose a Resend account and make sure the sending domain and sender addresses you plan to use are configured in Resend.

Create a Resend API key from the Resend dashboard. PeachJam validates that the key starts with `re_` and that Resend accepts it before storing the connection.

- Open Resend API keys from the connector form's Get value link.
- Use a temporary setup key if you want to verify the connector first.
- Do not paste Resend API keys into prompts or generated client-side code.

## Connect Resend

Open Dashboard, then Connectors. Select Resend, choose Add connection, and select App + chat connector.

Enter a display name, paste the Resend API key, choose who can use the connection, accept Resend's terms, and click Connect.

- Workspace admins and owners can create and manage Resend connections.
- Selected users limits connector use to the people you add.
- Invite entire workspace makes the connection available to all workspace members who can use connector-backed app workflows.
- The API key is stored encrypted and is never returned to the browser after creation.

## Use Resend in an app

After the connection is created, ask PeachJam to add the email workflow you need. Include the trigger, recipient, sender, email content, and product state that should appear in the message.

Review generated email behavior before production. Test with real recipient addresses you control, then verify sender domains, templates, unsubscribe requirements, logs, and error states in Resend.

- Example: Add an invitation email when an admin invites a teammate.
- Example: Send a payment receipt after checkout succeeds.
- Example: Send a weekly digest to users who opted in.

## FAQ

You need your own Resend account and API key. PeachJam does not create or bill the Resend account for you.

You can create multiple Resend connections for different environments or apps. Delete unused connections from PeachJam and revoke old keys in Resend.

If email is not sending, check the API key, sender and domain setup, generated app logs, and Resend activity logs first.

## Security and troubleshooting

Keep Resend credentials scoped to the workspace that needs them. Delete unused PeachJam connections and revoke old Resend API keys from the Resend dashboard.

If setup fails, check that the key begins with `re_`, has not been revoked, and belongs to the Resend account you expect. If delivery fails later, inspect Resend logs and domain verification first.

> PeachJam stores only encrypted credentials and redacted metadata. Connection lists show hints, not raw API keys.