Braze Send MessageInstall

Overview

This node integrates with the Braze API to manage and send messages through various channels such as email, SMS, and push notifications. It supports multiple operations including sending immediate messages, scheduling messages for future delivery, listing scheduled messages, updating or deleting scheduled messages, creating send IDs for tracking, and sending transactional messages.

The "List Scheduled Messages" operation specifically allows users to retrieve all scheduled messages and campaigns up to a specified end time. This is useful for monitoring upcoming communications, auditing scheduled campaigns, or managing message workflows.

Practical examples:

• A marketing team wants to review all scheduled email campaigns that will be sent before the end of the month.
• An operations team needs to verify which push notifications are queued for delivery in the next 24 hours.
• A customer support team wants to audit scheduled SMS alerts to ensure no duplicates exist.

Properties

Output

The output is an array of JSON objects, each representing a scheduled message or campaign retrieved from Braze. The structure corresponds directly to the Braze API response for scheduled broadcasts.

• The json field contains details about each scheduled message, such as schedule ID, message content, timing, and targeting information.
• There is no binary data output for this operation.

Example snippet of output JSON (simplified):

{
  "schedule_id": "abc123",
  "messages": {
    "email": {
      "subject": "Upcoming Sale",
      "from": "marketing@example.com"
    }
  },
  "schedule": {
    "time": "2024-07-01T10:00:00Z"
  },
  "targeting": {
    "segment_id": "segment_456"
  }
}

Dependencies

• Requires an API key credential for authenticating with the Braze API.
• Needs the Braze instance URL configured to form correct API endpoints.
• The node uses HTTP requests to communicate with Braze's REST API.

Troubleshooting

• Common issues:

  • Invalid or missing API key will cause authentication failures.
  • Incorrectly formatted endTime parameter may result in API errors or empty results.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • Errors returned by Braze API are captured and presented with their message and code.
  • If targeting options are required but missing in other operations, the node throws descriptive errors; however, for listing scheduled messages, only the endTime is mandatory.
  • To handle errors gracefully, enable "Continue On Fail" to receive error details per item without stopping execution.

• Resolution tips:

  • Verify the API key and Braze instance configuration.
  • Ensure the endTime is a valid ISO 8601 datetime string.
  • Check network access and firewall settings if requests fail.

Links and References

• Braze API Documentation - Scheduled Broadcasts
• ISO 8601 Date and Time Format