> For the complete documentation index, see [llms.txt](https://docs.boomerangme.cards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.boomerangme.cards/white-label/resend.md). # Resend ## Connecting Resend to Boomerangme Boomerangme can send emails to your customers through your own Resend account. Emails will then arrive from your name and your domain (e.g. `hello@yourcompany.com`) instead of the platform's shared address, which improves deliverability and brand recognition. {% hint style="info" %} **Billing**: Email sending is billed directly by Resend according to their pricing. Boomerangme does not charge for these emails. {% endhint %} ### What you'll need * Your own domain and access to its DNS records (Cloudflare, GoDaddy, Reg.ru, Namecheap, etc.) * A Resend account (you can start on the free plan) * Admin rights in Boomerangme * About 15 minutes; DNS propagation can take up to 24 hours, though it usually completes within a few minutes ### Overview 1. Sign up for Resend and confirm your email. 2. Add and verify your domain in Resend (DNS records). 3. Create an API key with **Full access** permissions. 4. In Boomerangme, paste the key, fetch the account list, and fill in sender addresses. 5. Send a test email and check its status in Resend → Logs. {% hint style="warning" %} **Order matters**: verify your domain in Resend **before** connecting it in Boomerangme. The platform pulls its domain list from Resend, and if there are no verified domains yet, there will be nothing to select. {% endhint %} ### Step 1. Sign up for Resend 1. Go to [resend.com/signup](https://resend.com/signup). 2. Sign up with Google, GitHub, or email + password, then click **Create account**. 3. Resend will show a **Check your email** screen — open the "Confirm your account" email and click **Confirm account**. 4. After logging in, you'll land on the "Send your first email" onboarding screen with an **Add API Key** button. This key is created with limited **Sending access** permissions and won't work for the Boomerangme integration — you can skip it or leave it as is; a separate key will be created later. ### Step 2. Add a domain in Resend 1. In the left-hand menu, open **Domains → Add domain**. 2. **Name** — enter the domain or subdomain you'll send emails from. A dedicated subdomain (e.g. `mail.yourcompany.com`) is recommended, so your sending reputation doesn't affect your main corporate mailbox. 3. **Region** — select the sending region closest to your customers: `us-east-1` (Virginia), `eu-west-1` (Ireland), `sa-east-1` (São Paulo), or `ap-northeast-1` (Tokyo). Resend suggests the nearest one automatically. 4. **Advanced options** — can be left as is. This is where you'd configure a custom open/click tracking subdomain and a custom return-path. 5. Click **Add domain**. {% hint style="danger" %} **The region can't be changed later.** To switch regions you'll need to delete the domain and re-add it with new DNS records. Choose the region deliberately the first time — Boomerangme stores it together with the connection. {% endhint %} ### Step 3. Add the DNS records Once the domain is added, Resend will display a **DNS Records** block. There are two ways to complete this step. #### Option A. Auto configure Works if your DNS is managed by a provider that supports Domain Connect — for example, Cloudflare. This is the simplest path. 1. Click **Auto configure** — a pop-up window will open asking you to sign in to your DNS provider (for Cloudflare, this is `dash.cloudflare.com`). 2. Sign in to your DNS provider account and confirm access. 3. The provider will create all the required records automatically — no manual entry needed. The domain timeline will show "Domain created" → "Checking DNS" → "Verified". You can double-check the result with your provider: the DNS records section will show 5–6 new rows (DKIM, SPF, MX, DMARC). Their structure is described below in case you ever need to edit something manually. #### Option B. Manual setup Open your domain's DNS management panel and create the records exactly as Resend shows them. | Purpose | Type | Name | Content | Priority | | ------------------------------------------- | ---- | ------------------- | -------------------------------------------- | -------- | | DKIM — email signing (required) | TXT | `resend._domainkey` | `p=MIGfMA0GCSqG...` (unique key from Resend) | — | | SPF — sending authorization (for sending) | TXT | `send` | `v=spf1 include:amazonses.com ~all` | — | | Bounce/feedback handling (for sending) | MX | `send` | `feedback-smtp..amazonses.com` | 10 | | Inbound email receiving (required) | MX | `@` (domain root) | `inbound-smtp..amazonaws.com` | 10 | | DMARC — authentication policy (recommended) | TXT | `_dmarc` | `v=DMARC1; p=none;` | — | {% hint style="info" %} **About DMARC**: Resend marks this record as optional — it's not required for domain verification. However, Gmail, Yahoo, and Outlook require DMARC from high-volume senders, and it improves domain trust even at lower volumes. A value of `p=none` doesn't block anything — it only enables monitoring. We recommend adding it. {% endhint %} **Common reasons verification fails:** * Copy values using the **copy** button directly from Resend, not from a written guide — the DKIM key is unique to each domain. * Record names are relative to your domain. If your DNS panel asks for a fully qualified name, enter `send.yourcompany.com`, not `send.yourcompany.com.yourcompany.com`. * In Cloudflare, proxying must be **disabled** — the status should be **DNS only** (grey cloud), not **Proxied**. * TTL should be set to **Auto** (or the lowest available value). * The `send` subdomain must have exactly **one MX record**, and all MX records for the domain must point to the same region. * If the domain already has an SPF record for other mail, don't add a second one at the root — Resend's record lives on the `send` subdomain and won't conflict with your main mail. Once the records are added: 1. In Resend, click **I've added the records / Verify**. 2. Wait for all records to reach **Verified** status. This usually takes a few minutes, up to a maximum of 24 hours. If it's taking too long, click **Restart verification**. #### If the domain is already used in another Resend account Resend will show a warning and offer a **Claim domain** procedure: it will issue a TXT record like `resend-domain-verification=...` for the domain root (`@`). Add it to your DNS and run the verification — the domain will transfer to your team, and the previous account's access will be revoked. {% hint style="warning" %} * After the transfer, the domain gets **new DKIM keys** — the old records won't work, and DNS must be updated and re-verified. * If emails are currently being sent from the old account, Resend will block the takeover and ask you to delete the domain from that account first. Log in there and remove the domain manually. {% endhint %} ### Step 4. Create an API key for the integration 1. In the Resend left-hand menu, open **API keys → Create API key**. 2. **Name** — use a descriptive name, e.g. "Boomerangme". 3. **Permission** — select **Full access**. 4. Click **Add** and copy the key immediately (it starts with `re_`). {% hint style="info" %} **Why Full access is required**: when connecting, Boomerangme asks Resend for your list of domains (via the "Get account list" button). A **Sending access** key can only send emails and doesn't expose the domain list, so the connection won't complete. {% endhint %} **Two common questions about the key:** * *"Where do I select a domain when creating the key?"* — The domain selector only appears for **Sending access** keys. A **Full access** key has no such field — that's expected, since it works across all domains on the account, including ones you add later. * *"The key was shown once and now it's gone."* — That's by design; the value can't be viewed again. If you didn't copy it in time, delete the key and create a new one. ### Step 5. Connect in Boomerangme > **Boomerangme > Left-Hand Menu > Settings > White Label** 1. Open **Settings → White Label**. 2. From the buttons at the top-right corner, click **Other Settings**. 3. Find the **Resend** tile and click **Connect Account**. 4. In the "Connecting a Resend account" popup, enter your Resend **API key** in the API Key field, then click **Get account list**. Boomerangme will contact Resend and pull in your verified domains. #### Support for multiple Resend mailboxes It's possible to connect both a primary mailbox for general mailings (registration details, password resets, etc.) and additional mailboxes used exclusively for mailings via Richie. First, select the **primary mailbox** from the list of available mailboxes and enter the sender name. This mailbox is used to send: * welcome emails after your clients (sub-accounts) register * password recovery emails * manager registration emails After selecting the primary mailbox, enter the sender name and choose **additional mailboxes** for mailings via Richie. You can select as many mailboxes as you have configured in your Resend account. After selecting the mailboxes, click **Connect** — you're all set. You're now ready to receive and manage emails seamlessly with Resend and Boomerangme. | Block | What to fill in | Required | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | | Main account | Sender email (the part before `@`), the domain from the dropdown, and the sender name — what customers see in the "From" field. Emails from the company itself, including welcome, password recovery, and manager registration emails, are sent from this address. | Yes | | Sub-account | Address and sender name for emails sent on behalf of your sub-accounts. Can be the same as the main account. | Yes | | Additional Richie AI accounts | Addresses that the Richie AI administrator sends from. Added with the "Add" button, removed with "Remove". Can be left empty. | No | * The **region** is set automatically from the domain's settings in Resend — you don't need to specify it separately. * The domain dropdown only shows **verified** domains. If the list is empty, go back to Step 3. * The **sender name** is your brand's signature (e.g. "Beauty Salon N"), not a technical identifier — customers see it directly. ### Setting up an email sender at the agency level for sub-accounts Centralized email sending is available: the agency connects its own Resend at the agency level and selects a sender address. Sub-accounts can then send emails billed to the agency, without configuring their own Resend. Campaigns are available immediately after a sub-account is created. Each sub-account has a monthly limit of 100,000 messages. Once the limit is reached, sending is paused until the next billing period (or until the limit is increased). Sub-accounts can still connect their own Resend if needed — this option remains unchanged. **The sender name is generated dynamically for each sub-account.** A sub-account–specific variable is automatically appended to the base name, so the displayed sender name is unique for each sub-account. ### Editing the Resend connection At any time, you can edit the connection, select new mailboxes, or disconnect old ones. To do this, use the **Edit** button on the Resend tile. ### Step 6. Test the connection 1. Send a test email from Boomerangme (for example, a test campaign or scenario to your own address). 2. In Resend, open the **Emails** or **Logs** section — every email and its status are shown there. 3. **Delivered** status means everything is working. **Bounced** / **Failed** statuses — open the email to see the reason. 4. Check the email you received: confirm the sender address and name display as configured, and that it didn't land in spam. ### Troubleshooting | Symptom | Cause | What to do | | --------------------------------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | Account list is empty or errors out after pasting the key | Key was created with **Sending access** | Create a new key with **Full access** and use it instead | | Domain list is empty | Domain isn't verified in Resend | Wait for **Verified** status in Resend → Domains | | Domain hasn't verified in over 24 hours | Records added incorrectly, or a value got truncated | Compare each record's name and value against Resend; confirm Cloudflare is set to **DNS only** | | "Multiple regions" error on MX | The domain's MX records point to different AWS regions | Remove extra MX records, keep only the one for the correct region | | Domain is claimed by another Resend team | Domain already added under a different account | Complete **Claim domain**, or delete the domain from the old account | | Emails are delivered but land in spam | No DMARC record, a "cold" domain, or a sudden volume spike | Add a DMARC record (`p=none`), warm up the domain, and monitor complaint rates | | Lost the API key | Keys are only shown once | Delete the old key, create a new one, and update it in Boomerangme | ### Security * A **Full access** key grants full control over the Resend account — sending emails, domains, contacts, and other keys. Treat it like a password. * Don't share the key over messaging apps or expose it in screenshots, screen recordings, or screen shares. * If the key may have been exposed, delete it immediately in Resend → **API keys → … → Delete**, create a new one, and reconnect Boomerangme. * Use a separate, clearly named key for each integration — this makes it easy to revoke access for one service without breaking the others. ### Checklist * [ ] Resend account created, email confirmed * [ ] Domain added, region chosen deliberately * [ ] DNS records added (auto or manual), status **Verified** * [ ] API key created with **Full access** and copied * [ ] Main account and sub-account sender addresses filled in Boomerangme * [ ] Test email delivered, **Delivered** status confirmed in Resend logs