Seeking Insights on Integrating Adobe Workfront and Adobe AEM Assets with Pega Products

[Mike_CBA]

I'm reaching out to this amazing community to see if anyone has experience integrating Workfront and AEM Assets with any of the Pega products, particularly Pega's Next Best Action Designer (NBAD).

We're starting to explore ways to streamline our marketing operations and enhance our customer engagement strategies by leveraging the capabilities of both Adobe and Pega platforms.

We're particularly interested in understanding the following:

1. Integration Best Practices: What are the best practices for integrating Adobe Workfront and Adobe AEM Assets with Pega NBAD?
2. Technical Challenges: What technical challenges did you encounter during the integration process, and how did you overcome them?
3. Use Cases: Are there any specific use cases or success stories you can share where this integration significantly improved your marketing or customer engagement outcomes?
4. Tools and Resources: What tools, resources, or documentation were most helpful during the integration process?

Any insights, experiences, or recommendations you can share would be greatly appreciated. Looking forward to learning from this community and exchanging ideas!

Thanks in advance for your help! Mike 

[monicacardoso]

Hi @Mike_CBA, 

Thank you for your question! I personally haven't experimented with these processes, but I discussed it with our internal teams.

Integration Best Practices:

1) Workfront REST API: Use it to pull campaign briefs, task statuses, or asset metadata

2) AEM Assets API (or GraphQL for Assets): Use to push/pull assets or metadata

3) Pega API: Leverage Pega’s DX API or connectors to ingest data or trigger NBAD logic

Technical Challenges: 

Potential Challenge	Solution
Workfront doesn’t “push” data natively	Use Fusion or webhooks to monitor and push updates
Pega’s NBAD expects highly contextualized inputs	Build transformation logic in Fusion or middleware
Asset metadata mapping between AEM and Pega	Standardize tagging and taxonomy; use shared metadata profiles
Real-time orchestration	Consider async updates with IDs/tokens to link across platforms

Use Cases:

1) Campaign Brief to Action

• Marketers submit a campaign brief in Workfront
• Fusion sends metadata and tasks to Pega NBAD to personalize offers
• AEM assets selected in Workfront feed directly into Pega campaigns

2) Asset Approval → Dynamic Offer

• Final assets approved in Workfront/AEM
• Once approved, metadata and asset paths are passed to Pega
• Pega auto-publishes or selects assets for the next best action via defined strategies

Tools and Resources:

• Adobe Workfront Fusion - For orchestrating Workfront and AEM
• Pega Integration Designer/API Explorer
• Adobe I/O/AEM GraphQL API - For interacting with AEM programmatically
• Postman/Insomnia - Test API payloads across systems
• Data mapping spreadsheets - For aligning object fields and metadata

- Monica