Actions7
Delete Scheduled Message
AI-generatedOverview
This node integrates with the Braze API to manage messaging campaigns and user communications. It supports various operations such as sending immediate messages, scheduling messages for future delivery, updating or deleting scheduled messages, creating send identifiers, listing scheduled messages, and sending transactional messages.
The Delete Scheduled Message operation specifically allows users to delete a previously scheduled message before it is sent. This is useful in scenarios where a planned campaign or broadcast needs to be canceled or modified by removing the scheduled message from Braze's queue.
Practical examples:
- Canceling a promotional email scheduled to go out tomorrow due to a last-minute change.
- Removing a push notification scheduled for a specific time because the content is no longer relevant.
- Deleting an SMS campaign that was scheduled but now conflicts with other marketing activities.
Properties
| Name | Meaning |
|---|---|
| Schedule ID | The unique identifier of the scheduled message you want to delete. |
Output
The node outputs a JSON object representing the response from the Braze API after attempting to delete the scheduled message. This typically includes confirmation of deletion or error details if the operation failed.
Example output structure (simplified):
{
"json": {
// API response confirming deletion or error information
},
"pairedItem": {
"item": <index_of_input_item>
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an active Braze API connection configured with a valid API key credential.
- The node uses Braze's REST API endpoints, so internet access and proper authentication are necessary.
- No additional environment variables beyond the API credentials are required.
Troubleshooting
Common issues:
- Invalid or missing Schedule ID: The operation requires a valid schedule identifier; ensure the correct ID is provided.
- Authentication errors: Verify that the Braze API key credential is correctly set up and has sufficient permissions.
- Network or endpoint errors: Check network connectivity and Braze service status.
Error messages:
- Errors returned by Braze API are captured and presented in the output JSON under
errorfields. - If targeting options or parameters are invalid, the node throws descriptive errors indicating the problem.
- To handle errors gracefully, enable the node’s "Continue On Fail" option to process subsequent items even if one fails.
- Errors returned by Braze API are captured and presented in the output JSON under