Journey Agent workflow
How Journey Agent turns campaign briefs into reviewed Journey Builder drafts.
Journey Agent is Campaign Builder's workflow for planning, reviewing, and creating Salesforce Marketing Cloud Journey Builder drafts. It can work from chat, uploaded briefs, scoped knowledge, existing journeys, planned email copy, and audience handoffs while keeping activation manual in SFMC.
Journey workflow
From brief to draft Journey Builder structure.
Journey Agent is useful when a team needs to turn campaign intent into a reviewed journey plan, email sequence, audience setup path, and draft journey without forcing marketers to know SFMC object IDs.
Start from chat or a brief
Journey Agent accepts business-language requests and uploaded PDF or .docx briefs through /chat and /chat/stream, then normalizes journeyInfo, chat history, uploaded metadata, and readiness state.
Build the canonical plan
The tool loop can extract the brief, search scoped knowledge, set or revise the canonical journeyDraftPlan, draft email copy, and check readiness before any draft creation step is available.
Reuse existing journeys when useful
Reference flows search or fetch recent SFMC journeys so users can clone by business context instead of pasting Journey Builder IDs into the chat.
Create drafts after review
Approved workflows can create Journey Builder drafts from scratch or from a selected template/reference journey, then surface warnings such as missing EMAILV2 legacy IDs or entry-event setup issues.
Implementation map
What evaluators can trace to Journey Agent and SFMC routes.
The Journey Agent surface is not a generic chat promise. It is backed by route families for stateful journey planning, workflow gates, SFMC lookup, draft creation, and Bruno orchestration.
Journey Agent is mounted under /api/v1/journey/* and /api/v1/agent/journey/* behind authentication and the agent:journey-agent entitlement.
POST /chat and POST /chat/stream return reply, question, quickReplies, journeyInfo, activationReadiness, blueprintReadiness, preview, and workflow state.
Workflow endpoints cover progress lookup, blueprint approval, email asset building, audience resolution, deterministic verification, settings, blueprint documents, creation, and created-state marking.
Marketing Cloud routes support getJourneys, getJourneyById, searchJourneys, recentJourneys, getJourneyTemplates, createJourneyFromTemplate, createJourneyFromScratch, and journey summaries.
Audience handoffs remain separate: Audience Agent owns entry-audience and data-contract planning before Journey Agent or Factory work continues.
Journey execution can be orchestrated by Bruno through execute-campaign and run lookup routes when the account is entitled and the run is confirmed.
Readiness model
Draft creation is gated by concrete blockers and warnings.
Journey Agent evaluates the plan before creation so teams can see whether they are blocked by missing names, unresolved decisions, incomplete email content, missing source journeys, or manual activation warnings.
A new journey name is required before draft creation can proceed.
Create mode needs a current journeyDraftPlan with goal, audience, and planned email structure.
Open decisions block creation until the user resolves the missing business choices.
Planned emails must include timing, message or role, CTA, subject, preheader, and body HTML before readiness can clear.
Clone mode requires a selected source journey, and missing or unknown source entry events are surfaced as warnings.
Every readiness result includes manualActivationRequired because Journey activation stays inside Salesforce Marketing Cloud.
Workflow gates
The newer Journey workflow separates review, artifact build, verification, and creation.
Technical evaluators can inspect the Journey workflow as a staged contract, not just one chat response. The implementation keeps blueprint approval, email asset creation, audience resolution, journey settings, deterministic verification, draft creation, and created-state marking as distinct route-backed phases.
Approve the blueprint first
The /workflow/approve-blueprint route evaluates business readiness, freezes the reviewed plan when blockers are clear, and returns 409 without spawning artifact threads when the blueprint is not ready.
Build email and audience artifacts separately
Dedicated /workflow/build-emails and /workflow/resolve-audience steps materialize SFMC email assets and entry-source context before Journey Agent attempts to create the Journey Builder draft.
Record settings and blueprint evidence
The workflow settings and blueprint-document routes persist entry mode, contact data needs, email field choices, and a downloadable blueprint document for review before or after creation.
Verify before any create call
The deterministic verifier blocks creation when journey name, email assets, or entry source are missing, while surfacing EMAIL_LEGACY_ID_MISSING, ENTRY_SOURCE_MANUAL, and manual activation as warnings.
Create only reviewed drafts
The /workflow/create path re-runs verification, creates the draft through the proven SFMC journey creation path, records the audit trail, and leaves activation to Salesforce Marketing Cloud.
Post-create review
Created Journey drafts still expose SFMC follow-up work.
Journey Agent does not treat a successful SFMC create response as launch completion. It carries activationReadiness and clone artifact warnings forward so technical evaluators can see the exact manual checks that remain inside Journey Builder.
Created as Draft is the success state
After a successful create response, the UI marks the journey Created as Draft and keeps the readiness panel focused on blockers, warnings, and manual activation instead of calling the journey production-ready.
Clone artifacts carry manual fix-up notes
Marketing Cloud create responses can include cloneArtifacts.warnings. Journey Agent surfaces those warnings in chat so the team sees which SFMC pieces still need manual review.
EMAIL_LEGACY_ID_MISSING stays visible
When SFMC creates a Content Builder email asset but does not return the legacy numeric ID required by an EMAILV2 activity, the warning tells reviewers to select the email manually in Journey Builder.
ENTRY_EVENT_CREATE_FAILED blocks silent launch assumptions
If entry event creation fails, the draft can still exist, but the team is told to wire the entry source manually before any Salesforce Marketing Cloud activation review.
Technical evaluator FAQ
Where Journey Agent helps, and where SFMC review remains.
The safest evaluation lens is reviewed draft production: Journey Agent can prepare the Journey Builder structure and related artifacts, but final activation remains a Marketing Cloud operator decision.
Can Journey Agent create a journey from a short brief?
Yes. The implemented chat flow can extract a brief, create or revise a journeyDraftPlan, draft planned email copy, check readiness, and expose draft creation only after required fields and review gates are clear.
Can it clone an existing Journey Builder journey?
Yes. Reference flows search and fetch accessible SFMC journeys, preserve the selected source journey internally, and create a new draft from the selected reference when the user confirms.
Does Journey Agent create the audience and email artifacts too?
The newer workflow surface includes email asset building and audience resolution steps, while Audience Agent still owns entry-audience and data-contract planning. Those artifacts are reviewed before Journey creation proceeds.
Does it activate journeys automatically?
No. The readiness model always carries manualActivationRequired, and created journeys remain Drafts that teams review and activate manually inside Salesforce Marketing Cloud.
Enterprise guardrails
Journey execution stays scoped, verified, and reviewable.
Journey Agent extends Campaign Builder's SFMC execution layer with entitlement checks, scoped credentials, workflow verification, and visible activation boundaries before draft creation touches Marketing Cloud.
Authenticated journey scope
Journey APIs run under authenticated account, user, workspace, and Marketing Cloud credential context before route handlers can read workflow state or call SFMC.
Draft creation boundary
Journey Agent creates or clones Journey Builder drafts for review. It does not activate, publish, approve sends, or label a draft as production-ready.
Verification before SFMC writes
Workflow create calls run the deterministic verifier first; blocked verification returns a conflict and no SFMC write is performed.
Evaluation takeaway
Journey Agent reduces Journey Builder setup work without hiding activation risk.
A buyer evaluating Journey Agent should expect brief extraction, scoped knowledge grounding, reference journey search, blueprint approval, email and audience artifact preparation, deterministic verification, reviewed draft creation, and downloadable blueprint evidence. They should not expect automatic activation, send approval, or unrestricted SFMC writes.