Claude Braze connectorWhat Claude can do in your Braze account.

Returns a daily series of a campaign's results over time: messages sent, opens, clicks and conversions, broken down by channel. Claude can chart the curve in words or compare two campaigns over the same days.

Retrieves the useful information about one campaign from its identifier. Claude reaches it once it knows which campaign you mean. It is the step between a name in a list and the facts behind that campaign.

Exports the list of campaigns with their name, identifier, whether they are API campaigns, and their tags. Claude uses it to find the campaigns you mean before pulling any numbers on them.

Exports the time series data of a Canvas so Claude can follow how it performed day by day. Claude can then point to the day a journey started to lose people.

Returns rollups of a Canvas's time series for a short results summary, rather than every data point. It suits a quick verdict better than the full series does.

Exports a Canvas's metadata: its name, when it was created, its current status and more. Claude uses it to check what a journey is before judging how it performs.

Pulls every Canvas into one list with their name, identifier and tags. It is how Claude locates a journey you only remember by part of its name or by a tag.

Returns a single catalog item and its content, from the catalog you name. Braze's reference reaches it through the catalog name and the item ID, and Claude can then describe that item's stored content to you.

Returns several items of a catalog along with their content. It gives Claude a sample of the catalog to describe or compare, item by item.

Lists the catalogs that exist in a workspace, the starting point for both catalog item tools. Claude needs a catalog name before it can open any of its items.

Gets the details of an existing content block, and can add which campaigns or Canvases include it. That inclusion data shows how far one revision would reach.

Lists the existing content blocks in your account with their information. Claude starts here when you describe a block by what it contains rather than by its name.

Exports the custom attributes recorded for your app, in alphabetical groups of 50. Claude pages through them to tell you which fields your team actually records.

Tracks daily active users: one count of unique active people per date. Claude can set the curve against a date you name, such as a launch or an outage.

Gets the information held for one specific email template. Claude reads it before proposing a new version or reusing the template. It covers one template, where the listing tool shows them all.

Lists the email templates available in your Braze account. It gives Claude the names to work with when you ask about a template in your own words.

Pages through the custom events recorded for your app, in alphabetical groups of 50 with cursor paging. Claude can then tell which events exist before counting any of them.

Returns how often a custom event occurred over a time period you set. Claude turns the counts into a day-by-day reading of the period you set.

Exports custom event names in alphabetical groups of 250, page by page. It is the lighter option when Claude only needs to check a name exists. Paging is by page number here.

Returns past sync statuses for a given Cloud Data Ingestion integration, ten per call. Claude can tell you when the last good sync ran and which ones did not finish.

Gives monthly active users as a daily figure, each one counted over a rolling 30-day window. Claude can read the trend of that rolling figure across the period you ask about.

Counts new users day by day, one total per date. Claude can line these counts up with your campaign calendar. Each point is one calendar day.

Returns a paginated list of product IDs from your purchase data. Claude uses those identifiers to ask the right questions about purchases. The list comes back in pages, which Claude walks through for you.

Returns the total number of purchases in your app over a time range. Claude can compare it with an earlier range of the same length. It counts purchases, not the money they brought in.

Adds up the money spent in your app over a time range. Claude can put the figure next to purchase counts to show the average basket. It measures money, where the quantity tool counts orders.

Follows a segment's estimated size over time, one value per day. Claude reads the trend rather than a single snapshot. Braze gives an estimate, so read it as a direction rather than an exact headcount.

Retrieves the relevant information on one segment from its identifier. Claude uses it to explain a segment before you target it, without any user profile data.

Exports segments with their name, identifier and whether analytics tracking is on. It is where Claude finds the segment you describe in plain words. The tracking flag tells Claude which segments carry analytics at all.

Gives daily stats for one tracked delivery of an API campaign, found by its ID. Claude can compare those days with the previous run of the same message.

Returns the number of sessions in your app over a time period you choose. Claude can set sessions against active users to see whether engagement per person moved.

Measures app uninstalls, one total per date. Claude can line up the spikes with your campaign dates, although Braze counts per day, not per campaign, so tying a spike to one campaign remains your own reading.

Lists the Braze workspaces your connection can reach. Braze describes it as a way to discover which workspaces your access token can reach, which tells Claude where it is allowed to work.