Adobe

Adobe Experience Manager (AEM) offers a central, powerful platform for managing and delivering digital content—especially large volumes of images, videos, and documents. The integrated Digital Asset Manager (DAM) allows media content to be efficiently organized, versioned, and delivered in a targeted manner. Access to assets can be controlled via user roles and workflows, enabling secure and controlled use – even without direct access to the backend system. AEM is ideal for companies that want to centrally manage consistent content across different channels. Thanks to comprehensive integration options, AEM can be flexibly integrated into existing system landscapes. This guide shows you step by step how to upload, manage, and deliver media in AEM for various applications.

Since June 2025, the transmission method currently used by Adobe's AEM has become obsolete. If necessary, we will adapt the connection option to newer methods.

Authentification

Until now, a bearer token has been used for the AEM upload node. This must be generated correctly before uploading an asset. A .json file is used for this purpose, which has the following form:

{
  "ok": true,
  "integration": {
    "imsEndpoint": "<IMS_ENDPOINT>",
    "metascopes": "<METASCOPES>",
    "technicalAccount": {
      "clientId": "<CLIENT_ID>",
      "clientSecret": "<CLIENT_SECRET>"
    },
    "email": "<EMAIL>",
    "id": "<ID>",
    "org": "<ORG>",
    "privateKey": "-----BEGIN RSA PRIVATE KEY-----\r\n<KEY>\r\n-----END RSA PRIVATE KEY-----\r\n",
    "publicKey": "-----BEGIN CERTIFICATE-----\r\n<KEY>\r\n-----END CERTIFICATE-----\r\n",
    "certificateExpirationDate": "<EXPIRATION_DATE>"
  },
  "statusCode": 200
}

Reference:
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/generating-access-tokens-for-server-side-apis

Documentation Adobe:
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/developer-reference-material-apis

Meta data

Documentation:
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/metadata-schemas#edit-metadata-schema-forms
(may open in a private window due to login))

For the metadata, the underlying JCR (Java Content Repository) key-value pairs must be provided to the upload node as metadata items. The metadata can also have user-defined values – so it always depends on how the AEM system was set up and which metadata schema is used.

There are also standard fields such as:

• dc:title for the title

  • “MyTitle”

• dc:subject for a description or subject

  • “MySubject”

Connection Parameter

Parameter	Type	Unit	Explanation	Example
Address	String		Defines the URL or endpoint of the AEM server (e.g., https://author-<AUTHOR-ID>.adobeaemcloud.com). This is used to establish the connection to the instance and enable access to assets or APIs.	https://author-<AUTHOR-ID>.adobeaemcloud.com
Jwt Credentials File	JSON-File FileStorageItem		The .json file containing the service credentials. Can be generated as an admin from the AEM system and must be provided in the workflow for generating a bearer token for authentication.
Target Folder	String		Specifies the path under which files are stored in AEM. The specification can be made without the prefix /content/dam/ – this is automatically added and validated internally.	My Subfolder
File Name	String		The name of the file as it should appear in AEM. Pay attention to the file extension! Depending on which file extension (.txt, .jpg, .bmp, etc.) is used, the file will be interpreted in the AEM system and displayed accordingly. Example: Uploading a .bmp image with the file name “testupload.txt” results in a PDF with cryptic characters being stored in the AEM system.	20250731_meinBild.jpg
Payload	Byte Array		Contains the digital content (e.g., images, PDFs, or videos) to be uploaded to AEM DAM. The data is transferred and processed as a byte array.	Image via “Image to JPG” node
Metadata Items	Metdata Items		The metadata for an AEM asset is generated separately. To do this, an array of key-value pairs can be generated using the Generate Metadata Items (Adobe) node, which is used as input in the Upload node. Individual, empty metadata items are not permitted and will result in an error during execution. However, it is not necessary to define metadata items overall. Documentation: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/metadata-schemas#edit-metadata-schema-forms	CODE Key: dc:title Value: MyTitle
Publish	Boolean		Specifies whether an uploaded asset should be published automatically after upload. When enabled, the asset is immediately made available for delivery in AEM. This means that data is forwarded from the author instance to the public instance.

Workflow Setup

Creating an AEM connection

1. In Workflows, go to Components to ➕.

2. Search for the component “AEM Connection (Adobe)” and select this entry.

3. A new component named “AEM Connection (Adobe)” appears. You can rename this component at any time by double-clicking on the component name.

4. Enter the connection parameters here. Upload the corresponding JSON file for authentication to File System and link it to the Jwt Credentials File.

5. In the Event Graph, open the context menu by right-clicking, search for “Get AEM Connection (Adobe)” and select this entry.

Congratulations—you have successfully created the component for AEM Connection (Adobe).

6. In the context menu of the workflow, search for “AEM Upload (Adobe)” and select this entry to add the node.

7. Enter the target folder and file name.

8. If metadata items are required, these can also be transferred.