Skip to main content
Deepikakhanna
Level 2
Nov 3, 2026 7:41 AM UTC
Question

Workfront and Adobe journey integration

Hello, I need a help -

I am working on project enablement phase for one of our Banking Project in Discovery phase,

I got an urgent requirement to check on Adobe Workfront to AJO integration, build & deployments as per customer use case.
below I am multiple questions i need answer for that I am new to this AJO and not able to find the Correct Answer so i need help-

 

  • Can a campaign in AJO be initiated or created from a brief in Workfront?
  • Can Workfront retrieve the campaign proof / creative output so that reviewers can annotate and comment on it directly in the proofing workflow?
  • Can Workfront manage the approval workflow and, once approved, trigger the campaign validation or next step in AJO?

  • Can an approved Workfront brief automatically create a draft campaign shell in AJO, containing metadata only, through Fusion or a supported API? Audience, journey, and content creation are out of scope.

  • Can we store the Workfront reference ID in AJO and return the generated AJO campaign ID to Workfront, while preventing duplicate creation?

  • What we expect to be created in AJO: a draft campaign shell carrying the request metadata only. Candidate fields from the current intake form draft: campaign ID, campaign name, channel, brand (BNPP / Hello bank!), nature (commercial / regulatory), market, planned dates. Audiences stay in AEP and content comes later via AEM Assets, so both are out of scope.

  •  Cardinality: one Workfront request can cover several channels and/or both brands. We need to understand what is technically cleaner: one AJO campaign per request, or one per channel and/or per brand.

  • Return flow: only the AJO campaign ID written back into a Workfront field. Status updates and proofing sync are out of MVP scope, in line with the constraints you flagged.

3 replies

Community Advisor
Anuhya-YCommunity Advisor
Community Advisor
Nov 3, 2026 5:20 PM UTC

​@Deepikakhanna 

Please find the answers below.

  1. Can a Workfront brief create or initiate an AJO campaign?

    Neither the Fusion out-of-the-box AJO modules nor the AJO API offer campaign creation, so WF brief can't create AJO campaign automatically as of today.

  • Fusion AJO modules: https://experienceleague.adobe.com/en/docs/workfront-fusion/using/references/apps-and-their-modules/adobe-connectors/adobe-journey-optimizer-modules

  • AJO API: https://developer.adobe.com/journey-optimizer-apis/

  1. Can Workfront retrieve the campaign proof for annotation?

    AJO exposes a "Preview campaigns and send proofs" API, so Fusion may be able to fetch a rendered preview and attach it to a Workfront document for proofing. This can be done with the Fusion HTTP module calling the AJO API 

  • Fusion HTTP module: https://experienceleague.adobe.com/en/docs/workfront-fusion/using/references/apps-and-their-modules/universal-connectors/http-module-make-a-request

  • AJO create campaign preview API: https://developer.adobe.com/journey-optimizer-apis/references/simulations#operation/createCampaignPreview

  1. Can Workfront manage approval and trigger the next step in AJO?

    Workfront manages the approval workflow. Please see this Adobe Community blog on a Workfront, Fusion, AEP and AJO integration for campaign approvals:

    https://experienceleaguecommunities.adobe.com/adobe-journey-optimizer-15/accelerating-go-to-market-how-workfront-workfront-fusion-aep-and-ajo-integration-revolutionize-campaign-approvals-14677

  2. Can an approved brief auto-create a draft campaign shell (metadata only)?

    NO,The fallback is that, on approval, Fusion generates a structured "AJO setup task" in Workfront containing the metadata (campaign ID, name, channel, brand, nature, market, planned dates)

  3. Can we store the Workfront reference ID, return the AJO campaign ID, and prevent duplicates?

    Try this approach:

  • When the campaign is created in AJO, add the Workfront reference ID to the campaign name or description manually

  • Use the AJO "Retrieve campaigns" (getCampaigns) API from Fusion, iterate over the campaigns, find the one matching the Workfront reference ID, and store its campaign ID in a Workfront field.

    API reference: https://developer.adobe.com/journey-optimizer-apis/references/campaigns-retrieve#operation/getCampaigns

  1. What is expected to be created in AJO (draft campaign shell, metadata only) and cardinality?

    Please refer to the answers to questions 1 and 4:

  2. Return flow (AJO campaign ID only)

    Please refer to the answer to question 5.

Translate
DeepikakhannaAuthor
Level 2
Nov 4, 2026 7:06 AM UTC

Hello Anuhya-YCommunity Advisor,

Thanks a lot…

I have this use case any way i can do this can you please help me-

Once the brief is approved in Workfront, Workfront Fusion will send the approved brief metadata and required campaign details to AJO. The AJO team can then use these details to create and configure the appropriate campaign or journey in AJO. The resulting AJO Campaign/Journey ID can be sent back to Workfront to maintain the relationship between the two systems.

Translate
Community Advisor
Anuhya-YCommunity Advisor
Community Advisor
Nov 4, 2026 9:02 AM UTC

​@Deepikakhanna 

The integration is feasible, with one constraint to take into account: to my knowledge, neither Workfront Fusion nor the AJO API supports creating a campaign or journey in AJO. The process would therefore involve a structured handoff to the AJO team rather than a fully automated build.

Proposed approach

  1. Trigger: A Fusion scenario monitors the Workfront brief request and is triggered when its status changes to Approved.
  2. Data collection: Fusion retrieves the approved brief metadata and the required campaign details (for example, campaign ID, name, channel, brand, nature, market and planned dates).
  3. Handoff to the AJO team: Fusion sends this information to the AJO team, preferably through a Workfront task assigned to them with the details pre-filled, accompanied by an email or Teams notification.

  4. Campaign creation in AJO: The AJO team creates and configures the campaign or journey manually, referencing the Workfront campaign ID in its name or description or tag so that both records can be matched.

  5. Return of the identifier: The resulting AJO Campaign or Journey ID is recorded in a dedicated custom field on the Workfront request. In the initial release, the AJO team will enter this ID manually. In a later phase, Fusion can use the getCampaigns AJO API to identify the campaign whose name or tag contains the Workfront Campaign ID and automatically write the corresponding AJO Campaign/Journey ID back to the Workfront metadata field.

     

Translate
Terms & ConditionsAccessibility statement

Loading footer...