How to send messages in Braze

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
External User IDs external_user_ids	array	Required	–
Campaign ID (optional, for analytics) campaign_id	string	Optional	–
Messages object (JSON) messages_json	string	Required	See Braze /messages/send docs for full message schema

Sample request

{
  "external_user_ids": "{{trigger.external_user_ids}}",
  "campaign_id": "{{trigger.campaign_id}}",
  "messages_json": "{\"apple_push\":{\"alert\":\"Hi!\"}}"
}

Returns

{
  "message": "success",
  "dispatch_id": "abc-123"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Send Messages.

What does the Send Messages action do in Braze?

Sends a message immediately to a specific user list (bypasses Canvas/Campaigns). Compose the message in the API call — channel, content, sender. For one-off transactional sends; for templated production messaging, prefer Trigger API Campaign with a pre-built campaign.

What inputs does Send Messages require?

Required: External User IDs, Messages object (JSON). Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Braze returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Send Messages support batch operations?

Yes. Run Send Messages inside a Loop node to process arrays. TinyCommand handles Braze's rate limits automatically so you don't have to throttle manually.

More actions