Connect Resend
Send email from AXO triggers.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
api_key | A private server-side credential for the selected provider account. |
from | Verified sender address. |
subject | Optional subject; otherwise the trigger name is used. |
reply_to | Optional reply address. |
Connect
Open Integrations, find Resend, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Verify the sender/domain in the email provider before configuring AXO.
- Create an email trigger and select an email identifier. Its rendered payload becomes the message content. Keep recipients limited to the audience intended for the message.
Verify the result
The check reads /api-keys; it sends no email. A restricted sending-only key may fail this read even if sending is permitted. Verify delivery with a controlled recipient after the trigger is ready.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Check sender-domain verification, sending permissions, and recipient identity. Review trigger History and the provider’s delivery log separately.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.