Workfront to AEM as a Cloud Service: Asset & Metadata Synchronization

One of the interesting aspects of integrating Adobe Workfront with AEM as a Cloud Service using the native connector is designing the right metadata model and synchronization strategy.

For the implementation, I used Workfront Custom Forms to capture business-specific metadata that is not available through the standard Workfront fields.

Workfront allows custom forms to be attached to different objects, including Projects and Documents. This provides a flexible way to maintain metadata at different levels of the content hierarchy.

Project Custom Form → AEM Folder Metadata

The first custom form is attached to the Workfront Project.

The Project represents the business context and folder structure for the content. The custom form captures metadata that needs to be associated with the corresponding folder in AEM.

For example:

• Brand
• Business Unit
• Region
• Market
• Campaign
• Language
• Content Category
• Folder Description

The metadata captured at the Project level can then be mapped to the appropriate AEM folder metadata properties.

Document Custom Form → AEM Asset Metadata

The second custom form is attached to the Workfront Document.

This form captures metadata specific to the individual asset, such as:

• Asset Title
• Asset Description
• Asset Type
• Product
• Campaign
• Region
• Language
• Usage Rights
• Keywords
• Other business-specific attributes

The document-level fields are mapped to the corresponding AEM Asset metadata properties.

Metadata Mapping Strategy

The important part of the implementation is defining a clear mapping between the Workfront data model and the AEM metadata model.

A simplified mapping looks like this:

Workfront Project → Project Custom Form → Project-level metadata → Mapping → AEM Folder Metadata

Workfront Document → Document Custom Form → Asset-level metadata → Mapping → AEM Asset Metadata

For each field, the mapping needs to consider more than just the field name. Data type, allowed values, field purpose, and the corresponding AEM metadata property should all be considered.

For controlled fields such as Region, Market, Language, or Brand, maintaining consistent values between Workfront and AEM is particularly important. This helps avoid inconsistent metadata and improves search, filtering, reporting, and governance in AEM Assets.

Why Custom Forms Matter

The native Workfront–AEM connector provides the integration capability, but the metadata model is what makes the integration meaningful for the business.

Using custom forms allows us to extend the standard Workfront data model and capture information specific to the organization's content workflow.

The result is a more structured flow:

Project + Folder Metadata ↓ Workfront–AEM Connector ↓ AEM Folder

and

Document + Asset Metadata ↓ Workfront–AEM Connector ↓ AEM Asset

This approach reduces manual metadata entry, improves consistency, and creates a stronger connection between project management, creative production, and digital asset management.

The key takeaway: Before configuring the connector, design the metadata model and mapping between Workfront and AEM. A well-defined mapping strategy is critical to building a scalable and maintainable Workfront-to-AEM integration.