Actions12
- Mail Actions
- Contact Actions
- Broadcast Actions
Overview
The node integrates with the Resend API to send emails, manage contacts, and handle broadcasts. Specifically, for the Mail - Create Batch Email operation, it allows sending batch emails by providing a JSON payload that defines the email content and optional custom headers. This is useful when you want to send multiple personalized or bulk emails in one request, such as newsletters, promotional campaigns, or notifications.
Practical examples:
- Sending a batch of transactional emails with different content per recipient.
- Dispatching marketing emails with custom headers for tracking or compliance.
- Automating bulk email sends triggered by workflows.
Properties
| Name | Meaning |
|---|---|
| Content (JSON) | The full JSON payload describing the batch email content, including recipients, subject, body, etc. |
| Headers | Optional collection of key-value pairs to set custom headers on the email messages. |
The "Headers" property supports multiple entries, each with a "Key" and "Value" to define metadata headers for the emails.
Output
The node outputs an array of JSON objects representing the response from the Resend API after attempting to send the batch email. Each object typically contains details about the success or failure of the email send operation, such as message IDs, status, or error information.
If binary data were involved (e.g., attachments), it would be included accordingly, but this operation focuses on JSON payloads and responses.
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node depends on the Resend service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API key.
Troubleshooting
- Invalid JSON Payload: If the "Content (JSON)" input is malformed or missing required fields, the API will reject the request. Validate your JSON structure carefully.
- Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is correctly set up in n8n credentials.
- Header Format Issues: Headers must be valid key-value strings; incorrect formatting may cause the API to ignore them or return errors.
- API Rate Limits: Sending large batches frequently might hit rate limits imposed by the Resend API. Monitor usage and adjust accordingly.
- Network/Connectivity Problems: Ensure n8n can reach the Resend API endpoint without firewall or proxy issues.
Links and References
- Resend API Documentation — Official API docs for detailed payload formats and capabilities.
- n8n Documentation — For general guidance on using credentials and creating workflows.