Resend icon

Resend

Resend API node
Join our community

Actions12

Overview

The node implements integration with a broadcast messaging service, specifically allowing users to create and send email broadcasts to a specified audience. This is useful for marketing campaigns, newsletters, or any scenario where you want to send the same message to multiple recipients grouped as an audience.

For example, a user can create a broadcast to welcome new subscribers by sending a personalized HTML email to all members of a particular audience list.

Properties

Name Meaning
Audience ID The unique identifier of the audience to which the broadcast email will be sent.
From Email The sender's email address that will appear in the "From" field of the broadcast email.
Subject The subject line of the broadcast email.
Message The content of the email message; supports plain text or HTML format.
Reply To (Optional) One or more reply-to email addresses separated by semicolons.
Name (Optional) A friendly internal name for the broadcast used for reference within the system.

Output

The node outputs JSON data representing the result of the broadcast creation operation. This typically includes information such as broadcast status, IDs, timestamps, or confirmation messages returned from the broadcast service API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the external broadcast/email service.
  • The node depends on the external Resend API service to send emails and manage audiences.
  • Proper configuration of the API key credential in n8n is necessary for successful execution.

Troubleshooting

  • Invalid Audience ID: If the provided Audience ID does not exist or is incorrect, the API call will fail. Verify the Audience ID is correct and accessible.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is correctly configured in n8n.
  • Email Format Issues: Improperly formatted email addresses in "From Email" or "Reply To" fields may cause errors. Use valid email formats and separate multiple reply-to addresses with semicolons.
  • Empty Required Fields: Omitting required fields like Audience ID, From Email, Subject, or Message will likely result in errors. Make sure all mandatory inputs are provided.
  • API Rate Limits: Sending too many broadcasts in a short time might trigger rate limiting by the external service. Check service limits and adjust usage accordingly.

Links and References

Discussion