Braze connector for AI agents

Tools your lifecycle marketing agent reaches for on Braze, scoped per user.

CALL ANY TOOL

73 tools for customer engagement in Braze: read campaign, Canvas, segment, and KPI analytics, trigger and schedule campaigns and Canvases, send messages, manage catalogs, templates, and Content Blocks, and update user profiles and subscriptions.

braze_campaign_analytics_get

Get campaign analytics

Get daily performance stats for a campaign over a date range. Returns a data array with one entry per day, holding per-channel stats such as sends, opens, clicks, conversions, and revenue. Use braze_campaign_analytics_get for a campaign's totals; use braze_send_analytics_get for one tracked send; use braze_canvas_analytics_get for Canvases.

Parameters

Name

Type

Required

Description

campaign_id

string

Required

The campaign API identifier, found on the campaign's details page in the Braze dashboard, under Settings > APIs and Identifiers, or from braze_campaigns_list. Example: 4cf9b8b8-3b1c-4a0a-9b9e-2a8b2c1d3e4f.

length

integer

Required

How many days before ending_at to include in the series, between 1 and 100. Example: 14.

ending_at

string

Optional

ISO 8601 datetime the series ends on; defaults to the time of the request. Example: 2026-10-01T23:59:59Z.

braze_campaign_duplicate

Duplicate campaign

braze_campaign_trigger_schedule_create

Create campaign trigger schedule

Schedule an API-triggered campaign, whose content lives in the dashboard, to send at a set time. Returns the dispatch_id and a schedule_id for later updates. Use braze_campaign_trigger_schedule_create to send later; use braze_campaign_trigger_send to send now.

Parameters

Name

Type

Required

Description

campaign_id

string

Required

schedule_time

string

Required

When to send, as an ISO 8601 datetime. Interpreted in UTC unless in_local_time is true, in which case it is the send time in each user's local time zone. Example: 2026-11-01T15:00:00Z.

at_optimal_time

boolean

Optional

If true, use Intelligent Delivery to send on the day of schedule_time at each user's optimal time. Example: false.

audience

object

Optional

Connected Audience filter object; the message goes only to users matching these filters. Combine filters with AND/OR arrays; each filter targets a custom attribute, a subscription status, or last-used-app time. Example: {"AND": [{"custom_attribute": {"custom_attribute_name": "eye_color", "comparison": "equals", "value": "blue"}}, {"email_subscription_status": {"comparison": "is", "value": "opted_in"}}]}.

broadcast

boolean

Optional

Set to true only when sending to the entire segment that the campaign targets in the dashboard, without listing recipients. When true, you cannot include recipients. Defaults to false; use with care because it can message a much larger audience than intended. Example: false.

in_local_time

boolean

Optional

If true, send at schedule_time in each user's local time zone instead of UTC. Example: false.

recipients

array

Optional

Up to 50 recipient objects. Each recipient names exactly one of external_user_id, user_alias, or email (email also needs a prioritization array such as ["identified", "most_recently_updated"]). A recipient can carry its own trigger_properties (overriding the request-level values), an attributes object that creates or updates profile attributes before sending, and send_to_existing_only (defaults to true; set false together with attributes to create the user). Omit recipients only when broadcast is true or audience is set. Example: [{"external_user_id": "user_123", "trigger_properties": {"order_id": "A100"}}].

send_id

string

Optional

Optional send identifier used to track analytics for this specific send separately. Create one with braze_send_id_create (or let Braze create it on first use). Example: spring_sale_2026_wave1.

trigger_properties

object

Optional

Personalization key-value pairs applied to every recipient in this request; reference them in the message with {{api_trigger_properties.${key}}}. Example: {"order_id": "A100", "discount": 15}.

braze_campaign_trigger_schedule_update

Update campaign trigger schedule

braze_campaign_trigger_send

Send campaign trigger

Send an API-triggered campaign, whose content lives in the Braze dashboard, to recipients right now. Returns a dispatch_id for the whole batch. Use braze_campaign_trigger_send to send immediately; use braze_campaign_trigger_schedule_create to send later; use braze_canvas_trigger_send for Canvases. The campaign must use API-triggered delivery.

Parameters

Name

Type

Required

Description

campaign_id

string

Required

attachments

array

Optional

Email file attachments, each with a file_name (without extension), a url the file is fetched from (up to 2 MB), and optionally basic_auth_credential naming a stored credential. Not allowed when broadcast is true. Example: [{"file_name": "invoice", "url": "https://example.com/invoice.pdf"}].

audience

object

Optional

broadcast

boolean

Optional

recipients

array

Optional

send_id

string

Optional

Optional send identifier used to track analytics for this specific send separately. Create one with braze_send_id_create (or let Braze create it on first use). Example: spring_sale_2026_wave1.

trigger_properties

object

Optional

Personalization key-value pairs applied to every recipient in this request; reference them in the message with {{api_trigger_properties.${key}}}. Example: {"order_id": "A100", "discount": 15}.

braze_campaigns_list

List campaigns

braze_canvas_analytics_get

Get canvas analytics

braze_catalog_create

Create catalog

braze_catalog_item_get

Get catalog item

braze_catalog_item_update

Update catalog item

braze_catalog_items_list

List catalog items

braze_catalog_selection_create

Create catalog selection

braze_content_blocks_list

List content blocks

braze_custom_event_analytics_get

Get custom event analytics

braze_custom_events_list

List custom events

braze_email_subscription_status_update

Update email subscription status

braze_email_template_create

Create email template

braze_email_unsubscribes_list

List email unsubscribes

