SFMC draft production
Factory Production for Salesforce Marketing Cloud teams.
How Campaign Builder Factory turns structured campaign inputs into Salesforce Marketing Cloud campaign drafts, Content Builder folders, image uploads, Data Extensions, template-based emails, previews, variants, and template reviews.
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.
Factory persists structured campaign drafts and version metadata before production assets are prepared.
Factory asset routes create Content Builder campaign folders, Data Extension folders, upload selected images, and expose image-analysis job status.
Factory can create standard or custom Data Extensions for configured campaign production workflows.
Factory email and preview routes check configured templates, generate template-based email assets, return raw or rendered previews, produce variant previews, and run AI template review.
Implementation map
What technical evaluators can trace.
Factory is mounted under `/api/v1/factory` and gated by the `tool:factory` entitlement.
Prerequisites include `settings.factory.enabled` set to true, connected account SFMC credentials, and configured SFMC template assets for template-dependent email and preview flows.
Implemented sub-routers cover campaigns, config, brand language, assets, Data Extensions, emails, previews, variants, and template review.
Concrete routes include `POST /api/v1/factory/campaigns/draft`, `POST /assets/folder`, `POST /assets/folder/data-extension`, `POST /assets/upload-images`, `POST /data-extensions`, `POST /data-extensions/custom`, `GET /template-check`, `POST /emails`, `POST /preview/draft`, `GET /preview/variants`, and `POST /template-review`.
Factory routes use shared SFMC clients and typed error handling with request correlation rather than ad hoc Marketing Cloud writes.
Review boundaries
Where Campaign Builder stops before launch risk.
Boundary
Factory availability depends on authentication, account context, and the factory tool entitlement.
Boundary
SFMC-facing Factory work depends on connected account or workspace Marketing Cloud credentials and configured template assets where required.
Boundary
Factory prepares reviewed draft artifacts and previews; it does not automatically send campaigns, activate journeys, or bypass Marketing Cloud approval steps.
Boundary
Data Extension and asset operations stay within scoped SFMC client paths rather than unrestricted database or Content Builder access.
FAQ
Evaluation questions for Factory Production.
What does Factory create for an SFMC campaign?
Factory can prepare campaign drafts, Content Builder campaign folders, Data Extension folders, image uploads, Data Extensions, template-based emails, preview drafts, variants, and AI template reviews.
What needs to be configured before Factory production work runs?
The account needs the factory entitlement, `settings.factory.enabled` must be true, SFMC credentials must be connected, and template-dependent flows need configured Marketing Cloud template assets.
Does Factory launch the campaign?
No. Factory creates reviewed SFMC draft artifacts and preview evidence. Final send approvals, campaign launch decisions, and Journey activation remain manual Marketing Cloud steps.
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.