Nexra
All connectors
Implemented
Marketing & advertising
Braze logo

Braze

Track Braze user attributes, events and purchases; read users, segments, campaigns, Canvases and catalogs; manage catalog items and subscription groups; trigger API campaigns to named users.

Keep Braze profiles, consent and catalogs in step with CRMs and commerce systems, and trigger personalised journeys from operational events.

Build a flow with BrazeProvider API documentation

Source actions

16

Destination actions

9

Data types

17

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

campaign analytics
  • Get campaign analytics
    Source

    Daily series of sends, opens, clicks, conversions and revenue by channel.

    campaign_analytics.list
campaign messages
  • Trigger API campaign for users
    Destination
    Not retried automatically
    Approval before production

    Sends an API-triggered campaign to an explicit list of up to 50 existing users (never a segment broadcast).

    campaign_messages.send
campaigns
  • Get campaign
    Source

    Campaign settings, channels, message variations and conversion behaviours.

    campaigns.get
  • List campaigns
    Source
    Incremental

    Campaigns with API-campaign flag, tags and last edit time.

    campaigns.list
canvas messages
  • Trigger API Canvas for users
    Destination
    Not retried automatically
    Approval before production

    Enters an explicit list of up to 50 existing users into an API-triggered Canvas (never a segment broadcast).

    canvas_messages.send
canvases
  • Get Canvas
    Source

    Canvas settings, variants and steps.

    canvases.get
  • List Canvases
    Source
    Incremental

    Canvases with tags and last edit time.

    canvases.list
catalog items
  • Create catalog item
    Destination
    Provider duplicate protection
    Approval before production

    Creates one catalog item with the given ID; fails if the ID exists.

    catalog_items.create
  • Get catalog item
    Source

    A catalog item and its field values.

    catalog_items.get
  • List catalog items
    Source

    Items in a catalog (50 per page).

    catalog_items.list
  • Update catalog item
    Destination
    Provider duplicate protection
    Approval before production

    Edits fields on an existing catalog item; array fields accept $add and $remove operators.

    catalog_items.update
catalogs
  • List catalogs
    Source

    Catalogs with field definitions and item counts.

    catalogs.list
custom attributes
  • List custom attributes
    Source

    Custom attribute definitions with data type, status and tags.

    custom_attributes.list
custom events
  • List custom events
    Source

    Custom event names recorded in the workspace.

    custom_events.list
email unsubscribes
  • List email unsubscribes
    Source
    Incremental

    Email addresses that unsubscribed in a date range, or one address's status.

    email_unsubscribes.list
messages
  • Send message to users
    Destination
    Not retried automatically
    Approval before production

    Sends API-defined message content to an explicit list of up to 50 existing users (no segment or audience targeting).

    messages.send
purchases
  • Track purchase
    Destination
    Not retried automatically
    Approval before production

    Records a purchase for a user through /users/track.

    purchases.create
segments
  • Get segment
    Source

    Segment details with description and filter summary.

    segments.get
  • List segments
    Source

    Segments with analytics tracking flag and tags.

    segments.list
subscription status
  • Get subscription group status
    Source

    A user's state in one subscription group (independent of the global subscription state).

    subscription_status.get
  • Set subscription group status
    Destination
    Provider duplicate protection
    Approval before production

    Explicitly subscribes or unsubscribes up to 50 users in one subscription group (consent change).

    subscription_status.update
user events
  • Track custom event
    Destination
    Not retried automatically
    Approval before production

    Records a custom event for a user through /users/track.

    user_events.create
user subscription groups
  • List a user's subscription groups
    Source

    Subscription groups with status in the user's history.

    user_subscription_groups.list
users
  • Export users by ID
    Source

    Profiles for up to 50 external IDs, or one email address, with attributes, events and purchases.

    users.list
  • Create or update user
    Destination
    Provider duplicate protection
    Approval before production

    Sets standard and custom attributes on a user identified by external ID through /users/track.

    users.upsert

Authentication

REST API key (bearer)

Plans and access

All Braze plans include the REST API; some endpoints depend on packaged features (catalogs, Canvas). REST API keys carry per-endpoint permissions and can be restricted by IP allowlist; keys are workspace-scoped.

Test environment

Use a development workspace in your Braze dashboard.

Rate limits

Per-endpoint limits: /users/track 3,000 requests per 3 seconds; /users/export/ids 250 per minute (40 per second with fields_to_export); export lists 1,000 per hour. HTTP 429 with X-RateLimit headers.

Pagination

Segment, campaign, Canvas and custom event lists use a zero-based page parameter; catalog items and custom attributes use Link-header cursors; unsubscribes use limit/offset.

Provider events

Braze Currents streams engagement events to supported destinations. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Broadcasts to whole segments or connected audiences are never sent; message operations require an explicit list of up to 50 external user IDs.
  • Subscription states change only through the explicit subscription status operation or the explicit emailSubscribe/pushSubscribe inputs on user upserts.
  • Event and purchase tracking have no idempotency key; uncertain writes are not repeated automatically.
  • Deleting users, catalog items and catalogs is not implemented; asynchronous bulk catalog endpoints are not used.
  • User export by segment (asynchronous file export) is not implemented; export by IDs is limited to 50 users per request.

Developer reference

  1. Create the Braze credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Braze, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Braze docsAPI referenceBraze docsAuthenticationBraze docsRate limitsBraze docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/braze and the Connections API.