Bruno Super Agent
How Bruno coordinates Campaign Builder execution.
Bruno is Campaign Builder's orchestration layer for turning a marketer's request into the right specialist workflow, required inputs, reviewed write actions, and Salesforce Marketing Cloud draft execution.
Orchestration path
From plain-language request to the right execution path.
Bruno is useful because it sits above specialist agents and shared skills. It classifies requests, checks what the account can actually run, asks for missing inputs, and stages writes for review.
Classify the request
Bruno uses the published workflow definitions for make_content, make_campaign, make_journey, make_email, make_image, and the bruno.router meta-workflow to route requests to the right specialist path.
Discover entitled skills
The shared skill registry is filtered through the account entitlement context before Bruno offers or executes Campaign, Content, Email, Journey, Image, Advisor, Audience, Factory, Data Extension, or AMPscript skills.
Collect missing inputs
When a skill needs required fields, Bruno stores a pending action for the session, asks for the missing values, and resumes the same action once the user supplies them.
Confirm write actions
Write skills are staged with preview summaries and require explicit confirmation before SFMC email updates, content publishing, image insertion, Factory execution, or other production-bound writes run.
Specialist agents
Bruno connects the campaign work, it does not replace it.
The implemented Bruno route advertises specialist capabilities for campaign planning, journeys, emails, content, images, Advisor guidance, audience work, Data Extensions, AMPscript, and localization.
Campaign execution
Dry runs, durable runs, and Factory-backed SFMC drafts.
Bruno campaign execution is grounded in a normalized campaignSpec. Evaluators can inspect dry-run artifacts first, then use confirmed execution for account-scoped draft production.
Dry-run first
The Bruno campaign execution path accepts dryRun so teams can inspect stage plans, proposed artifacts, missing Data Extension names, missing content blocks, missing subjects, and other readiness issues without SFMC side effects.
Durable runs
Confirmed execution creates account-scoped run records with stage state, artifact ledgers, summaries, request IDs, and journals so partial work can be inspected instead of disappearing into a chat response.
Resume support
resumeRunId allows a failed or partial run to continue when the campaignSpec and mode still match the stored run, reducing duplicate SFMC work after transient failures.
Factory-backed production
When Bruno moves into campaign execution, it calls the internal Factory routes for folders, Data Extensions, email generation, preview drafts, variant previews, and template review where configured.
Recovery model
Durable execution leaves evidence when work partially completes.
Bruno execution is designed for technical review after both dry runs and confirmed runs. The implementation records stage state, journals, artifacts, rollback metadata, and resume constraints so evaluators can see what happened before continuing in Marketing Cloud.
Run journal
Each durable campaign execution run stores request-aware journal entries such as run creation, resume events, stage transitions, warnings, and failure details for later inspection.
Artifact ledger
Created and reused outputs are tracked as run artifacts with stage, ID, customer key, source, and rollback eligibility metadata where the underlying SFMC operation returns enough detail.
Rollback scope
Rollback is limited to created artifacts with matching run provenance. It can attempt supported cleanup for Data Extensions, Content Builder assets, email assets, preview drafts, and folders, then returns warnings or failures instead of hiding partial cleanup.
Resume guard
resumeRunId only continues a run when the requested mode and campaignSpec match the stored run, which helps avoid duplicating SFMC work after a transient execution failure.
Execution guardrails
Bruno keeps SFMC work scoped and reviewable.
The orchestration model is designed around authenticated account context, entitlement-filtered skills, connected Marketing Cloud credentials, request tracing, and explicit review before production-bound writes.
Authenticated account context
Bruno routes require authenticated users and account IDs before reading conversation context, workspace insights, credentials, skills, pending actions, or run state.
Scoped SFMC credentials
Marketing Cloud operations use connected account or workspace credentials, business-unit context, shared SFMC helpers, and request ID propagation for outbound calls.
Draft-only launch boundary
Journey creation remains draft-oriented. Bruno explicitly returns activation instructions because journey activation and final launch decisions stay in Salesforce Marketing Cloud.
Technical evaluator FAQ
The boundaries to verify before trusting orchestration.
Bruno should be evaluated as an execution coordinator with guardrails, not as a black-box sender or a replacement for Marketing Cloud launch controls.
Is Bruno a single autonomous sender?
No. Bruno is the orchestration layer. It can coordinate specialist agents and confirmed write skills, but high-risk launch decisions such as Journey activation remain manual in Salesforce Marketing Cloud.
How does Bruno avoid offering unavailable tools?
Bruno lists skills through the shared registry using the current account entitlement context, so the available skill set follows the account's enabled agents, blocks, and tools.
What happens when a write skill is incomplete?
Bruno stores a pending action with the draft arguments, missing fields, and preview summary, asks for the missing input, and resumes only after required fields and confirmation are present.
How should technical teams evaluate Bruno execution?
Start with dry runs, inspect the proposed stage plan and warnings, verify Factory and SFMC prerequisites, then review the durable run journal and draft artifacts before continuing in Marketing Cloud.
Evaluation takeaway
Bruno makes Campaign Builder feel like one execution layer.
For Salesforce Marketing Cloud teams, Bruno's value is reducing handoff drag across planning, copy, email, journey, image, localization, Advisor, Data Extension, and Factory workflows while preserving the review boundaries that protect production SFMC assets.