Resend icon

Resend

Resend API node

Overview

This node, named "Resend Node," interacts with the Resend API to perform various actions related to emails, contacts, and broadcasts. Specifically, for the Broadcast resource with the Get Broadcast operation, it retrieves details of a specific broadcast by its ID. This is useful when you want to fetch information about a previously sent or scheduled broadcast message, such as its status, content, or metadata.

Practical examples include:

  • Checking the status or details of a marketing broadcast campaign.
  • Retrieving broadcast data to display in dashboards or reports.
  • Verifying broadcast content before resending or analyzing delivery results.

Properties

Name Meaning
Broadcast ID The unique identifier of the broadcast to retrieve. Example format: UUID string like 479e3145-dd38-476b-932c-529ceb705947.

Output

The node outputs JSON data representing the broadcast details fetched from the Resend API. This typically includes fields such as broadcast ID, status, content, recipients, timestamps, and other metadata related to the broadcast.

If the broadcast contains any binary data (e.g., attachments), the node would handle it accordingly, but based on the provided code and context, the output focuses on JSON structured data describing the broadcast.

Dependencies

  • Requires an API key credential for authenticating with the Resend API.
  • The node depends on the Resend API service being available and accessible.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing Broadcast ID: Ensure the Broadcast ID is correctly provided and matches an existing broadcast.
    • Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
    • Network or API downtime: Check connectivity and Resend API status.
  • Error messages:

    • "Broadcast not found" or similar indicates the provided Broadcast ID does not exist.
    • Authentication failures suggest invalid or expired API credentials.
    • Timeout or network errors require checking internet connection or API availability.

Resolving these usually involves verifying input parameters, refreshing credentials, and ensuring stable network access.

Links and References

Discussion