PUBLISHED DATE: 2026-09-28 22:35:21

Workfront and AEM Assets Integration | Publicis Sapient

Sapient Slingshot wins Technology Breakthrough of the Year. Explore Slingshot

Sapient Bodhi ranked #1 for deep research. Explore Bodhi

Meet Sapient Sustain: context-aware AI for complex IT operations. Explore Sustain

3M lines of COBOL → clear specs in 8 weeks. Get the details

Workfront and AEM Assets (DAM) Integration

Connect Workfront and AEM Assets to move approved content into the DAM, sync metadata and reduce manual asset handling.

September 29, 2026

Meet the author

Vishwas Khamboj

Content Supply Chain Expert

How does the Workfront and AEM Assets integration work?
How do you send documents from Workfront to AEM Assets?
How is metadata kept in sync?
Native or enhanced connector: which should you use?
Native Workfront and AEM Assets integration
Workfront for AEM enhanced connector
When should you use Workfront Fusion?
How can Workfront automate marketing operations?
How Publicis Sapient helps

Generate AI Summary

Loading AI-generated summary...

Connect Creative Operations to Digital Asset Management

Integrating Adobe Workfront with Adobe Experience Manager Assets helps marketing and creative teams move approved content into the DAM without manual downloads, uploads or repeated metadata entry.

Teams can link AEM Assets content to Workfront, send completed documents from Workfront to AEM Assets and synchronize mapped metadata between the two platforms.

Creative teams can continue managing work in Workfront while DAM teams govern and distribute assets through AEM Assets.

How does the Workfront and AEM Assets integration work?

The integration connects creative work management in Workfront with digital asset management in AEM Assets.

Depending on the configuration, users can:

Browse and link approved AEM Assets content from Workfront
Create folders connected across Workfront and AEM Assets
Send completed documents and their metadata to AEM Assets
Update mapped metadata after an asset has been transferred
Manage asset versions without downloading and re-uploading files
Trigger additional workflows through Workfront Fusion

This reduces manual handoffs and gives both creative and DAM teams access to the information they need within their primary systems.

How do you send documents from Workfront to AEM Assets?

Users can send a Workfront document to a configured AEM Assets destination from the document area.

They select the AEM Assets integration, choose the destination folder and send the asset.

Mapped Workfront fields can be written to corresponding AEM metadata properties as part of the transfer.

For teams moving large volumes of approved content into a DAM, this can reduce repetitive metadata entry and create a more consistent handoff process.

How is metadata kept in sync?

Metadata synchronization helps information in AEM Assets remain aligned with changes made during the creative workflow.

Campaign names, usage information, brand classifications and other mapped values may change after an asset is first created.

With the appropriate integration and metadata mappings configured, updates in Workfront can be synchronized with the corresponding asset or folder metadata in AEM Assets.

The exact synchronization behaviour depends on:

Whether the native or enhanced integration is being used
Which Workfront object types are mapped
How asset and folder metadata schemas are configured
Whether object metadata synchronization is enabled
Which system is designated as the source for each field

Teams should define these rules before implementation to avoid conflicts, duplicated values or incomplete metadata.

Native or enhanced connector: which should you use?

The appropriate integration approach depends primarily on your AEM deployment model, business requirements, and the level of synchronization needed between Workfront and AEM.

Native Workfront and AEM Assets integration

The native integration is Adobe's recommended approach for new implementations with AEM Assets as a Cloud Service (AEMaaCS) and Assets Essentials.

It requires no connector installation and provides a simplified, cloud-first architecture.

It supports core capabilities such as:

Sending assets and metadata from Workfront to AEM Assets
Linking AEM assets to Workfront projects, tasks, and issues
Creating and managing connected folders
Asset versioning and version tracking
Real-time viewing of mapped AEM metadata within Workfront
Real-time updates of mapped Workfront metadata to AEM
Direct navigation to AEM repositories from Workfront
Support for multiple AEM repositories and multiple Workfront environments
Multiple AEM environments connected to a single Workfront environment

Organizations implementing a new integration with AEM Assets as a Cloud Service should evaluate the native integration first due to its simplified administration, cloud-native architecture, and Adobe's strategic direction.

Workfront for AEM enhanced connector

The AEM Enhanced Connector remains relevant for organizations using AEM 6.5, AEM Managed Services, or existing mature integrations that require advanced synchronization capabilities.

In addition to core asset linking and folder functionality, it provides:

Bi-directional metadata synchronization between Workfront and AEM
Comment synchronization between Workfront and AEM Assets
Workfront metadata mapping to AEM assets and folders
Automatic creation of document custom forms through AEM workflows
Automatic updating of AEM metadata from Workfront custom forms
Metadata synchronization during asset version updates
Automatically created project-linked folders based on configurable criteria
Advanced workflow automation and integration patterns
Publishing workflows to AEM publish environments and Brand Portal
Support for multiple AEM environments connected to a single Workfront environment

The enhanced connector must be deployed and configured through Adobe Professional Services or an Adobe-certified partner to remain supported.

Organizations already using it should assess their current capabilities and future cloud migration plans before changing their integration architecture.

When should you use Workfront Fusion?

Workfront Fusion extends the standard integration when a workflow requires additional transformation, orchestration or conditional logic.

Typical use cases include:

Transforming metadata before it is written to AEM Assets
Mapping values from multiple Workfront objects
Applying conditional synchronization rules
Triggering AEM workflows from Workfront events
Creating or updating assets through AEM APIs
Coordinating Workfront and AEM with other marketing systems
Managing exception handling and approval logic

A common enterprise pattern is to use the standard Workfront and AEM Assets integration for routine asset transfers and metadata synchronization, then use Workfront Fusion for processes that require custom rules or cross-platform orchestration.

How can Workfront automate marketing operations?

Adobe Workfront can serve as the operational layer connecting campaign planning, creative production, asset management, activation and reporting.

Large marketing organizations often use several platforms across this workflow, including:

Adobe Creative Cloud
Adobe Experience Manager
Adobe GenStudio
Marketing automation platforms
Jira
Microsoft Power BI
Salesforce
Tableau
Other enterprise marketing and data systems

Without integration, teams may rely on manual status updates, repeated data entry and disconnected approval processes.

These handoffs can slow campaign delivery and make it harder to track content from the original brief through production and activation.

Workfront integrations and Workfront Fusion can help automate these processes by moving information between systems, initiating workflows and keeping campaign data aligned.

How Publicis Sapient helps

Publicis Sapient helps organizations design and implement connected marketing operations using Adobe Workfront, AEM Assets, Workfront Fusion and related marketing technology platforms.

This work can include:

Assessing current campaign and content workflows
Defining Workfront and AEM integration architecture
Designing metadata and taxonomy mappings
Configuring standard connector workflows
Building custom Workfront Fusion automations
Connecting creative, DAM, activation and reporting systems
Establishing governance and operational support models

The objective is to reduce manual work, improve content flow and help marketing teams spend more time on planning, creativity and customer outcomes.

Meet our Adobe leaders

Dana Decker

Director, Business Development, Adobe Practice, North America

View Dana Decker's LinkedIn Profile

Phil Guilfoyle

Director, Business Development, Adobe Practice, International

View Phil Guilfoyle's LinkedIn Profile