Resend icon

Resend

Interact with Resend API for emails, domains, API keys, broadcasts, audiences, and contacts

Actions25

Overview

This node integrates with the Resend API to manage email-related resources such as emails, domains, API keys, broadcasts, audiences, and contacts. Specifically for the Domain - Get operation, it retrieves detailed information about a specific email domain by its unique ID.

Common scenarios where this node is beneficial include:

  • Fetching domain verification status or configuration details.
  • Checking domain settings before sending emails.
  • Automating domain management workflows in email marketing or transactional email systems.

For example, you might use this node to get the current status of a domain to ensure it is verified and ready to send emails, or to retrieve domain metadata for reporting purposes.

Properties

Name Meaning
Domain ID The unique identifier of the domain you want to retrieve information about.

Output

The output is a JSON object containing the domain's details as returned by the Resend API. This typically includes fields such as domain name, verification status, region, tracking settings, TLS configuration, and other metadata related to the domain.

Example output structure (simplified):

{
  "id": "4dd369bc-aa82-4ff3-97de-514ae3000ee0",
  "name": "example.com",
  "region": "us-east-1",
  "verified": true,
  "click_tracking": false,
  "open_tracking": false,
  "tls": "opportunistic",
  "custom_return_path": "send"
}

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Resend API.
  • The node makes HTTP requests to https://api.resend.com/domains/{domainId} endpoint.
  • Ensure the API key has sufficient permissions to read domain information.

Troubleshooting

  • Invalid Domain ID: If the provided Domain ID does not exist or is malformed, the API will return an error. Verify the Domain ID is correct.
  • Authentication Errors: If the API key is missing, invalid, or lacks permissions, authentication errors will occur. Check that the API key credential is properly configured.
  • Network Issues: Connectivity problems can cause request failures. Ensure your n8n instance can reach the Resend API endpoint.
  • API Rate Limits: Excessive requests may be throttled by the Resend API. Implement retry logic or reduce request frequency if needed.

Common error messages:

  • "Unauthorized": Invalid or missing API key.
  • "Not Found": Domain ID does not exist.
  • "Bad Request": Malformed input parameters.

Resolving these usually involves verifying credentials, checking input values, and ensuring network connectivity.

Links and References

Discussion