Send email from your own domain with Resend

By default, Polzy sends email from its own shared account. Connect your Resend account and every email this workspace sends to participants — campaign invitations and reminders, thank-you and event emails, workflow emails and replies in a conversation — goes out through Resend, from an address on your own domain. People see a sender they recognise, and your domain's reputation is your own.

Before you start

You need:

• A workspace on Team or higher, and the Admin role in it.
• A Resend account, with the right to add a domain and create an API key.
• Access to your domain's DNS, to add the records Resend gives you.
• The address you want to send from, such as surveys@acme.com, on that domain.

How Polzy uses Resend

• All participant email. Once you choose Resend for email, every email the workspace sends to participants goes through it. Polzy's own email — sign-in links, password resets, invoices — still comes from Polzy.
• Who it is from. The From address you enter. The name and reply-to address set under Settings → Branding (Sender name and Reply-to address) take precedence over the From name and Reply-to address entered here.
• What it looks like. Nothing changes: emails keep your workspace's logo and colour.
• What it costs. Resend bills you for these emails. They do not count against your organization's monthly emails in Polzy.
• What comes back. With a webhook in Resend, each message's log shows whether it was delivered, opened, clicked or bounced.

Step 1: Verify your domain in Resend

Mail providers such as Gmail and Outlook trust an email when the domain it comes from says the sender may use it. Three DNS records do that: SPF names the servers allowed to send for your domain, DKIM signs each message so it cannot be altered, and DMARC tells receivers what to do when a message fails both. Resend gives you the first two; you add the third.

1. In Resend, open Domains and click Add Domain.
2. Enter the domain to send from. Resend recommends a subdomain, such as mail.acme.com, so your main domain's email is not affected.
3. Add every record on the Records tab at your DNS host, exactly as shown. If your DNS host is Cloudflare, set CNAME records to DNS only, not proxied.
4. Wait until Resend shows the domain as verified. It often takes 15 minutes, and can take up to 72 hours.
5. Add a DMARC record: a TXT record at _dmarc on your domain. v=DMARC1; p=none; is a safe start that changes nothing while you check your reports.

Your From address must be on exactly the domain you verified: with mail.acme.com verified, send from surveys@mail.acme.com, not surveys@acme.com.

See Resend: Add and verify a domain and Resend: Implementing DMARC. Gmail requires SPF or DKIM from every sender, and DMARC as well from anyone sending more than 5,000 messages a day: see Google: Email sender guidelines.

Step 2: Create an API key

1. In Resend, open API Keys and create a key. Name it Polzy.
2. Give it Full access. Polzy reads your list of domains to check that your From address is on a verified one, which a key limited to sending cannot do.
3. Copy the key, which starts with re_. Resend shows it once.

See Resend: Manage API keys.

Step 3: Connect Resend in Polzy

1. Open the place to connect it:
   • On Team: Messages, then the Integrations tab. Under Providers, find Resend and click Set up.
   • On Business and up: Integrations in the sidebar, the Available tab, then Connect on Resend's row.
2. In the Connect Resend panel, fill in the fields:

1. Click Test connection. You should see Connected to Resend, sending as and your address.
2. Click Connect.

Integration

Connect ResendKeys are encrypted and only used on your behalf.

2 of 2 required

Credentials

Webhook signing secretOptional

API keyRequired

From addressRequired

From nameOptional

Reply-to addressOptional

Encrypted at restTest connectionConnect

On Team, the Integrations tab of Messages lists the providers you can connect, with Configure and Test once one is connected:

Messages

MessagesIntegrations

Providers1 live · 6 available

ResendEmail

Connected

TestConfigure

SendGridEmail

Not connected

Set up

MailgunEmail

Not connected

Set up

TelnyxSMS and WhatsApp

Not connected

Set up

Step 4: Choose Resend for email

Connecting Resend does not switch your email over yet. Choose it once for the workspace:

1. Open Settings, then the Notifications tab, and scroll to Channels.
2. On the Email row, change Polzy · shared account to Resend.
3. Make sure the switch on the row is on.

Channels

Channels appear here once a provider is connected under Connect. Until then, Polzy sends on its own shared account with a lower daily cap.

EmailOnInvitations, reminders and conversation replies. · 1,240 sent · 30dResend

SMSOffShort invitations for people without a desk. · not sendingPolzy · shared account

WhatsAppOffTwo-way messages through a Business number. · not sendingPolzy · shared account

SlackOffChannel posts and direct messages to admins. · not sendingNo provider connected

TeamsOnPosts into a Teams channel your workspace watches. · not sendingNo provider connected

From now on every email the workspace sends goes through Resend.

Step 5: Get delivery statuses back

Without this step, emails still go out, but their log stops at Sent. With it, Polzy learns from Resend what happened to each one.

1. In Polzy, open Integrations, click Resend's row to open its page, and find Receiving. Copy the address shown there.
2. In Resend, open Webhooks and click Add Webhook.
3. Paste the address as the endpoint and select the email events: delivered, bounced, complained, opened, clicked and delivery delayed. To receive replies on your own domain too (see below), also select received.
4. Save, and copy the webhook's signing secret, which starts with whsec_.
5. In Polzy, click Configure on Resend, paste it into Webhook signing secret and click Save.

Receiving

Give this address to Resend so it can report what happened to your messages.

Delivery receipts

Replies

Copy

In Resend, add a webhook with this URL and subscribe to the email events. Copy the signing secret it shows into the field above.

Without the signing secret, Polzy refuses every event from Resend as unsigned, and the Activity section of Resend's page shows Incoming message refused. See Resend: Create a webhook.

Opened and Clicked appear only when open and click tracking is on for your domain in Resend. A permanent bounce or a spam complaint marks the message Bounced, and Polzy stops emailing that address from this workspace.

Replies. A reply in a Polzy conversation comes back through Polzy's own reply address, whichever sender you use, so it needs nothing here. If you also receive email for your own domain in Resend and send its received events to the same webhook, a reply from someone with an open email conversation is added to that conversation. See Resend: Custom receiving domains.

Test it

Send a small campaign with only yourself in the audience (see Send a survey with a campaign). Then open Messages: your email should move from Sent to Delivered, and to Opened when you open it. Open the email's details in your mail app to check that SPF, DKIM and DMARC say pass.

Troubleshooting

Good to know

• If Resend stops working, Polzy keeps trying it, because the next attempt may work, and marks it Needs attention. If you disconnect it, or your plan no longer includes your own email sender, email goes back to Polzy's shared account and counts against your monthly emails again.
• One email sender at a time. The Email row takes one provider. You can connect another to have it ready, and switch on the row.
• What Polzy keeps. The API key and the signing secret are stored encrypted and never shown again.

Useful links

• Resend: Add and verify a domain
• Resend: Implementing DMARC
• Resend: Manage API keys
• Resend: Create a webhook
• Resend: Custom receiving domains
• Google: Email sender guidelines