Have these details ready
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, 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 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
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.