Braze MCP integration for AI agents.
Connect AI agents to Braze through 4 structured actions, including get campaign details, get canvas details, and list campaigns. Review authentication, input…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Braze integration exposes
The Braze Agent App exposes 4 provider-backed actions for marketing and data work. Its current contract lets an authorized agent fetch braze metadata and message details for one campaign, fetch braze metadata, variants, steps, and message details for one canvas, and list braze campaigns with optional archived, sort, page, and last-edited filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Braze account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Braze capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_campaign_detailsREADFetch Braze metadata and message details for one campaign.
INPUTS: campaignId / postLaunchDraftVersion / includeHasTranslatableContent
get_canvas_detailsREADFetch Braze metadata, variants, steps, and message details for one Canvas.
INPUTS: canvasId / postLaunchDraftVersion / includeHasTranslatableContent
list_campaignsREADList Braze campaigns with optional archived, sort, page, and last-edited filters.
INPUTS: page / includeArchived / sortDirection / lastEditedAfter
list_canvasesREADList Braze Canvases with optional archived, sort, page, and last-edited filters.
INPUTS: page / includeArchived / sortDirection / lastEditedAfter
INPUT CONTRACTS
Know what the action needs before it runs.
get_campaign_details
campaignIdREQUIRED- The Braze campaign API identifier.
postLaunchDraftVersionOPTIONAL- Whether Braze should return the post-launch draft version when one exists.
includeHasTranslatableContentOPTIONAL- Whether Braze should include has_translatable_content fields for messages.
get_canvas_details
canvasIdREQUIRED- The Braze Canvas API identifier.
postLaunchDraftVersionOPTIONAL- Whether Braze should return the post-launch draft version when one exists.
includeHasTranslatableContentOPTIONAL- Whether Braze should include has_translatable_content fields for messages.
list_campaigns
pageOPTIONAL- The zero-based Braze page number to return.
includeArchivedOPTIONAL- Whether archived campaigns or Canvases should be included.
sortDirectionOPTIONAL- The creation-time sort direction to send to Braze.
lastEditedAfterOPTIONAL- Only return items edited after this time, mapped to Braze last_edit.time[gt]. Use Braze's yyyy-MM-DDTHH:mm:ss-compatible timestamp format.
list_canvases
pageOPTIONAL- The zero-based Braze page number to return.
includeArchivedOPTIONAL- Whether archived campaigns or Canvases should be included.
sortDirectionOPTIONAL- The creation-time sort direction to send to Braze.
lastEditedAfterOPTIONAL- Only return items edited after this time, mapped to Braze last_edit.time[gt]. Use Braze's yyyy-MM-DDTHH:mm:ss-compatible timestamp format.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Campaign Details
Fetch Braze metadata and message details for one campaign. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_campaign_detailsVerify with Get Canvas Details
Fetch Braze metadata, variants, steps, and message details for one Canvas. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_canvas_detailsSAFETY BOUNDARY
Operate Braze with explicit limits
- Authorize Braze with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Braze data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `campaigns.details`, `canvas.details`, `campaigns.list`, and `canvas.list`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Braze task completed successfully.
CONNECTION MODEL
API key
Braze REST API key sent as Authorization: Bearer <key>. Create or view REST API keys in Braze under Settings > APIs and Identifiers > API Keys: https://www.braze.com/docs/api/basics.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Braze.