braze_kpi_dau_get

Get kpi dau

braze_kpi_new_users_get

Get kpi new users

braze_messages_schedule_update

Update messages schedule

braze_messages_send

Send messages

Send a message immediately to specific users, a segment, or a Connected Audience, with the message content defined in the request. Returns a dispatch_id identifying this send. Use braze_messages_send for API-only content; use braze_campaign_trigger_send or braze_canvas_trigger_send to send content built in the dashboard. Recipients named by external ID or alias must already exist in Braze.

Parameters

Name

Type

Required

Description

messages

object

Required

Messaging objects keyed by channel: apple_push, android_push, kindle_push, web_push, email, sms, webhook, content_card or whats_app. Each value follows Braze's messaging object for that channel; for email you typically pass app_id, from, subject and body. Example: {"email": {"app_id": "your_app_id", "from": "Acme <hello@acme.com>", "subject": "Welcome", "body": "Hi {{${first_name}}} "}}.

audience

object

Optional

broadcast

boolean

Optional

Set to true only when sending to the entire segment that the campaign or Canvas targets in the dashboard, without listing recipients. When true, you cannot include recipients. Defaults to false; use with care because it can message a much larger audience than intended. Example: false.

campaign_id

string

Optional

The campaign API identifier, found on the campaign's details page in the Braze dashboard, under Settings > APIs and Identifiers, or from braze_campaigns_list. Needed to track sends, opens, and clicks against an API campaign. Example: 4cf9b8b8-3b1c-4a0a-9b9e-2a8b2c1d3e4f.

external_user_ids

array

Optional

List of up to 50 external user IDs to send to. The users must already exist in Braze. Example: ["user_123", "user_456"].

override_frequency_capping

boolean

Optional

Ignore frequency capping rules for this send; defaults to false. Example: false.

recipient_subscription_state

string

Optional

Which users can receive the message by subscription state: opted_in (only explicitly opted-in users), subscribed (subscribed or opted in; the Braze default), or all (includes unsubscribed users, for transactional email only). Example: subscribed. One of: `opted_in`, `subscribed`, `all`.

segment_id

string

Optional

Segment to send to; combined with user lists it limits the send to those users who are in the segment, from braze_segments_list or Settings > APIs and Identifiers in the dashboard. Example: 2f6c8a1e-9d3b-4c7a-b5e2-0f1a2b3c4d5e.

send_id

string

Optional

Optional send identifier used to track analytics for this specific send separately. Create one with braze_send_id_create (or let Braze create it on first use). Example: spring_sale_2026_wave1.

user_aliases

array

Optional

List of user alias objects, each with an alias name and an alias label. Example: [{"alias_name": "device123", "alias_label": "device_id"}].

braze_preference_center_create

Create preference center

braze_preference_center_url_get

Get preference center url

braze_purchase_products_list

List purchase products

braze_purchase_revenue_get

Get purchase revenue

braze_segments_list

List segments

braze_send_analytics_get

Get send analytics

braze_subscription_group_status_set

Set subscription group status

braze_users_export_by_ids

Users export by ids

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Braze tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["braze"], toolNames: [
    "braze_campaigns_list",
    "braze_campaign_analytics_get",
    "braze_campaign_trigger_send"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Show yesterday's stats for the spring promo campaign" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["braze"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Show yesterday's stats for the spring promo campaign" }],
  tools,
});

// Execute the tool call with the user's vaulted Braze access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["braze"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Show yesterday's stats for the spring promo campaign" }],
  tools,
});

// Tool call runs with the user's vaulted Braze access token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["braze"] }, pageSize: 100,
});

const agent = new Agent({
  name: "lifecycle_marketing_agent",
  model: "gemini-2.5-pro",
  instruction: "Braze tools scoped to this user",
  tools,
});

await agent.run("Show yesterday's stats for the spring promo campaign");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Braze tool. Click to copy, paste into your agent, done.

Analytics

Copy the prompt

Copied

Show daily stats for the spring promo campaign over the last 7 days.

Copy the prompt

Copied

What was our daily active user count for the past 2 weeks?

Copy the prompt

Copied

Get the estimated size of the lapsed users segment this month.

Messaging

Copy the prompt

Copied

Send the API-triggered welcome campaign to user 81723.

Copy the prompt

Copied

Schedule these users to enter the onboarding Canvas on Monday at 9am.

Copy the prompt

Copied

List campaigns and Canvases scheduled to send this week.

Users and content

Copy the prompt

Copied

Log a plan_upgraded event and a purchase on user 81723's profile.

Copy the prompt

Copied

Unsubscribe this email address from the marketing subscription group.

Copy the prompt

Copied

Create a Content Block with our new footer HTML.

SEE HOW AUTH WORKS

Each user connects their own Braze access token once, and Scalekit sends it with every call. Credentials stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Braze

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Braze

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Braze

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Braze

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other marketing and messaging connectors.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Braze access token looks fine in a demo. In production every campaign send looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Braze today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Braze as the user or through a shared token?

As the user. Each user connects their own Braze access token once, and Scalekit sends it with every call. Sends, schedule changes, and profile updates are attributed to that user in your audit trail, not a shared service account.

Where is the Braze access token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Braze?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the analytics and list tools without braze_messages_send or braze_campaign_trigger_send, which send messages to real users. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Braze access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent send a Braze campaign without writing the message content?

Yes. braze_campaign_trigger_send sends an API-triggered campaign whose content lives in the Braze dashboard, and braze_canvas_trigger_send enters recipients into an API-triggered Canvas. braze_messages_send sends a message with content defined in the request instead.