ResendInstall

Overview

This node integrates with the Resend API to send emails. Specifically, the "Create Email" operation under the "Mail" resource allows users to compose and send a single email message. It supports two ways of providing the email content: either by manually mapping individual fields such as recipient, sender, subject, and HTML content, or by directly inputting the entire email payload in JSON format.

Common scenarios for this node include:

• Sending transactional emails like welcome messages, password resets, or notifications.
• Automating marketing or informational emails within workflows.
• Quickly testing email templates by sending custom HTML content.

Example use case: A workflow that triggers when a new user signs up, then sends a personalized welcome email using the node's individual fields mode.

Properties

Name	Meaning
Payload Type	Choose how to provide the email data: "Individual Fields" (manually map To, From, Subject, HTML) or "By JSON" (input full JSON payload).
Content (JSON)	The full email payload in JSON format (used if Payload Type is "By JSON").
To Email	Recipient email addresses; multiple emails separated by semicolons (;).
From Email	Sender's email address.
Subject	Subject line of the email.
HTML Template	HTML content/body of the email.
Additional Fields	Optional extra fields including: - CC: Carbon copy recipients (semicolon-separated emails). - BCC: Blind carbon copy recipients. - Attachments: Names of binary properties containing attachments (semicolon-separated).
Headers	Custom headers for the email; specify key-value pairs to add metadata or control email behavior.

Output

The node outputs an array of JSON objects representing the response from the Resend API after attempting to send the email. This typically includes details about the sent email such as message ID, status, and any metadata returned by the service.

If attachments are included, they are referenced by their binary property names but the node itself does not output binary data directly.

Dependencies

• Requires an API key credential for authenticating with the Resend API.
• The node depends on the Resend email sending service.
• No additional environment variables are explicitly required beyond the API key configuration.

Troubleshooting

• Invalid email addresses: Ensure all email fields (To, From, CC, BCC) contain valid email formats; semicolon-separated lists must be correctly formatted.
• Missing required fields: When using individual fields mode, "To Email", "From Email", "Subject", and "HTML Template" should not be empty.
• Incorrect JSON format: If using the JSON payload option, ensure the JSON is well-formed and matches the expected schema of the Resend API.
• Attachment issues: Verify that binary property names specified in attachments exist and contain valid file data.
• API authentication errors: Confirm that the API key credential is set up correctly and has necessary permissions.
• Headers misconfiguration: Custom headers must have both key and value defined; missing keys or values may cause errors.

Links and References

• Resend API Documentation — Official documentation for the Resend email API.
• n8n Documentation — General guidance on creating and using nodes in n8n workflows.