Actions25
Overview
This node integrates with the Resend API to manage emails, including sending, retrieving, updating, and canceling scheduled emails. Specifically, the Email - Update operation allows users to modify an existing email's scheduled send time.
Common scenarios for this node include:
- Adjusting the scheduled send time of a previously created email campaign.
- Postponing or rescheduling emails without needing to recreate them.
- Managing email workflows where timing adjustments are necessary after initial scheduling.
For example, if you have scheduled an email to be sent but need to delay it due to last-minute content changes, you can use this node to update the "Scheduled At" timestamp to a new ISO 8601 date-time string.
Properties
| Name | Meaning |
|---|---|
| Email ID | The unique identifier of the email to update. Required to specify which email is being modified. |
| Scheduled At | The new scheduled date and time to send the email. Must be in ISO 8601 format (e.g., 2024-08-05T11:52:01.858Z). Optional; if omitted, no change to schedule occurs. |
Output
The node outputs a JSON object representing the updated email resource as returned by the Resend API. This typically includes fields such as the email ID, status, scheduled time, and other metadata related to the email.
No binary data output is produced by this operation.
Example output snippet (simplified):
{
"id": "ae2014de-c168-4c61-8267-70d2662a1ce1",
"status": "scheduled",
"scheduled_at": "2024-08-05T11:52:01.858Z",
...
}
Dependencies
- Requires an active API key credential for the Resend API.
- The node makes HTTP requests to
https://api.resend.com/emails/{emailId}using the PATCH method to update the email. - Ensure the API key has permissions to update emails.
- No additional environment variables are required beyond the API key credential.
Troubleshooting
- Invalid Email ID: If the provided Email ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
- Invalid Scheduled At Format: The "Scheduled At" property must be a valid ISO 8601 date-time string. Incorrect formats will cause the API to reject the request.
- Permission Denied: If the API key lacks permission to update emails, the request will fail. Confirm the API key has appropriate access rights.
- Network Issues: Connectivity problems may cause HTTP request failures. Check network connectivity and API endpoint availability.
- Empty Scheduled At: If the "Scheduled At" field is left empty, the node sends an empty update body, which may result in no changes or an error depending on API behavior.
To resolve errors, verify input values, ensure proper API credentials, and consult the Resend API documentation for detailed error messages.
Links and References
- Resend API Documentation – Official API reference for managing emails and other resources.
- ISO 8601 Date Format – Explanation of the date-time format required for scheduling.