Factory production workflow
How Factory prepares Salesforce Marketing Cloud campaign drafts.
Factory is Campaign Builder's entitlement-gated production workflow for turning structured campaign inputs into account-scoped SFMC folders, images, Data Extensions, template-based emails, previews, and template review outputs.
Readiness gates
Factory only runs when the account is configured for it.
The implemented Factory router is mounted at /api/v1/factory, gated as tool:factory, and checks account readiness before template-dependent production work continues.
Production flow
What Factory does from draft to SFMC preview.
Factory is useful to evaluators because its output path is concrete: campaign drafts are saved, account configuration is loaded, assets and audience structures are prepared, and email previews are generated for review.
Save structured campaign drafts
Factory campaign routes persist drafts and version metadata in the account-scoped Factory Campaigns collection before production assets are prepared.
Load configuration and brand language
Config and brand-language rows give Factory account-specific defaults, taxonomy, template helpers, and language guidance for repeatable campaign production.
Create SFMC folders and upload images
Asset routes prepare Content Builder campaign folders, Data Extension folders, upload selected images, and expose image-analysis job status for reviewed campaign inputs.
Prepare Data Extensions
Factory Data Extension routes support standard and custom creation paths so campaign drafts can be paired with the audience structures needed for SFMC execution review.
Generate template-based emails
Email routes check configured templates, create template-based email assets, expose raw email data, and support preview requests against accessible Marketing Cloud email IDs.
Review previews and variants
Preview routes create draft previews, load variant previews, and can run AI template review so teams can inspect output before continuing in Marketing Cloud.
Bruno execution path
How Bruno turns a campaignSpec into Factory work.
Bruno campaign execution does not treat Factory as a black box. The implemented orchestrator uses a predictable stage plan so evaluators can inspect what will be created, reused, skipped, warned, or validated before continuing in Marketing Cloud.
Plan
Bruno normalizes the campaignSpec, builds the stage plan, and can return dry-run proposed artifacts before any Factory endpoint is called.
Folders
The folders stage calls Factory assets/folder with the Data Extension name, optional folderPath, and pathTokens, then records folder provenance for review and rollback eligibility.
Data Extensions
The data_extensions stage calls Factory data-extensions/custom with the normalized name, customer key, description, and fields. It warns when retention policy or provenance details are missing.
Content assets
The content_assets stage resolves referenced content blocks and assets from campaignSpec as reused artifacts instead of inventing new Content Builder assets.
The email stage requires at least one content block, then calls Factory emails for each campaign email using subject, preheader, blocks, campaign metadata, and optional target folder IDs.
Preview and validate
The preview stage creates a Factory preview draft and attempts a rendered preview when email ID, Data Extension key, and contact key are available; validate then checks subject, preheader, preview inputs, and compliance markers.
Run evidence
What to ask for during a Factory-backed Bruno evaluation.
A useful pilot should show the dry-run plan, stage warnings, and confirmed-run evidence rather than asking teams to trust a chat response or a finished asset alone.
Implementation map
Factory claims map to implemented route families.
Technical buyers can evaluate Factory by tracing the public claim back to its API surface: campaigns, config, assets, Data Extensions, email previews, variants, and template review.
Campaigns
GET /api/v1/factory/campaigns, POST /campaigns/draft, GET /campaigns/:id, and DELETE /campaigns/:id manage Factory drafts.
Configuration
GET /config plus config row and brand-language row routes expose account-level Factory setup data.
Assets
POST /assets/folder, POST /assets/folder/data-extension, POST /assets/upload-images, and image-analysis job lookup prepare SFMC production structure.
Data Extensions
POST /data-extensions and POST /data-extensions/custom create campaign audience structures through shared SFMC clients.
Emails and previews
GET /template-check, POST /emails, POST /emails/:id/preview, GET /emails/:id/raw, POST /preview/draft, and GET /preview/variants support reviewed email production.
Template review
POST /template-review runs AI review over configured template output rather than claiming automatic approval or launch.
Guardrails
Factory respects SFMC access and review boundaries.
Factory accelerates production setup without removing account scoping, template prerequisites, credential boundaries, or Marketing Cloud review.
Factory is entitlement-gated
The route family is mounted under /api/v1/factory and gated as tool:factory, so availability follows account entitlement and server-side checks.
SFMC writes stay scoped
Folder creation, uploads, Data Extension creation, email generation, and previews use connected account or workspace Marketing Cloud credentials.
Outputs remain reviewable drafts
Factory prepares folders, assets, Data Extensions, template-based emails, previews, variants, and template reviews. Journey activation and final launch decisions remain in Marketing Cloud.
Factory FAQ
The operational questions buyers usually ask first.
Factory should be evaluated as a practical SFMC production workflow engine: specific inputs, configured account settings, reviewable outputs, and scoped write paths.
Is Factory a generic file exporter?
No. Factory is implemented as a Campaign Builder API tool for preparing Salesforce Marketing Cloud draft artifacts through account-scoped routes and shared SFMC clients.
What must be configured before Factory can run?
The account needs the Factory entitlement, settings.factory.enabled must be true, SFMC credentials must be connected, and template-dependent flows need configured SFMC template assets.
Which SFMC artifacts can Factory prepare?
Factory can prepare campaign drafts, Content Builder folders, image uploads, Data Extension folders and records, Data Extensions, template-based emails, preview drafts, variant previews, and AI template reviews.
Does Factory bypass Marketing Cloud review?
No. Factory moves campaign production toward reviewed SFMC drafts and previews. It does not claim automatic campaign launch, unrestricted SFMC writes, or guaranteed compliance.
Evaluation takeaway
Factory reduces setup work before SFMC review.
For Salesforce Marketing Cloud teams, the value is not a separate campaign platform. Factory helps standardize the production steps between an approved campaign input and the draft assets teams inspect in Content Builder, Email Studio, Data Extensions, and related SFMC review flows.