Resend
Resend is a developer-focused email API. Entrig connects to Resend using your API key and sends emails from your verified domain.
What you’ll need
- A Resend account
- A verified domain in Resend (required to send to any address outside
@resend.dev) - A Resend API key. Create one in Resend under API Keys → Create API Key
Configure
-
Open Channels → Email in Settings
From the Entrig dashboard, go to Settings → Channels. Under the Email section, find Resend and click Configure.
-
Enter your API key
Paste your Resend API key, then click Connect. Entrig calls the Resend API to fetch your verified domains.
-
Select a domain
Choose a verified domain from the dropdown.
If Resend returns no domains (this happens with send-only API keys that have
Sendscope but notDomain: Read), you can skip the selector and enter your From address manually instead. -
Set the From address
Enter the email address notifications will be sent from (e.g.
notifications@yourdomain.com). It must use the domain you selected. -
Set the From name (optional)
Enter a display name that recipients will see (e.g.
My App). -
Save
API key scopes
A full-access API key works out of the box. If you prefer a scoped key, you need at minimum:
| Scope | Purpose |
|---|---|
Emails: Send | Required, used for every notification |
Domains: Read | Optional, allows Entrig to list your domains automatically |
Without Domains: Read, the domain dropdown will not appear. You can still configure by entering the From address directly.
Troubleshooting
”No verified domains found”
Cause: Your API key has send-only scope and cannot list domains, or you have no verified domains in Resend.
Fix: If you don’t have any verified domains, add one in Resend → Domains and complete DNS verification. If you do have domains but are using a send-only key, enter your From address manually. Entrig handles this gracefully.
Emails not arriving
Cause: The domain DNS records (SPF, DKIM) are not fully propagated, or the domain is not yet verified in Resend.
Fix: Check your domain status in the Resend dashboard. DNS changes can take up to 48 hours to propagate globally.
”Invalid API key”
Cause: The API key was deleted or regenerated in Resend after it was saved.
Fix: Generate a new API key in Resend and reconfigure the channel.