Braze Send Message icon

Braze Send Message

Send immediate messages using Braze API

Actions7

Send

AI-generated

Overview

The node "Braze Send Message" enables sending immediate messages through the Braze API. It supports multiple message channels including email, SMS, and push notifications. Users can send targeted campaigns or transactional messages, schedule messages for future delivery, and manage scheduled messages (list, update, delete). This node is useful for marketing automation, customer engagement, and transactional communication workflows.

Typical use cases include:

  • Sending promotional emails or SMS to specific user segments.
  • Delivering push notifications to mobile or web app users.
  • Scheduling campaigns to be sent at optimal times.
  • Sending transactional messages triggered by user actions.
  • Managing scheduled campaigns programmatically.

Properties

Name Meaning
Broadcast Whether to send the message to an entire segment (requires segment ID). Use with caution as it targets a broad audience.
Targeting Options Optional targeting parameters; at least one must be provided. Includes: External User IDs (comma-separated list, up to 50), User Aliases (JSON array of alias objects), Segment ID, Audience Filter (JSON defining custom attribute rules).
Campaign ID Optional identifier for the campaign, used for tracking purposes.
Send ID Optional identifier for the send event, used for tracking and analytics.
Recipient Subscription State Filter recipients by subscription state: Subscribed (default), Opted In, or All (regardless of subscription).
Message Channel Type of message to send: Email, SMS, or Push Notification.

Email-specific properties (shown when Message Channel = Email)

Name Meaning
Email Content Type Choose between Custom HTML content or using an existing Braze email template.
App ID Application identifier for sending the email.
Email Template ID ID of the Braze email template to use (required if using template).
Subject Email subject line; overrides template subject if using a template.
From Email sender address/name; overrides template sender if using a template.
Body (HTML) HTML content of the email (required if using custom content).
Additional Email Options Optional settings including Plain Text Body (auto-generated if not provided), Reply-To address, and Preheader text.

SMS-specific properties (shown when Message Channel = SMS)

Name Meaning
App ID Application identifier for sending the SMS.
Message SMS message content (required).
Subscription Group ID Identifier for SMS subscription group compliance (optional).

Push Notification-specific properties (shown when Message Channel = Push)

Name Meaning
Push Type Type of push notification: iOS (Apple Push), Android, or Web Push.
App ID Application identifier for sending the push notification.
Alert Push notification message content (required).
Title Optional title for the push notification.

Output

The node outputs JSON data representing the response from the Braze API for each input item processed. The structure varies depending on the operation but generally includes details about the message send status, any generated identifiers, or scheduling information.

If an error occurs and "Continue On Fail" is enabled, the output JSON will contain error details including:

  • error: Error message string.
  • originalError: Original error message from the HTTP request.
  • httpCode: HTTP status code returned.
  • brazeErrorCode: Specific Braze API error code if available.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Braze API.
  • Needs the Braze instance endpoint URL configured via credentials.
  • Uses HTTP POST requests to Braze API endpoints for sending and managing messages.
  • For JSON fields like user aliases and audience filters, valid JSON syntax is required.

Troubleshooting

  • Invalid JSON Errors: When providing user aliases or audience filter JSON, ensure the JSON is well-formed. Invalid JSON will cause errors with messages like "Invalid user aliases JSON" or "Invalid audience filter JSON".
  • Missing Targeting Options: At least one targeting option (External User IDs, User Aliases, Segment ID, or Audience Filter) must be specified unless broadcasting. Failure to provide these results in an error.
  • API Authentication Errors: Ensure the API key credential is valid and has appropriate permissions.
  • Subscription State Filtering: If no users match the subscription state filter, no messages will be sent.
  • Required Fields Missing: For each message channel, required fields such as App ID, message content, or template IDs must be provided.
  • HTTP Errors: The node surfaces HTTP errors from Braze API with detailed messages. Check the error codes and messages for guidance.

Links and References

Discussion