Actions25
Overview
This node integrates with the Resend API to manage API keys, specifically allowing you to create new API keys with defined permissions. It is useful in scenarios where you want to programmatically generate API keys for different access levels to your email sending service, such as full administrative access or restricted sending access tied to a specific domain.
Practical examples include:
- Automatically creating API keys when onboarding new team members or services.
- Generating limited-scope API keys that can only send emails from a particular domain, enhancing security.
- Managing API key lifecycle within automated workflows without manual intervention.
Properties
| Name | Meaning |
|---|---|
| API Key Name | The name assigned to the new API key. This is a required field and is used to identify the key. |
| Permission | The level of access granted by the API key. Options are: "Full Access" (complete control) or "Sending Access" (restricted to sending emails). |
| Domain ID | When permission is set to "Sending Access", this optional field restricts the API key to send emails only from the specified domain ID. |
Output
The node outputs a JSON object representing the created API key as returned by the Resend API. This typically includes details such as the API key's unique identifier, name, permission level, associated domain (if any), creation timestamp, and other metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authorize requests to the Resend API.
- The node makes HTTP POST requests to the Resend API endpoint for API key creation.
- Network connectivity to
https://api.resend.comis necessary.
Troubleshooting
Common issues:
- Missing or invalid API authentication token will cause authorization failures.
- Providing a domain ID when permission is not set to "Sending Access" may be ignored or cause errors.
- Invalid or malformed input values (e.g., empty API key name) will result in API validation errors.
Error messages:
- Authorization errors typically indicate problems with the API token; ensure the credential is correctly set up.
- Validation errors from the API will specify which input fields are incorrect or missing.
- Network errors suggest connectivity issues; verify internet access and API endpoint availability.
To resolve errors, verify all required properties are correctly filled, check API credentials, and ensure the domain ID is valid if used.
Links and References
- Resend API Documentation – Official API reference for creating API keys.
- n8n HTTP Request Node Documentation – For understanding how HTTP requests are made within n8n nodes.