Brief to build package
Campaign Planning for Salesforce Marketing Cloud teams.
How Campaign Builder turns typed intent, uploaded context, workspace knowledge, and campaign history into structured briefs, audience direction, email plans, journey plans, and Bruno-ready execution specs for Salesforce Marketing Cloud teams.
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.
Campaign Agent supports ideate, brief, top brief, and build phases for turning campaign intent into structured execution inputs.
Uploaded working files can ground the campaign brief alongside session context and tenant/workspace-scoped knowledge.
Build output can include email draft definitions, audience direction, Data Extension plans, journey plans, validation warnings, grounding references, and a Bruno-compatible campaignSpec.
Confirmed execution starts with a dry run before Bruno durable execution creates draft artifacts through entitled downstream skills.
Implementation map
What technical evaluators can trace.
Campaign Agent is mounted under `/api/v1/agent/campaign/*` and `/api/v1/campaigns/*` behind the agent:campaign-agent entitlement.
`POST /api/v1/agent/campaign/generate-brief` and `POST /api/v1/agent/campaign/execute-campaign` support normalized brief and build-package workflows.
Working-file context accepts PNG, JPG, GIF, PDF, DOC/DOCX, and XLS/XLSX uploads up to 15 MB per file, then stores summarized context with a six-hour TTL.
Grounding references expose safe metadata such as title, section, document ID, snippets, rationale, and influenced fields instead of raw unrestricted source material.
Build packages advertise handoff targets for Email Agent and, in single-email execution mode, Audience Agent and Journey Agent before Bruno campaign execution.
Review boundaries
Where Campaign Builder stops before launch risk.
Boundary
Campaign planning does not send campaigns, activate journeys, or bypass SFMC permissions.
Boundary
Campaign Agent access depends on authentication, account context, and the campaign-agent entitlement.
Boundary
Uploaded context and knowledge grounding are used to shape briefs and build packages, not to approve production execution automatically.
Boundary
Journey Builder activation remains manual even when Campaign Agent produces a journey plan and Bruno creates draft artifacts.
FAQ
Evaluation questions for Campaign Planning.
What does Campaign Agent produce from a campaign idea?
It can produce a normalized brief, audience direction, email content plan, Data Extension plan, journey plan, validation warnings, grounding references, build package, and Bruno-compatible campaignSpec.
Can teams upload source material for planning?
Yes. Campaign Agent accepts supported image, document, PDF, and spreadsheet uploads, summarizes working-file context, and uses tenant/workspace knowledge grounding when available.
Does the planning workflow create live SFMC sends?
No. Campaign planning prepares reviewed handoff artifacts. Confirmed execution creates draft artifacts through Bruno and downstream skills, while sends and Journey activation remain manual Marketing Cloud decisions.
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.