SFMC write boundaries
What Campaign Builder can read, draft, and write in Salesforce Marketing Cloud.
Campaign Builder is useful because it moves campaign work toward real SFMC assets while preserving review boundaries. This guide separates read paths, draft-building paths, confirmed writes, and manual Marketing Cloud decisions.
Execution boundary
The path from access to a reviewed SFMC write.
A buyer should be able to trace four implementation steps before trusting any production-bound claim: authenticated SFMC context, entitlement filtering, read or preview evidence, and explicit confirmation for writes.
Resolve account and SFMC context
Protected SFMC work starts from first-party sessions, bearer JWTs, SFMC signed_request launches, or SFMC mc_token sessions. The request is normalized to account, tenant, workspace, enterprise, and business-unit context before agent or Factory routes run.
Check entitlement gates
Campaign, Content, Email, Journey, Image, Translator, Advisor, Audience, Bruno, content-block, and Factory surfaces are mounted behind server-side entitlement checks. A connected Marketing Cloud account does not unlock every workflow.
Read and preview before writing
Marketing Cloud route families can retrieve Content Builder assets, email assets, journeys, event definitions, folders, and Data Extension rows so teams can inspect source material before approving draft-building work.
Confirm production-bound writes
Email updates, slot updates, rewrite application, translation application, image insertion, Content Builder publishing, Factory execution, and Bruno write skills are staged with review context instead of running as hidden chat side effects.
Marketing Cloud surfaces
Implemented SFMC operations by workflow.
Campaign Builder content should stay precise about which assets the product can prepare. The implemented surface is broad enough for campaign execution work, but bounded by account configuration and review.
Content Builder assets
Content Agent can send reviewed content to Marketing Cloud when account folder and template settings are configured. The Marketing Cloud route can create or patch Content Builder assets and records resulting asset IDs back on the Campaign Builder story.
Email assets
Email Agent supports SFMC email search, preview, copy, subject and preheader improvement, rewrite, translation, slot-aware HTML edits, and confirmed update paths. Factory can also generate template-based email assets from configured templates.
Journey drafts
Journey Agent can plan, search, clone, or create Journey Builder drafts from configured templates or scratch draft support. The implementation keeps activation warnings visible because activation remains manual in Salesforce Marketing Cloud.
Images
Image Agent supports provider search, saved image assets, generation requests, credit checks, and confirmed SFMC insertion. Content image writes upload the image as a Content Builder asset before updating the related story metadata.
Data Extensions
Factory can create standard or custom Data Extensions and prepare Data Extension folders. Shared SFMC clients also support SOAP row retrieval with paging for audience and Factory-style production flows.
Factory production
Factory is gated as tool:factory and requires settings.factory.enabled, connected SFMC credentials, and configured template assets before campaign drafts, folders, uploads, Data Extensions, emails, previews, variants, or template review can run.
Route evidence
Where technical evaluators can trace the claims.
The buyer-facing boundary maps to route families in the CampaignBuilder implementation: Marketing Cloud, SFMC launch and connection, specialist agents, Bruno, and Factory.
/api/v1/marketingcloud
Production Marketing Cloud routes cover Content Builder publishing, journey and email lookup, journey summary, journey search, recent journeys, entry event creation, journey cloning, scratch draft creation, and journey stats.
/api/v1/sfmc and /api/v1/sfmc-connect
SFMC launch, OAuth callback, BU mapping, unmapped handling, connection save, connection status, connection test, and disconnect routes establish account-scoped Marketing Cloud context before execution work starts.
/api/v1/agent/content and /api/v1/emails
Content and Email Agent routes handle source imports, variants, suggestions, translation, preview, copy, rewrite, and confirmed Content Builder email or content updates.
/api/v1/agent/journey
Journey Agent routes support brief extraction, chat planning, reference journey reuse, email and audience artifact preparation, readiness checks, workflow verification, and draft creation support.
/api/v1/agent/bruno
Bruno discovers entitled skills, collects missing inputs, stages pending write actions, supports dryRun campaign execution, stores durable run state, journals requests, and can resume failed or partial runs.
/api/v1/factory
Factory routes cover campaign drafts, configuration rows, brand language rows, folder creation, image uploads, image-analysis jobs, Data Extensions, template emails, previews, variants, and AI template review.
Evaluator evidence matrix
What to verify before trusting an SFMC execution claim.
Campaign Builder is strongest when technical evaluators can connect website claims to the actual control points in the app: account context, entitlements, preview evidence, prerequisites, and request-level traceability.
Before an agent can act
The request must resolve to authenticated account context and pass the relevant entitlement gate, such as campaign-agent, content-agent, email-agent, journey-agent, image-agent, bruno-super-agent, audience-agent, or tool:factory.
Before SFMC content is changed
Content and Email workflows read or preview source assets first, then use confirmed paths for email copy, rewrite application, translation application, slot-aware updates, Content Builder publishing, and image insertion.
Before a journey draft is created
Journey Agent builds or revises the journeyDraftPlan, resolves reference journeys or configured scratch support, checks readiness, and returns manual activation warnings with draft creation responses.
Before Factory prepares assets
Factory requires the Factory entitlement, enabled account settings, connected SFMC credentials, and configured templates before campaign drafts, folders, image uploads, Data Extensions, emails, previews, variants, or template review can run.
After a production-bound operation
External side effects are tied to request context, account-scoped credentials, route-level guards, centralized error handling, and action logging for operations such as SFMC content publishing, journey creation, and Factory output preparation.
Guardrails
What stays visible before, during, and after execution.
The strongest product position is not unchecked automation. It is faster SFMC production with account scope, request traceability, encrypted credentials, and human review where launch risk is highest.
Journey activation remains a manual Marketing Cloud step after draft creation and readiness review.
SFMC credentials are account or workspace scoped, encrypted at rest, and resolved through shared Marketing Cloud helpers.
Mutating browser requests use CSRF checks for first-party and SFMC cookie sessions unless a route is explicitly bypassed.
Request IDs are assigned and propagated through approved outbound SFMC clients for traceability.
Logs and centralized error handling are designed to avoid exposing sensitive credentials or raw payloads.
The site should describe these as implementation guardrails, not as a standalone compliance certification.
Evaluator FAQ
Short answers for security, SFMC admin, and marketing ops review.
Does Campaign Builder write directly into Salesforce Marketing Cloud?
Yes, for specific scoped operations such as Content Builder assets, email assets, folders, Data Extensions, image uploads, previews, and Journey Builder drafts. Those operations depend on authentication, entitlement checks, account-scoped SFMC credentials, configuration, and confirmation where production-bound writes are involved.
Can Bruno execute SFMC work without review?
Bruno can classify requests, discover entitled skills, dry-run campaign execution, and prepare durable run state. Write skills are staged with missing-input handling and preview summaries so production-bound actions are confirmed before execution.
What does Factory change in Marketing Cloud?
Factory can prepare campaign folders, Data Extension folders, image uploads, Data Extensions, template-based emails, preview drafts, variant previews, and template reviews when the account has Factory enabled and the required SFMC templates are configured.
What stays outside Campaign Builder automation?
Final Journey activation and launch decisions stay in Salesforce Marketing Cloud. Campaign Builder can create draft artifacts and warnings, but it does not claim automatic Journey activation, unrestricted writes, or guaranteed compliance.
Next reading
Use write boundaries with the pilot checklist.
Pair this article with SFMC connection readiness and the technical FAQ when evaluating account setup, BU mapping, entitlements, Bruno dry runs, Factory prerequisites, and manual activation boundaries.