Content Builder production
Content Blocks for Salesforce Marketing Cloud teams.
How Campaign Builder helps teams create, review, and publish reusable Salesforce Marketing Cloud Content Builder assets and content blocks from campaign context.
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.
Content Agent creates and refines content from briefs, templates, images, or existing assets.
Content publishing routes can create approved Content Builder assets with configured asset type and folder behavior.
Image and localization flows can support selected assets, translated variants, and review-ready content before SFMC handoff.
Bruno can route content work through entitled skills and keep write actions staged for confirmation.
Implementation map
What technical evaluators can trace.
Mounted Content Agent and content block routes include `/api/v1/agent/content/*` and `/api/v1/blocks/content` behind entitlement checks.
Content Agent localizes generated text and story metadata through shared localization helpers before returning localized variants.
SFMC Content Builder operations use shared Marketing Cloud helpers for asset creation, patching, image upload, and folder lookup.
Advisor and knowledge context can support content decisions, but production writes remain in confirmed specialist paths.
Review boundaries
Where Campaign Builder stops before launch risk.
Boundary
Content Blocks do not bypass Marketing Cloud review or account entitlements.
Boundary
Content Builder writes depend on connected SFMC credentials and configured account/workspace context.
Boundary
Localization preserves URLs, personalization tokens, AMPscript, placeholders, and HTML structure where requested.
FAQ
Evaluation questions for Content Blocks.
Can Campaign Builder create reusable Content Builder assets?
Yes. Implemented content and content block flows support creating or publishing reviewed Content Builder assets through scoped Marketing Cloud helpers.
Does it publish every generated suggestion automatically?
No. Bruno and specialist write paths stage production-bound actions for review and confirmation before SFMC writes run.
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.