Email actions are wonderfully quiet. That is why success and failure paths matter.
Resend Configuration Fields
| Field | Purpose |
|---|---|
| API key | Credential used to call Resend. |
| From email | Sender address connected to the Resend account. |
| To email | Recipient address for the workflow action. |
| Subject | Email subject line. |
| Text body | Plain text email content. |
Good Email Follow-Up Uses
Appointment details
Send a confirmation after a successful booking call.
Support summary
Send a ticket-style summary after intake.
Sales follow-up
Send next steps after a qualified lead call.
Failure fallback
Send a manual-review notice when another application action fails.
Resend Versus Wati
| Need | Choose |
|---|---|
| Formal written confirmation with subject and body | Resend. |
| WhatsApp reminder or template follow-up | Wati. |
| Internal operations alert | Resend. |
| Consumer reminder on a phone-first channel | Wati, if the recipient and template rules fit. |
Use Resend In A Workflow
Write subject and body
Include enough context that the recipient understands why they received the email.
Email Action Checks
From email fails
From email fails
Confirm sender is valid for the connected Resend account and is allowed to send.
Recipient is empty
Recipient is empty
Map a lead variable or static value to recipient email. Empty recipient fields should go to a failure path.
Subject lacks context
Subject lacks context
Use lead variables or call attributes to make it recognizable, such as appointment date or caller name.
Action fails in workflow
Action fails in workflow
Check failure output and integration invocation details before editing unrelated nodes.
Related Reading
Connecting Integrations
Connect Resend.
Using Integrations In Workflows
Run email actions.
Application Nodes
Map email fields.
Integration Functions
Debug Resend action results.