Use Workfront Fusion to convert a Workfront issue to a project that includes Adobe Experience Manager workflows

If you are creating a project through Workfront Fusion and want to include Adobe Experience Manager workflows on the project, you must use a specific Fusion module configuration, described in this article.

Workflows are available only in an Adobe Experience Manager as a Cloud Service integration. They are not available in integrations with Adobe Experience Manager Assets Essentials.

Access requirements

Expand to view access requirements for the functionality in this article.

You must have the following:

table 0-row-2 1-row-2 2-row-2 3-row-2 html-authored no-header
Adobe Workfront plan* Any
Adobe Workfront licenses* Request or higher

Adobe Experience Manager:

  • You must have Experience Manager Assets as a Cloud Service or Assets Essentials, and you must be added to the product as a user in the Admin Console.

  • You must have write access to the repository in Adobe Experience Manager.

Workfront Fusion:


  • Select or Prime Workfront Plan: Your organization must purchase Adobe Workfront Fusion.

  • Ultimate Workfront Plan: Workfront Fusion is included.


Current: Your organization must purchase Adobe Workfront Fusion.

Access level configurations*

Edit access to Documents

Note: If you still don't have access, ask your Workfront administrator if they set additional restrictions in your access level. For information on how a Workfront administrator can modify your access level, see Create or modify custom access levels.


Before you begin,

Module configuration

In Workfront Fusion, if you want to create a project that includes Adobe Experience Manager workflows, you must use the Workfront > Misc Action module.

  1. Add the Workfront > Misc Action module to your scenario.

  2. In the Connection field, select the Workfront connection that connects to the account this module will use.

    For instructions on creating a connection, see Connect Workfront to Workfront Fusion in the article Workfront modules.

    For instructions on creating the Client ID and Client Secret you will need to create a connection, see Create an OAuth application in this article.

  3. In the Record Type field, select Issue.

  4. In the Action field, select convertToProject.

  5. In the ID field, enter or map the ID of the issue that you are converting to a project.

  6. Enable Show advanced settings.

  7. Scroll to the bottom of the module and locate the Project (Advanced Collection) field.

  8. Paste the following text into the Project (Advanced Collection) field.

    code language-none
        "aemNativeFolderTreeIDs": ["Folder Tree ID here"],
        "aemNativeFolderWorkflowEnabled": "true",
        "name": "New project name here",
        "templateID": "Template ID here"
  9. Replace Folder tree ID here with the folder IDs.

    To locate folder tree IDs, see Locate folder tree IDs in this article.

    To use more than one folder tree, separate IDs with a comma:

    "aemNativeFolderTreeIDs": ["Folder tree ID here","Second folder tree ID here"],

  10. Replace New project name here with the name that the new project will have.

  11. Replace Template ID here with the ID of the template that you are using for the new project.

    You can map the template ID from a previous module (such as a Workfront > Search module) or locate it in the URL of the template’s page in Workfront.

  12. Click OK to save the module configuration.

Locate folder tree IDs

To locate the folder tree IDs:

These instructions use the Chrome browser.
  1. In Workfront, open the template that you want to use for this project. This template must include the Adobe Experience Manager configuration that you want to use for the project.

  2. Open the developer tools for your browser.

  3. Open the Network tab in the developer tools.

  4. In the Filter box, enter object-workflow.

  5. In the Name column, click on the alphanumeric ID that appears.

    Locating folder ID 1

  6. Click the Preview tab to the right of the alphanumeric ID.

  7. Open the following collapsed sections:

    1. data
    2. objectWorkflow
    3. workflows
    4. enhancedLinkedFolderCreationWorkflow
    5. enhancedLinkedFolderCreationWorkflowConfigurations

    Each folder tree is represented by a number. 0 (zero) represents the first folder in the list, 1 represents the second, and so on. If the template includes only one folder tree, it is number 0.

  8. Open the folder tree that you want to use for the new project. Make note of the _id field value. If you want to use more than one folder tree, make note of all of the _id field values for the folder trees you want to use.

    Locating folder ID 2

    These are the aemNativeFolderTreeIDs values that you will enter into the Project (Advanced Collection) field in the Workfront > Misc Actions Fusion module.

Create an OAuth application

You must set up an OAuth application in Workfront for this module’s connection. You only need to do this once for a given Workfront connection in Fusion.

  1. In Workfront, begin creating an OAuth application, as described in Create an OAuth2 application using user credentials (Authorization code flow) in the article Create OAuth2 applications for Workfront integrations.

  2. Copy the Client ID and Client Secret to a secure location.

  3. In the Redirect URIs field, enter the following:

    code language-none
  4. Click Save.

You will use this Client ID and Client secret when configuring the module’s connection in Fusion.

For instructions on creating a connection, see Connect Workfront to Workfront Fusion in the article Workfront modules.