Braze Send MessageInstall

Overview

This node integrates with the Braze API to manage messaging campaigns and user communications. Specifically, the Update Scheduled Message operation allows users to modify a previously scheduled message before it is sent. This includes changing the scheduled time and optionally updating the message content for different channels.

Common scenarios where this node is beneficial include:

• Adjusting the timing of marketing or transactional messages based on new information or campaign changes.
• Correcting or updating message content after scheduling but before delivery.
• Managing scheduled communications dynamically without needing to delete and recreate schedules.

For example, a marketing team might schedule an email blast but later decide to push the send time by a few hours and update the email body with new promotional details. Using this node, they can update the existing scheduled message seamlessly.

Properties

Output

The node outputs a JSON object representing the response from the Braze API after attempting to update the scheduled message. This typically includes confirmation details about the updated schedule or any errors encountered.

If the update is successful, the output JSON will contain data confirming the new schedule and message content state.

If the update fails, the output JSON will include error details such as error messages, HTTP status codes, and Braze-specific error codes.

The node does not output binary data.

Dependencies

• Requires an active connection to the Braze API using an API key credential.
• Needs proper configuration of the Braze instance endpoint.
• The node uses HTTP POST requests to interact with Braze's /messages/schedule/update endpoint.

Troubleshooting

• Common Issues:

  • Invalid or missing Schedule ID: The node requires a valid schedule identifier to update the correct message.
  • Incorrectly formatted New Schedule Time: Must be in ISO 8601 format; otherwise, the API may reject the request.
  • Malformed JSON in Messages property when updating message content can cause parsing errors.
  • Attempting to update a non-existent or already sent schedule will result in errors.

• Error Messages:

  • Errors returned from Braze API are captured and presented with their message, HTTP code, and Braze error code.
  • If targeting options or required fields are missing, the node throws descriptive errors.
  • When continuing on failure is enabled, errors are included in the output JSON instead of stopping execution.

• Resolution Tips:

  • Verify that the Schedule ID corresponds to an existing scheduled message.
  • Ensure date-time values conform to ISO 8601 standards.
  • Validate JSON syntax for the Messages input before running the node.
  • Check API credentials and network connectivity if authentication or request failures occur.

Links and References

• Braze API Documentation - Schedule Update Endpoint
• ISO 8601 Date and Time Format