> ## Documentation Index
> Fetch the complete documentation index at: https://developers.perkstar.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your Resend account

> Set up a verified domain and activate email sending inside Perkstar's integrations workspace.

The complete flow stays in **Integrations → Resend → Connect Resend**. Its progress
steps are **Prepare → Connect → Test delivery → Activate**.

## Have these details ready

| Field in Perkstar | What to enter |
| - | - |
| Sending email address | An address on the exact domain verified for sending in your Resend account, such as `loyalty@mail.example.com` |
| Reply-to email address | The mailbox where your team receives customer replies |
| Verified Resend domain ID | The ID of that verified domain in Resend, not the domain name |
| Temporary full-access setup key | A Resend API key that can inspect the domain and create the connection resources |

Use your own domain and mailbox. Do not enter a Perkstar domain, a password or a
key belonging to a different business. A domain and its subdomain are different:
verifying `example.com` does not satisfy an exact sender check for `mail.example.com`.

**1. Verify your sending domain in Resend**

In your [Resend account](https://resend.com/domains), add the domain you
own, follow its DNS instructions and wait until it is verified with sending
enabled. Copy its domain ID. Domain verification is completed in Resend;
Perkstar does not modify your DNS records.

**2. Create a temporary setup key**

Open [Resend API keys](https://resend.com/api-keys) and create a full-access
key for setup. Keep it private. Perkstar uses it to create a separate
sending-only key restricted to the verified domain and a signed delivery
webhook. Perkstar does not store the temporary full-access key.

**3. Connect inside Perkstar**

Sign in as the business owner and confirm the correct business. Open
**Integrations → Resend → Connect Resend**, enter the four details and read
the connection terms. Tick the acknowledgement, then choose **Connect and
test Resend**. This creates the connection resources; it does not activate
customer sending.

**4. Wait for the signed delivery test**

The test goes only to Resend's `delivered@resend.dev` test address. No
customer receives it. Choose **Refresh status** while waiting. The
connection must reach **Test passed — ready to activate** before you can
continue. Provider acceptance alone is not enough: Perkstar requires the
signed delivery event for this test.

**5. Activate your own account**

Choose **Use my Resend account**. Confirm that the current sending account
now shows your Resend sender. You can revoke the temporary full-access setup
key in Resend; retain the named Perkstar sending key and webhook while using
the integration.

## Check the result

* **Manage Resend** still appears inside the integration workspace.
* The selected sending account shows your sender and the connection is connected.
* A saved connection is not a guarantee that every future email will be delivered.
* No stopped campaign has restarted automatically. Review the campaign separately
  before deliberately choosing a new send or retry.

## If setup does not finish

| What you see | What to check |
| - | - |
| Domain not verified or inaccessible | Exact sender domain, sending-enabled status, domain ID and access of the temporary setup key |
| Waiting for signed delivery confirmation | Refresh status; check the test email and webhook delivery in Resend. Do not activate based only on an accepted event |
| Setup needs attention | Read the error. Correct the provider configuration, disconnect the failed connection and reconnect |
| Only the owner can manage | Use the actual owner's login, outside a support or impersonation session |
| Existing connection | Inspect its status first. Disconnect deliberately before replacing it |

Do not post API keys or webhook secrets in screenshots, support messages or shared
documents. For a failed test, provide the business account number, time and visible
error instead. Continue with [delivery and recovery](https://developers.perkstar.co.uk/integrations/resend/delivery-recovery.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.