Content Agent workflow
How Content Agent turns grounded inputs into SFMC-ready content.
Content Agent is Campaign Builder's workflow for creating, refining, localizing, varianting, and handing off campaign content. It connects source-backed drafts to Knowledge, Content Builder, CloudPage previews, and Marketing Cloud write paths without hiding review requirements.
Content workflow
From source-backed draft to reviewed Content Builder handoff.
Content Agent is useful when campaign teams need more than generic copy: it tracks the source, works against account style settings, produces channel variants, and only reaches SFMC through configured routes.
Start from a grounded source
Content Agent can create drafts from uploaded images, URL imports, readable Knowledge documents, Content Builder assets, or existing local content instead of treating every request as a blank prompt.
Refine the working content
Authenticated routes support content list, detail, update, delete, chat, feedback, temporary context, settings, field suggestions, and channel configuration for reviewable iteration.
Generate channel variants
Variant routes transform a core content object into requested channel output, persist variants by channel, and keep source metadata so evaluators can see where the draft came from.
Prepare SFMC outputs
Content can be saved to Knowledge, created or updated as a Content Builder asset, rendered against configured CloudPage templates, or sent to Marketing Cloud only through authenticated, scoped routes.
Implementation map
What evaluators can trace to Content Agent routes.
The implemented route surface separates sources, iteration, variants, translation, Knowledge handoff, Content Builder saves, CloudPage rendering, and constrained AMPscript execution.
Content Agent is mounted under /api/v1/agent/content/* behind the agent:content-agent entitlement; content block workflows are exposed through /api/v1/blocks/content behind entitlement checks.
Source routes include POST /sources/url, POST /sources/knowledge, POST /sources/content-builder, and POST /sources/local for URL, Knowledge, Content Builder, and local-content drafts.
Iteration routes include GET /, GET /:id, PUT /:id, DELETE /:id, POST /chat, POST /feedback, GET/POST /context, DELETE /context/:id, GET /channels, and GET /settings.
Variant and field routes include GET /:id/variant, POST /:id/variants, POST /:id/suggest, and POST /:id/translate for channel output, field suggestions, and localized story metadata.
Handoff routes include POST /:id/knowledge, POST /:id/content-builder, POST /:id/cloudpage/render, and POST /:id/sendToMC for reviewed Knowledge and SFMC Content Builder paths.
Content Agent exposes only ampscript.* skill execution through /skills and /skills/execute, and the execute route rejects non-AMPscript skill IDs.
Readiness gates
What must be available before content reaches SFMC.
Content Agent can support SFMC-facing content work only when entitlement, authentication, account scope, SFMC credentials, folder configuration, and template configuration match the requested action.
The account must have the agent:content-agent entitlement before Content Agent routes can run.
All Content Agent routes are authenticated, and content records are filtered through the current account, tenant, workspace, and user context.
Content Builder source, save, CloudPage save, and send-to-Marketing-Cloud paths require connected SFMC credentials for the current account or user context.
Content Builder writes require an explicit Content Builder folder ID supplied by the request or account Content Agent settings.
CloudPage rendering depends on configured account cloudPageTemplates; the implementation does not use built-in production templates as fallbacks.
Evaluation evidence
What to ask for in a Content Agent SFMC walkthrough.
A useful evaluation should prove the implemented route behavior, saved artifacts, and guardrails instead of stopping at generated copy. These checks map to the current source, variant, localization, Content Builder, CloudPage, and handoff paths.
Prove the source path
Ask the team to create drafts from a URL, readable Knowledge item, Content Builder asset, local content record, and uploaded image, then verify source metadata or sourceTrail values are visible on the saved story.
Inspect variant persistence
Generate channel variants through POST /:id/variants and reload the content record to confirm variants are stored under the requested channel keys instead of only appearing in a chat reply.
Validate localization output
Run POST /:id/translate with target locale inputs and check that story translations preserve field structure and return translated metadata without claiming send approval.
Check folder-required writes
Attempt a Content Builder save without a folder ID, then with an account-configured or request-supplied folder ID, to prove SFMC writes are blocked until the destination is explicit.
Review CloudPage configuration
Load configured CloudPage templates, render against an approved template and slot, and confirm the workflow fails closed when account cloudPageTemplates are missing.
Confirm the handoff boundary
Use Content Builder save or sendToMC as a reviewed asset handoff, then keep send approval, CloudPage publication, and Journey activation inside Salesforce Marketing Cloud.
Technical evaluator FAQ
Where Content Agent helps, and where review remains.
The buyer lens is content production, not autonomous launch: Content Agent helps teams prepare reviewable assets and variants for SFMC workflows while Marketing Cloud approvals remain explicit.
Can Content Agent create content from existing SFMC assets?
Yes. The Content Builder source route can load an accessible Content Builder asset, convert it into a Content Agent draft, and preserve source metadata for review.
Can generated content be saved back to Salesforce Marketing Cloud?
Yes, when the account is authenticated and connected, and a valid Content Builder folder ID is supplied by request or account settings. The save path creates or patches Content Builder assets rather than launching sends.
How do channel variants work?
Content Agent can generate one or more requested channel variants from the saved story object, then persist each variant under its channel key with updated source metadata.
Does Content Agent publish CloudPages automatically?
No. It can render configured CloudPage templates and optionally save rendered HTML to Content Builder when requested. It does not claim automatic page publishing, send approval, or journey activation.
Enterprise guardrails
Content production stays source-aware and scoped.
Content Agent extends Campaign Builder's execution layer while keeping source attribution, Content Builder folder requirements, configured template boundaries, and account-scoped access visible.
Source trail and scope
Generated drafts carry source metadata and sourceTrail entries for URL, Knowledge, Content Builder, generated, or local content, while database reads stay account-scoped.
Folder-required SFMC writes
Content Builder saves reject missing or invalid folder IDs before creating or patching assets, keeping production-bound content out of unspecified SFMC locations.
Configured templates only
CloudPage preview and save flows render against account-configured templates and slots; no hidden default production template is used when configuration is missing.
Evaluation takeaway
Content Agent shortens SFMC content production without making launch claims.
A buyer evaluating Content Agent should expect grounded source imports, editable drafts, channel variants, field suggestions, localization metadata, Knowledge saves, Content Builder asset creation or patching, and CloudPage template preview paths. They should not expect it to approve sends, bypass folder configuration, publish unconfigured CloudPages, or activate journeys.