Actions7
Schedule
AI-generatedOverview
This node allows scheduling messages for future delivery using the Braze API. It supports multiple message channels including email, SMS, and push notifications. Users can specify detailed targeting options to control which recipients receive the scheduled message. The node is useful for marketing automation, customer engagement campaigns, or any scenario where timed communication with specific user segments is required.
Practical examples:
- Scheduling a promotional email campaign to be sent at a specific date and time.
- Sending an SMS reminder to users who opted in, targeting a particular segment.
- Scheduling push notifications to mobile app users based on their subscription state and preferences.
Properties
| Name | Meaning |
|---|---|
| Broadcast | Whether to send the message to the entire segment (requires segment ID). Use with caution as it targets all users in the segment. |
| Targeting Options | Optional parameters to target specific users. At least one must be provided. Includes: External User IDs (comma-separated list), User Aliases (JSON array of alias objects), Segment ID, Audience Filter (JSON rules). |
| Campaign ID | Optional identifier for the campaign, used for tracking purposes. |
| Send ID | Optional identifier for the send instance, used for tracking and analytics. |
| Recipient Subscription State | Filter recipients by their subscription status. Options: Subscribed (default), Opted In, All (regardless of subscription state). |
| Message Channel | Type of message to send. Options: Email, SMS, Push Notification. |
| Email Content Type | For email channel only. Choose between Custom HTML content or using an existing Braze email template. |
| App ID | Application identifier for sending messages. Separate required fields exist for email, SMS, and push channels. |
| Email Template ID | Required if using an email template. Specifies which Braze email template to use. |
| 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 email content. |
| Additional Email Options | Optional email settings such as plain text body, reply-to address, and preheader text. |
| Message (SMS) | SMS message content. Required for SMS channel. |
| Subscription Group ID | Identifier for SMS subscription group compliance. |
| Push Type | Type of push notification. Options: iOS (Apple Push), Android, Web Push. |
| Alert | Push notification message content. Required for push channel. |
| Title | Push notification title. Optional. |
| Schedule Time | ISO 8601 datetime string specifying when the message should be sent. Required for scheduling operation. |
| Send in Local Time | Whether to send the message according to each recipient's local time zone. |
| Send at Optimal Time | Whether to send the message at the optimal time for each user based on their typical engagement patterns. |
Output
The node outputs JSON data representing the response from the Braze API after scheduling the message. This typically includes identifiers for the scheduled message, status information, and any relevant metadata returned by Braze.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Braze API.
- Needs proper configuration of the Braze instance endpoint.
- The node depends on the Braze API service being available and accessible.
- Input properties must be correctly formatted, especially JSON fields like user aliases and audience filters.
Troubleshooting
- At least one targeting option must be provided: If no targeting options are specified (external user IDs, user aliases, segment ID, or audience filter), the node will throw an error. Ensure you provide at least one valid targeting parameter.
- Invalid JSON in user aliases or audience filter: If the JSON strings for user aliases or audience filter are malformed, the node will raise an error indicating invalid JSON. Validate JSON syntax before input.
- Missing required fields: For example, missing App ID for the selected message channel or missing schedule time for scheduling operation will cause errors.
- API authentication errors: Incorrect or missing API key credentials will result in authorization failures.
- HTTP or Braze API errors: The node surfaces HTTP status codes and Braze-specific error codes/messages. Review these to diagnose issues such as rate limits, invalid parameters, or server errors.