Start free
ActionBrazeUpdated June 2026

How do I update Braze user attributes?

Short answer: You can update user attributes in Braze by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Braze Update User Attributes action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 4 Braze actions
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
External User ID
external_id
stringRequired–
Email
email
stringOptionalThe email address. Used as the recipient or identifier depending on context.
Phone
phone
stringOptionalPhone number in E.164 format (with country code, no spaces).
First Name
first_name
stringOptionalContact's first (given) name.
Last Name
last_name
stringOptionalContact's last (family) name.
Custom Attributes (JSON)
custom_attributes
stringOptional{"plan":"premium","mrr":99}
Sample request
{
  "external_id": "{{trigger.external_id}}",
  "email": "e.g. user@example.com",
  "phone": "e.g. +14155551234",
  "first_name": "e.g. Jane",
  "last_name": "e.g. Doe"
}
Returns
{
  "message": "success",
  "attributes_processed": 1
}

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

Triggered by

Apps that pair well as the trigger for Update User Attributes.

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

Gmail → Braze
1 Gmail triggers
Slack → Braze
13 Slack triggers
Google Sheets → Braze
2 Google Sheets triggers
HubSpot → Braze
18 HubSpot triggers
FAQ

Questions about Update User Attributes.

What does the Update User Attributes action do in Braze?
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.
What inputs does Update User Attributes require?
Required: External User ID. 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 Update User Attributes support batch operations?
Yes. Run Update User Attributes inside a Loop node to process arrays. TinyCommand handles Braze's rate limits automatically so you don't have to throttle manually.
More actions

Other Braze actions.

Action
Send Messages
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.
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
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.