Skip to content
Jooosi
Account
JM Jooosi Mail

Resend

Browse documentation
Overview
Contents
On this page
  1. Before you begin
  2. Supported transport and settings
  3. Create the connection
  4. Verify delivery
  5. Webhooks
  6. Troubleshooting

Resend supports API and SMTP delivery. Each route has its own API key field, and the profile also supports signed Resend webhooks using a separate webhook signing secret.

Before you begin#

  • You need access to the provider account and the Jooosi Mail Connections screen. If the provider requires sender or domain verification, complete it in the provider account first.
  • Copy credentials directly from the provider’s own console into the matching Jooosi Mail field. Keep secret values private; never include them in screenshots or support messages.

Consult provider sending documentation for any provider-side setup requirements.

Supported transport and settings#

  • resend+api (default): Required: Resend API key (secret).
  • resend+smtp: Required: Resend SMTP API key (secret).

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select Resend in Profile.
  3. Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
  4. Review the sender, routing, and advanced settings for this connection.
  5. Choose Create connection to save it.

The SMTP transport uses the fixed Resend username internally, so Jooosi Mail asks only for the SMTP API key. Webhook signing uses a different secret from the sending key.

For the shared form workflow, see Connect a provider.

Verify delivery#

Use Send a test email with a recipient you control; it sends a real message through this connection. Check its status and the email log for the provider response.

Webhooks#

Resend webhooks report sent, delivered, delayed, complained, bounced, opened, and clicked events. Enter the signing secret in the connection’s webhook-secret setting; Jooosi Mail verifies the Svix signature headers. Follow Provider webhooks for the Jooosi Mail URL. Copy this secret from Resend’s console; do not reuse or publish the send API key.

Troubleshooting#

  • For missing-field validation, confirm the scheme and fill all required settings listed above.
  • After a failed test, re-copy the matching credential and inspect the connection status and email log.
  • For send errors, match the API key field to the selected API or SMTP scheme. For webhook verification failures, check the separate webhook signing secret and that svix-id, svix-timestamp, and svix-signature headers are preserved.