Resend

What it enables in Codexa

• Store a Resend API key encrypted in the workspace, with a connection test.
• Keep the team's Resend credentials in one place; copy them into project environment variables when a generated app sends transactional email.

• test

Setup

Fields on the workspace connection form. Password-type fields are encrypted before storage and never shown again.

1. Open Settings → Integrations in your workspace (requires the admin or owner role).
2. Choose the provider, give the connection a name, and fill in the fields listed above. Secret fields are encrypted before they are stored and are never sent back to the browser.
3. Click Test connection. Codexa makes a single read-only request to the provider to confirm the credentials work.
4. Save. The connection is now available to projects in this workspace.

Required permissions and scopes

• A Resend API key (re_…). A sending-only key is sufficient.
• A verified sending domain in Resend for production email.

Limitations

• Codexa's own account emails use the operator-level email provider (CUSTOMERIO_APP_API_KEY or RESEND_API_KEY), not workspace connections.
• Templates and audiences are not managed by Codexa.