← सभी गाइड
Playbook गाइड · मुफ़्त

Check Your Braze Campaigns, Segments, and Revenue Through Your Muse

सत्यापित 2026-11-19

Through a custom connector, your muse can read your Braze workspace: how campaigns and journeys performed, how big your audience groups are, and what your app earned, with sends held for your yes.

What it does

The connector carries 23 tools and works with an API key tied to one workspace and its REST address. For campaigns and Canvases, the muse reads daily results: sends, deliveries, opens, clicks, conversions, and revenue, per channel. It reads segments and estimated sizes, active user counts, custom events, purchases and revenue by product, and user profiles with subscription groups. Three tools write, all asking first: recording attributes, events, and purchases, which can move people into segments and start journeys. Sending an API campaign or Canvas sends real messages: for a broadcast the muse names the campaign, channel, and exactly who receives it, then waits for an explicit yes. Deleting users starts switched off.

How to use it

  1. In Braze, open Settings, then APIs and Identifiers, then API Keys, and create a key for one workspace. Check the reading permissions the tools need, and the writing ones only if you plan to use them. Permissions cannot change later, so a missing one means a new key.
  2. Copy the key and the REST endpoint, which must match your instance; a key works only on its own instance.
  3. In AnythingMCP, install the Braze connector and paste both values where it asks. Never paste the key into a chat.
  4. In Muse, open Settings, then Connectors, and add a custom connector with the address AnythingMCP gives you.
  5. Start with a read: ask which campaigns went out in the last 30 days and earned the most, then compare one figure with the dashboard.

What you need

  • A Muse account that can add custom connectors
  • An AnythingMCP workspace
  • A Braze workspace and an API key with the permissions you need

What to watch for

  • Anyone who can use the connector sees everything the key can read across the workspace, including user profiles, so share it only with people allowed to see profiles.
  • A 401 usually means a wrong key or an endpoint on another instance. A 403 means a missing permission: make a new key.
  • Profile reads cap at 250 calls a minute on newer workspaces.
  • Templates, catalogs, and scheduled messages are not covered, and no broadcast goes out on a half-heard yes.
  • This is a custom connector, and Meta does not review custom connectors. You can disconnect it in Settings at any time. The muse prepares, you decide.

क्या आपने यह गाइड आज़माई?

समुदाय को बताएँ कि यह कैसा रहा, या इसे चलाने में मदद माँगें।

MuseFM पर इस बारे में बात करें →

Playbook Pro

क्या आप पाठ छोड़ना चाहते हैं?

अपने एजेंट को एक साथ सब कुछ सीखने में मदद करें। 1,015 स्किल, एक पास, 90 दिनों के लिए $49।

Pro Pass लें
और गाइड →