Super Agent workflow routing
Bruno Orchestration for Salesforce Marketing Cloud teams.
How Bruno coordinates Campaign Builder specialist agents, missing inputs, confirmed write actions, and Factory-backed Salesforce Marketing Cloud draft execution.
What it supports
Concrete workflow support, not generic AI copy.
This use case is grounded in implemented Campaign Builder routes, agents, shared SFMC clients, and documented review boundaries.
Bruno routes requests across Campaign, Content, Email, Journey, Image, Advisor, Audience, Factory, Data Extension, and AMPscript skills when those skills are available to the account.
The shared skill registry exposes required fields, prompts, ownership, entitlement metadata, and confirmRequired flags so Bruno can ask for missing values before execution.
Write skills are staged as pending actions with preview summaries and require explicit confirmation before SFMC-facing execution runs.
Bruno campaign execution supports dryRun planning, durable run records, stage state, artifact ledgers, request journals, and resume support for partial runs.
Implementation map
What technical evaluators can trace.
Bruno is implemented under `/api/v1/agent/bruno` with skill planning, pending action storage, missing-field prompts, confirmation replies, and execution formatting.
Workflow execution routes expose run, resume, and get endpoints while the executor enforces per-skill entitlements and the write double-gate.
Bruno campaign orchestration persists account-scoped run records with campaignSpec, mode, stage state, artifact ledgers, summaries, request IDs, and journals.
Confirmed Bruno production flows can call internal Factory routes for folders, Data Extensions, email generation, preview drafts, variant previews, and template review.
Review boundaries
Where Campaign Builder stops before launch risk.
Boundary
Bruno does not bypass specialist agent entitlements or account-scoped skill availability.
Boundary
SFMC write actions require confirmation and enabled write execution rather than running as hidden chat side effects.
Boundary
Dry runs produce stage plans and proposed artifacts without SFMC side effects.
Boundary
Journey activation and final campaign launch decisions remain manual inside Salesforce Marketing Cloud.
FAQ
Evaluation questions for Bruno Orchestration.
Can Bruno decide which Campaign Builder agent should handle a request?
Yes. Bruno can select from the entitlement-filtered shared skill registry and route work to specialist skills when the request matches implemented Campaign Builder workflows.
Can Bruno run production work without review?
No. Implemented write skills use pending actions, preview summaries, explicit confirmation, entitlement checks, and enabled write execution before SFMC-facing work runs.
Next step
Review this workflow against your SFMC setup.
Bring one existing campaign, journey, email, Content Builder process, or Data Extension workflow to the demo so the evaluation can stay concrete.