A Workfront brief cannot be assumed to create an AJO campaign shell

A marketing team may want an approved Workfront brief to become a draft Adobe Journey Optimizer campaign automatically. A current Experience League discussion asks exactly where that handoff stops: approval, proofing, metadata, campaign ID, and duplicate prevention. A community advisor says the published Fusion modules and AJO API do not currently expose campaign creation. The public developer reference lists campaign retrieval, execution, preview, and monitoring, but no create-campaign operation in that catalog.

Fix the MVP contract

Define one Workfront request ID, owner, channel, brand, market, planned dates, and approval state. Decide whether one request yields one campaign or several by channel and brand before building an automation. A single ambiguous brief should not create multiple launch objects by accident. Record the approval timestamp and the exact metadata passed onward, then create a Workfront setup task for the AJO operator if campaign creation remains manual in your environment.

Keep the human step explicit

The AJO operator creates the draft campaign using the approved brief and puts the Workfront reference in a searchable field or agreed naming pattern. The operator returns the new AJO campaign ID to Workfront. Fusion can reconcile that ID through the documented retrieval API, but a name match alone is not a strong uniqueness guarantee. Require a single write-back field and flag multiple matches for review. Keep content, audience, and launch approval as separate gates.

Test proofing independently

The AJO reference includes preview and proof APIs. Prototype whether a rendered proof can be attached to a Workfront document in a way reviewers can actually annotate; the existence of a preview endpoint does not guarantee the full proofing workflow. Confirm access, expiry, versioning, and what happens after the creative changes. If Adobe adds a create-campaign API later, replace only the manual creation step while preserving approval and ID reconciliation.

Adovo’s view

Automation should make the handoff legible before it makes it fast. A brief, a campaign, and an approval are different records. Give each a stable identity and an accountable owner; then connect the parts that the platform actually supports.