ActionBrazeUpdated September 2026

How do I send a Braze message directly?

Short answer: You can send messages in Braze by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Braze Send Messages action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Send Messages in Braze — start free All 4 Braze actions

Send Messages in Braze — start free

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.

Triggered by

Apps that pair well as the trigger for Send Messages.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Braze

2 Google Sheets triggers

HubSpot → Braze

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Braze returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Send Messages support batch operations?

Run Send Messages inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Braze's rate limits.

More actions

Other Braze actions.

Action

Track Custom Event

Pushes a custom behavioural event for a user with optional properties. Braze Canvas journeys can trigger on these events for engagement automation. The hook for "server-side action happened → fire Braze event to start the matching journey" workflows.

Action

Update User Attributes

Upserts user-level attributes (plan tier, country, signup_date, lifetime_value). Drives Braze segmentation. The standard "external state changed → reflect in Braze" sync action for keeping audience filters accurate.

Action

Trigger API Campaign

Fires an API-triggered campaign (designed and reviewed in Braze UI) at a specified user set with optional trigger_properties merged into the templates. The recommended pattern for production messaging — keeps content review in Braze, just invokes from the workflow.

Send Messages in Braze — start free