Braze Integration for AI Agents
Connect your AI agent to 98 QA'd Braze actions via MCP, A2A, or SDK, with agent authentication, tool-calling execution, and security built-in, plus 105 events to subscribe to.
Braze AI Agent Actions
98 production-ready actions for your agent to do more on Braze.
Braze Webhook Events
105 real-time Braze events your AI agent can subscribe to.
- Active Check Responds with 200 OK to any Braze delivery that is neither a Currents batch nor a transactional postback.
- Email Abort Fired if an email message was aborted by Liquid abort logic or a similar rule.
- Email Bounce Fired when an Internet Service Provider returns a hard bounce.
- Email Click Fired when a user clicks an email.
- Email Deferral Fired when an Internet Service Provider does not immediately deliver the email to a non-hard bounced email address and Braze retries the email for up to 72 hours.
- Email Delivery Fired when an email made it successfully to the end user's inbox.
- Email Mark As Spam Fired when the end user hits the "spam" button on the email.
- Email Open Fired when a user opens an email.
- Email Retry Fired when a message is deprioritized or frequency capped and will be retried later within the configured retry window.
- Email Send Fired when an email send request was successfully communicated between Braze and SendGrid.
- Email Soft Bounce Fired when an Internet Service Provider returns a soft bounce.
- Email Unsubscribe Fired when the end user has clicked "unsubscribe" from the email.
- Transactional Email Sent Fired when Braze successfully dispatches the transactional email to its email sending partner.
- Transactional Email Processed Fired when the email sending partner receives the transactional email and prepared it for the inbox provider.
- Transactional Email Delivered Fired when the inbox provider accepts the transactional email.
- Transactional Email Bounced Fired when the inbox provider rejects the transactional email (metadata.reason explains why).
- Transactional Email Aborted Fired when Braze cannot dispatch the transactional email, for example a missing email address or abort logic (metadata.reason explains why).
- LINE Abort Fired when a scheduled LINE message cannot be delivered, before sending to LINE.
- LINE Click Fired when a user clicks a link in a LINE message where the link's domain matches the click tracking domain.
- LINE Inbound Receive Fired when a LINE message is received from a user.
- LINE Retry Fired when a message is deprioritized or frequency capped and will be retried later within the configured retry window.
- LINE Send Fired when a LINE message is sent to LINE.
- RCS Abort Fired when an RCS send is interrupted due to an error detected within Braze, and the message is dropped.
- RCS Click Fired when the user interacts with an RCS message in a way that involves tapping or clicking on a UI element.
- RCS Delivery Fired when an RCS message is successfully delivered to a user's mobile device.
- RCS Inbound Received Fired when Braze receives an RCS message that originates from the user.
- RCS Read Fired when a user opens an RCS message on their device, indicating that they have seen or read the message content.
- RCS Rejection Fired when an RCS message fails to be delivered to a user's mobile device due to intervention by the carrier.
- RCS Send Fired when an RCS message is sent out of Braze to its last-mile delivery partners.
- SMS Abort Fired if an SMS message was aborted by Liquid abort logic or a similar rule.
- SMS Carrier Send Fired when an SMS is sent to the carrier.
- SMS Delivery Fired when an SMS was successfully delivered to the user's mobile phone.
- SMS Delivery Failure Fired when an SMS experiences delivery failure.
- SMS Inbound Received Fired when one of your users sends an SMS to a phone number in one of your Braze SMS subscription groups.
- SMS Rejection Fired when an SMS send gets rejected by the carrier.
- SMS Retry Fired when a message is deprioritized or frequency capped and will be retried later within the configured retry window.
- SMS Send Fired when Braze sends an SMS message to a user.
- SMS Short Link Click Fired when a user clicks an SMS short link.
- Webhook Abort Fired if a webhook message was aborted by Liquid abort logic or a similar rule.
- Webhook Failure Fired if a webhook message was delivered but failed with an error response from the endpoint.
- Webhook Retry Fired when a message is deprioritized or frequency capped and will be retried later within the configured retry window.
- Webhook Send Fired when a webhook was processed and sent to the third party specified in that webhook.
- WhatsApp Abort Fired if a WhatsApp message was aborted by Liquid abort logic or a similar rule.
- WhatsApp Tracked Link Click Fired when a user clicks a link or button in a WhatsApp message where the link's domain matches the click tracking domain.
- WhatsApp Delivery Fired when a WhatsApp message made it successfully to the user's device.
- WhatsApp Failure Fired when WhatsApp cannot deliver the message to the user.
- WhatsApp Inbound Received Fired when one of your users sends a WhatsApp message to a phone number in one of your Braze WhatsApp subscription groups.
- WhatsApp Read Fired when a WhatsApp message is read by the user.
- WhatsApp Retry Fired when a message is deprioritized or frequency capped and will be retried later within the configured retry window.
- WhatsApp Send Fired when a send request was successfully communicated between Braze and WhatsApp.
- Banner Abort Fired when an originally scheduled banner message was aborted for some reason.
- Banner Click Fired when a user clicks a banner.
- Banner Dismissal Fired when a user dismisses a banner.
- Banner Impression Fired when a user views a banner, including control group users when an impression is logged.
- Content Card Abort Fired if a Content Card message was aborted by Liquid abort logic or a similar rule.
- Content Card Click Fired when a user clicks a Content Card.
- Content Card Dismiss Fired when a user dismisses a Content Card.
- Content Card Impression Fired when a user views a Content Card.
- Content Card Send Fired when a Content Card gets sent to a user.
- Feature Flag Experiment Impression Fired whenever a user has had an opportunity to interact with your feature, or when they could have interacted if the feature is disabled (in the case of a control group in an A/B test).
- In-App Message Abort Fired when an originally scheduled in-app message was aborted.
- In-App Message Click Fired when a user clicks an in-app message.
- In-App Message Impression Fired when a user views an in-app message.
- Landing Page Click Fired when an end user clicks on select elements and form fields on a landing page.
- Landing Page Form Submission Fired when an end user completes a form on a landing page and clicks on the button to submit the information.
- Landing Page Impression Fired when an end user's browser loads and displays a landing page.
- Live Activity Outcome Fired when Braze receives a response from a third-party provider (for example APNs) after a Live Activity request.
- Live Activity Send Fired when the Braze system makes a request to its provider regarding Live Activity.
- Push Notification Abort Fired if a push notification message was aborted by Liquid abort logic or a similar rule.
- Push Notification Bounce Fired when an error is received from either Apple Push Notification Service or Firebase Cloud Messaging.
- Push Notification iOS Foreground Open Fired when a user opens an iOS push notification while the app is in the foreground (legacy Obj-C SDK only; deprecated).
- Push Notification Open Fired when a user directly clicks on the push notification to open the application.
- Push Notification Retry Fired when a message is deprioritized or frequency capped and will be retried later within the configured retry window.
- Push Notification Send Fired when Braze processes a push message for a user, communicating this to Apple Push Notification Service or Firebase Cloud Messaging.
- Survey Response Fired when an end user submits a survey response.
- Live Activity Push To Start Token Change Fired when Braze syncs the Live Activity push to start token with the user.
- Live Activity Update Token Change Fired when Braze syncs Live Activity update token with the user.
- Push Notification Token State Change Fired when a push token is inserted, updated, or removed.
- Agent Executed Fired when a BrazeAI Agent Console agent is executed.
- Tool Invocation Fired when a BrazeAI agent invokes a tool (a function given to the LLM to fulfil an objective).
- Content Optimizer Component Store Update Fired when the Content Optimizer component store is updated with a component combination.
- Campaign Conversion Fired when a user does an action that has been set as a conversion event in a campaign.
- Campaign Control Group Enrollment Fired when a user is enrolled in a control variant set on a multi-variant campaign.
- Canvas Conversion Fired when a user does an action that has been set as a conversion event in Canvas.
- Canvas Entry Fired when a user enters into the Canvas.
- Canvas Content Optimizer Step Conversion Fired when a user converts on a Content Optimizer Canvas step.
- Canvas Content Optimizer Step Send Fired when a Content Optimizer Canvas step sends a message to a user.
- Canvas Exit Match Audience Fired when a user has exited a Canvas by matching an audience.
- Canvas Exit Perform Event Fired when a user has exited a Canvas by performing an event.
- Canvas Experiment Step Conversion Fired when a user converts for a Canvas experiment step.
- Canvas Experiment Split Entry Fired when a user enters a Canvas experiment step path.
- Canvas Step Progression Fired when a user progresses through a step in a Canvas with some outcome.
- Uninstall Fired when a user uninstalls an app.
- Global Subscription State Change Fired when Braze receives a request to update the global subscription state of the user.
- Subscription Group State Change Fired when the subscription state of a user in a subscription group changes.
- Custom Event Fired when a specific custom event is triggered.
- Install Attribution Fired when an app installation is attributed to a source.
- Location Fired when a user visits a specified location.
- Purchase Fired when a user makes a purchase.
- First Session Fired when a user starts their first session in your application.
- Session End Fired when a user exits your application, ending their current session.
- Session Start Fired when a user starts a session.
- User Delete Request Fired when Braze receives a request to delete a user profile.
- User Orphan Fired when a user profile is orphaned because it was merged into another profile (properties.orphaned_by_id identifies the surviving profile).
- User Profile Update Fired when a user profile or its attributes are updated (standard fields plus custom_attributes as a JSON string).
Braze AI Agent Use Cases
Connect your AI agent to Braze and help your team scale the marketing operations they run by hand today.
Use StackOne to connect your AI agent to your marketing automation, CRM, and email tools to automate lead nurture email sequences.
ViewUse StackOne to connect your AI agent to your marketing automation, email, and analytics platforms to automate campaign performance reporting.
ViewUse StackOne to connect your AI agent to your document stores, email platforms, and messaging tools to automate content repurposing and distribution.
ViewDo More, Build Less
Integration Infrastructure for Braze AI Agents
"What impressed us most about StackOne is its ambition and clarity. They're creating infrastructure that modern software and the entire AI agent ecosystem can rely on. The depth of secure integrations, the pace of delivery, and the team's foresight into AI's future uniquely position StackOne to redefine this category."
Luna Schmid, Partner at GV
"We've been impressed by how quickly and deeply StackOne integrates with complex enterprise systems -- and now, with their focus on agent-to-agent interoperability, they're unlocking even more powerful use cases for customers. StackOne delivers all of the above in a universal layer -- without compromise."
Barbry McGann, SVP at Workday Ventures
Braze AI agent integration resources
Webhooks for AI agents: why agentic workflows need them purpose-built
AI agents can act the moment a system changes, using webhooks. But webhooks built for software hit three limits in agentic workflows. Here is how to fix each.
7 min read
Agentic Context Engineering: Why AI Agents Kill Their Own Context Windows
AI agents exceed their context windows without knowing it. Six failure patterns and seven survival architectures for agentic context engineering.
15 min
MCP Code Mode: Keeping Tool Responses Out of Agent Context
Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.
11 min
Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery
Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.
10 min
Put your AI agents to work
All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.