Connecting Resend

What this is for in Lazycom

Resend sends outbound email from your Lazycom dashboard and automations (order confirmations, broadcasts, etc). It's outbound only — inbound email and reply ingestion aren't implemented, so a customer's email reply won't appear anywhere in Lazycom. Go to Settings → Apps and press "Switch on" on the Resend card. You'll paste a Resend API Key and a "from" email address, then press "Test Connection".

Finding the values in Resend's dashboard

1. Sign in at resend.com and add your sending domain under Domains → Add Domain if you haven't already (see "Verifying your sending domain" below) — Resend strongly recommends sending from a subdomain (e.g. mail.yourstore.com) rather than your bare root domain.
2. Go to API Keys (resend.com/api-keys) and click Create API Key.
   • Choose Sending access and restrict it to the one domain you verified — a key scoped that way can only send from that domain, so a leaked key can't be used to send from anything else in your account. Save a separate, unrestricted Full access key for your own dashboard work; never paste that one into Lazycom or anywhere else.
   • Resend shows the key's value once. Copy it immediately into Lazycom's Resend API Key field — you can't view it again afterward.
3. In Lazycom's Email From Address field, enter an address at the domain you just verified (e.g. orders@mail.yourstore.com). Sending from an unverified domain will fail or land in spam.

Verifying your sending domain

When you add a domain in Resend, it generates DNS records for you to add at your domain registrar (the same place you manage the domain's other DNS records — GoDaddy, Namecheap, Cloudflare, etc, not Lazycom):

• An SPF record (TXT) — lists which mail servers may send on the domain's behalf.
• A DKIM record (TXT, selector resend._domainkey) — a public key used to sign outgoing mail so receiving servers can confirm it wasn't tampered with. Copy each record's exact type, host/name and value from Resend's Domains page into your DNS provider — don't retype them by hand. DNS changes can take up to 24 hours to propagate; Resend's Domains page shows "SPF/DKIM missing" warnings until they resolve, then flips the domain to verified.

Testing the connection

Use the Test Connection button on the Resend card after saving your key and from-address. It makes a read-only, authenticated call to Resend to confirm the key works — it does not send a real email.

Troubleshooting

• "No active connection configured" on test — save both the API key and the from-address; both are required.
• Emails not arriving / marked as spam — check the domain's status on Resend's Domains page; SPF/DKIM must show verified, not just DNS records added.
• Connection test fails with an HTTP error — the key may have been restricted to a domain that no longer matches, or was deleted/rotated in Resend after being saved in Lazycom.

Safety

Never paste your Resend API key into this chat — paste it directly into the Lazycom field on the app's card in Settings → Apps. If it was ever exposed elsewhere, delete it from resend.com/api-keys and create a new one (sending access, restricted to your domain), then update it in Lazycom.