Email Agent workflow
How Email Agent turns existing SFMC emails into reviewed updates.
Email Agent is Campaign Builder's workflow for reusing Salesforce Marketing Cloud email assets. It helps teams search, preview, copy, rewrite, translate, and update email drafts while keeping production-bound Content Builder changes confirmed and reviewable.
Email workflow
From reusable email asset to confirmed Content Builder update.
Email Agent fits teams that already have SFMC emails, templates, or campaign variants and need a safer way to repurpose them with previewed changes instead of untracked manual editing.
Find existing SFMC emails
Email Agent searches accessible Marketing Cloud email assets through the email-agent route family and related Marketing Cloud email lookup APIs before production edits are considered.
Preview the reviewable fields
Preview helpers fetch subjectline, preheader, HTML content, template metadata, slot payloads, and folder path context when those fields are available to the connected account.
Rewrite, translate, or copy
Teams can generate rewrite or translation drafts, copy existing emails, or prepare copy-and-update flows for safer reuse instead of starting from a blank Content Builder asset.
Apply only after confirmation
Subjectline, preheader, HTML, slot updates, copy, rewrite application, and translation application are production write skills with confirmation and Bruno pending-action previews.
Implementation map
What evaluators can trace to Email Agent routes.
The Email Agent surface is concrete: search, preview, template lookup, folder-path resolution, copy, update, slot update, rewrite, translation, context, and feedback are exposed as separate reviewable routes or skills.
Email Agent is mounted under /api/v1/emails/* and /api/v1/agent/email/* behind the agent:email-agent entitlement.
GET /api/v1/marketingcloud/getEmails and GET /api/v1/marketingcloud/getEmailById/:id provide related search and preview surfaces for Marketing Cloud email assets.
Read skills include email.search, email.get, email.preview, email.template.get, email.folderPath, email.chat, and email.context.list.
Write skills include email.copy, email.update, email.updateSlots, email.copyAndUpdate, email.rewrite, and email.translate with confirmation required for SFMC-facing changes.
Preview-safe fields include id, name, subjectline, preheader, HTML content, slots, template metadata, and folder path details when available.
Production write summaries identify the action, source and target email IDs, changed fields, slot usage, and SFMC requirement status without exposing full raw HTML.
Confirmed-write lifecycle
How an email change moves from preview to reviewed SFMC asset.
The implementation gives evaluators a concrete sequence to inspect: identify an existing email, preview the fields, choose a scoped write skill, review the Bruno pending-action summary, then confirm the Content Builder change.
Start with an existing asset
Search and preview routes establish the source email, template metadata, folder context, subjectline, preheader, HTML, and slot payloads before a write skill is proposed.
Choose the safest mutation
Email Agent separates copy, direct header or HTML update, slot payload update, copy-and-update, rewrite application, and translation application instead of hiding every change behind one opaque publish action.
Show Bruno what will change
Production write skills return previewSummary data for pending actions, including action name, source and target email IDs, changed fields, slot usage, and whether SFMC credentials are required.
Keep launch outside the agent
Confirmed write paths can create or update Content Builder email assets, but send approval, campaign send, and Journey activation remain explicit Salesforce Marketing Cloud review steps.
Readiness gates
What must be available before email work can reach SFMC.
Email Agent can only support production email work when entitlements, SFMC credentials, accessible assets, and transformable source fields match the requested action.
The account must have the agent:email-agent entitlement before Email Agent search, chat, preview, or write workflows are available.
Most executable SFMC email skills require connected Marketing Cloud credentials for the current account or user context.
Preview and update operations require an accessible Content Builder email asset ID or legacy email ID in the connected business unit.
Slot-aware updates depend on template slot data being present in the source email or template preview payload.
Rewrite and translation drafts depend on configured OpenAI model credentials and enough source content in subjectline, preheader, HTML, or slots.
Technical evaluator FAQ
Where Email Agent helps, and where SFMC review remains.
The safest evaluation lens is email asset production: Email Agent helps prepare controlled updates while final campaign sends and journey activation stay outside the workflow.
Can Email Agent reuse existing SFMC emails?
Yes. It can search, preview, copy, rewrite, translate, and update accessible SFMC email assets through the email-agent route family and related Marketing Cloud lookup routes.
What fields can Email Agent update?
Implemented write paths cover subjectline, preheader, HTML content, slot payloads, copy-and-update flows, rewrite application, and translation application when the connected account has access.
How are template slots handled?
When slot payloads are available, Email Agent can transform slot content and apply updates with email.updateSlots while preserving template structure instead of flattening every email into raw HTML.
Does Email Agent send emails or activate journeys?
No. It supports reviewed email asset production. Final sends, approvals, and Journey activation remain Salesforce Marketing Cloud steps.
Enterprise guardrails
Email production stays scoped and reviewable.
Email Agent extends Campaign Builder's SFMC execution layer, but it keeps entitlement checks, Marketing Cloud scope, token-preserving transformations, and confirmed write boundaries explicit.
Entitlement and SFMC scope
Email Agent routes run under authenticated account context, email-agent entitlement checks, and the connected Marketing Cloud account or user context before SFMC email assets are read or changed.
Token-preserving transforms
Translation instructions preserve URLs, AMPscript and personalization tokens, placeholders, punctuation, whitespace, and HTML structure so localized emails stay reviewable inside SFMC.
Confirmed write boundary
Email Agent can prepare and apply confirmed email changes, but it does not send campaigns, approve creative, or activate Journey Builder journeys.
Evaluation takeaway
Email Agent shortens SFMC email reuse without hiding Content Builder changes.
A buyer evaluating Email Agent should expect search, preview, copy, rewrite, translation, slot-aware update support, and Bruno-compatible preview summaries. They should not expect it to approve sends, bypass SFMC permissions, or activate journeys.