Adobe Workfront modules

Last update: August 24, 2026

Topics:
APIs
Integrations

IMPORTANT

This article contains instructions for the new version of the Workfront connector, released on October 22, 2025. This new connector reflects changes made to the Workfront API.

The new connector is labeled as “Workfront,” and the previously available connector is labeled as “Workfront (Legacy).”

We recommend:

Using the new connector when creating or updating a scenario.
Upgrading existing modules to the new connector.

The legacy Workfront connector uses Workfront API version 20, which is scheduled to be deprecated with the 28.4 release (April 2028). Modules in the legacy connector will continue to work until that time.

For instructions on upgrading existing modules, see Upgrade a Workfront module to a new version in the article Upgrade a module to a new version.

For information on why a new connector is sometimes necessary, see Overview of APIs in Fusion.

You can use the Adobe Workfront Fusion Adobe Workfront connector to automate your processes within Workfront. You can also connect Workfront to other applications and services.

For instructions on creating a scenario, see the articles under Create scenarios: article index. For information about modules, see the articles under Modules: article index.

Access requirements

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

table 0-row-2 1-row-2 2-row-2 layout-auto html-authored no-header

Adobe Workfront package

Any Adobe Workfront Workflow package and any Adobe Workfront Automation and Integration package

Workfront Ultimate

Workfront Prime and Select packages, with an additional purchase of Workfront Fusion.

Adobe Workfront licenses

Standard

Work or higher

Product

If your organization has a Select or Prime Workfront package that does not include Workfront Automation and Integration, your organization must purchase Adobe Workfront Fusion.

For more detail about the information in this table, see Access requirements in documentation.

Connect Workfront to Workfront Fusion

The Workfront connector uses OAuth 2.0 to connect to Workfront.

You can create a connection to your Workfront account directly from inside a Workfront Fusion module.

Connect to Workfront using Client ID and Client secret
Connect to Workfront using a Server-to-Server connection

Connect to Workfront using Client ID and Client secret

In any Adobe Workfront module, click Add next to the Connection field.

Fill in the following fields:

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 layout-auto html-authored no-header
Connection type	Select Adobe Workfront auth connection.
Connection name	Enter a name for the new connection.
Client ID	Enter your Workfront Client ID. This can be found in the OAuth2 Applications area of the Setup area in Workfront. Open the specific application you are connecting to to see the Client ID.
Client Secret	Enter your Workfront Client secret. This can be found in the OAuth2 Applications area of the Setup area in Workfront. If you do not have a Client Secret for your OAuth2 application in Workfront, you can generate another. For instructions, see the Workfront documentation.
Authentication URL	This can remain the default value, or you can enter the URL of your Workfront instance, followed by `/integrations/oauth2`. Example: `https://mydomain.my.workfront.com/integrations/oauth2`
Host prefix	In most cases, this value should be `origin`.

Click Continue to save the connection and return to the module.

If you are not logged in to Workfront, you are directed to a login screen. After you log in, you can allow the connection.

NOTE

OAuth 2.0 connections to the Workfront API no longer rely on API keys.
To create a connection to a Workfront Sandbox environment, you must create an OAuth2 application in that environment, and then use the Client ID and Client Secret generated by that application in your connection.

Connect to Workfront using a Server-to-Server connection

In any Adobe Workfront module, click Add next to the Connection field.

Fill in the following fields:

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 6-row-2 7-row-2 layout-auto html-authored no-header
Connection type	Select Adobe Workfront Server-to-Server connection.
Connection name	Enter a name for the new connection.
Instance name	Enter the name of your instance, also known as your domain. Example: if your URL is `https://example.my.workfront.com`, enter `example`.
Instance lane	Enter the environment type that this connection will connect to. Example: if your URL is `https://example.my.workfront.com`, enter `my`.
Client ID	Enter your Workfront Client ID. This can be found in the OAuth2 Applications area of the Setup area in Workfront. Open the specific application you are connecting to to see the Client ID.
Client Secret	Enter your Workfront Client secret. This can be found in the OAuth2 Applications area of the Setup area in Workfront. If you do not have a Client Secret for your OAuth2 application in Workfront, you can generate another. For instructions, see the Workfront documentation.
Scopes	Enter any applicable scopes for this connection.
Host prefix	In most cases, this value should be `origin`.

Click Continue to save the connection and return to the module.

If you are not logged in to Workfront, you are directed to a login screen. After you log in, you can allow the connection.

NOTE

OAuth 2.0 connections to the Workfront API no longer rely on API keys.
To create a connection to a Workfront Sandbox environment, you must create an OAuth2 application in that environment, and then use the Client ID and Client Secret generated by that application in your connection.

Workfront modules and their fields

When you configure Workfront modules, Workfront Fusion displays the fields listed below. Along with these, additional Workfront fields might display, depending on factors such as your access level in the app or service. A bolded title in a module indicates a required field.

If you see the map button above a field or function, you can use it to set variables and functions for that field. For more information, see Map information from one module to another.

Map toggle

NOTE

If you do not see the most up-to-date fields in a Workfront module, this may be because of caching issues. Wait one hour and try again.
HTTP 429 status codes from Adobe Workfront should not cause deactivations, but instead trigger a short execution pause in the scenario.

Triggers
Actions
Searches

Watch Events

This trigger module executes a scenario in real time when objects of a specific type are added, updated, or deleted in Workfront.

The module displays all event subscriptions related to the webhook. This includes event subscriptions created through Fusion as well as event subscriptions created directly through the API. This event subscription view is not available in the legacy version of the Watch Events module.

The module returns any standard fields associated with the record, along with any custom fields and values that the connection accesses. You can map this information in subsequent modules in the scenario.

IMPORTANT

You can edit this module later, which will edit the webhook.

Consider the following when updating a webhook:

The edited webhook is treated by Workfront event subscriptions as a new subscription. Event subscription history is not preserved for the previous webhook configuration, because that is considered a separate event subscription.
The switch from old to new event subscription may not be perfectly synchronized. It is therefore possible to receive an event twice (if the new subscription begins running before the old one stops) or to miss an event (if the old subscription stops before the new one begins running).

For more information on editing webhooks, see Edit webhooks.

Click Add to the right of the Webhook box.

Configure the webhook in the Add a hook box that displays.

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 6-row-2 7-row-2 layout-auto html-authored no-header
Webhook name	Enter a name for the webhook
Connection	For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.
Record Type	Select the type of Workfront record that you want the module to watch.
State	Select whether you want to watch the old state or the new state. New state Trigger a scenario when the record changes to a given value. For example, if the state is set to New State and the filter is set to Status Equals In Progress, the webhook triggers a scenario when the Status changes to In Progress, regardless of what the status was before. Old state Trigger a scenario when the record changes from a given value. For example, if the state is set to Old State and the filter is set to Status Equals In Progress, the webhook triggers a scenario when a Status that is currently In Progress changes to another status.
Events filters	You can set filters to watch for only records that meet criteria you select. For each filter, enter the field you want the filter to evaluate, the operator, and the value that you want the filter to allow. You can use more than one filter by adding AND rules. NOTE: You cannot edit filters in existing Workfront webhooks. To set up different filters for Workfront event subscriptions, remove the current webhook and create a new one. For more information on event filters, see Event subscription filters in the Workfront > Watch Events modules in this article.
Exclude events made by this connection	Enable this option to exclude events created or updated using the same connector that this trigger module uses. This can prevent situations where a scenario might trigger itself, causing it to repeat in an endless loop. NOTE: The Assignment record type does not include this option.
Record Origin	Choose whether you want the scenario to watch New Records Only, Updated Records Only, New and Updated Records, or Deleted Records Only. NOTE: If you choose New and Updated Records, the webhook creation creates 2 event subscriptions (for the same webhook address).
Enable secured hooks	Choose whether you want to enable authToken-based security for this webhook. NOTE: As of August 23, 2026, Fusion enables authToken-based security by default for all Workfront > Watch Event modules, including existing ones. If a specific webhook breaks or you need to disable this for compatibility reasons, you can turn off the Enable secured hooks option.

After the webhook is created, you can view the address of the endpoint that events are sent to.

For more information, see the section Examples of Event Payloads in the article Event Subscription API in the Workfront documentation.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

Watch Field

This trigger module executes a scenario when a field that you specify is updated. The module returns both the old and the new value of the specified field. You can map this information in subsequent modules in the scenario.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Record Type

Select the type of Workfront record that you want the module to watch.

For example, select Task if you want to start executing the scenario each time a record field is updated in a task.

Field

Select the field that you want the module to watch for updates. These fields reflect the fields that your Workfront administrator has set up for tracking.

Outputs

Select the object fields that you want included in the output bundle for this module.

Limit

Enter or map the maximum number of records you want the module to return during each scenario execution cycle.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

Watch Record

This trigger module executes a scenario when objects of a specific type are added, updated, or both. The module returns all standard fields associated with the record or records, along with any custom fields and values that the connection accesses. You can map this information in subsequent modules in the scenario.

In the output, the module indicates whether each record is new or updated.

Records that were both added and updated since the last time the scenario ran are returned as new records.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Filter

Choose whether you want the scenario to watch New Records Only, Updated Records Only, or New and Updated Records.

Record Type

Select the type of Workfront record that you want the module to watch.

For example, if you want to start the scenario each time a new Project is created, select Project

Outputs

Select the fields that you want included in the output bundle for this module.

Reference

Select the reference fields that you want included in the output bundle for this module.

Outputs

Select the collection fields that you want included in the output bundle for this module.

Optional Filter

(Advanced) Type an API code string to define any additional parameters or code that will refine your criteria.

Limit

Enter or map the maximum number of records you want the module to return during each scenario execution cycle.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

Actions

Convert object
Create a record
Custom API Call
Delete Record
Download Document
Get a presigned file URL
Misc Action
Read a Record
Update Events Payload Version
Update a record
Upload Document

Convert object

This action module makes one of the following conversions:

Convert Issue to Project
Convert Issue to Task
Convert Task to Project

NOTE

As of July 2024, custom forms can be included when converting an object.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Object type

Select the type of object that you want to convert. This is the type that the object has before the conversion.

Convert to

Select the object that you want to convert it to. This is the type that the object has after the conversion.

<Object> ID

Enter the object's ID.

Note: When entering the ID of an object, you can begin typing the name of the object, then select it from the list. The module then enters the appropriate ID into the field.

Template ID

If you are converting to a project, select the Template ID that you want to use for the project.

Note: When entering the ID of an object, you can begin typing the name of the object, then select it from the list. The module then enters the appropriate ID into the field.

Custom forms

Select any custom forms that you want to add to the newly converted object, then enter values for the custom form's fields.

Options

Enable any options you want when converting the object. Options are available depending on which object you are converting to or from.

Copy native fields

Enable this option to copy any native fields from the original object to the new object.

Copy custom forms

Enable this option to copy any native fields from the original object to the new object.

Create a record

This action module creates an object, such as a project, task, or issue in Workfront, and allows you to add a custom form to the new object. The module allows you to select which of the object’s fields are available in the module.

You specify the ID of the record.

The module returns the ID of the record and any associated fields, along with any custom fields and values that the connection accesses. You can map this information in subsequent modules in the scenario.

Make sure you provide the minimum number of input fields. For example, if you want to create an issue, you need to provide a valid parent project ID in the Project ID field to indicate where the issue should live in Workfront. You can use the mapping panel to map this information from another module in your scenario, or you can enter it manually by typing in the name and then selecting it from the list.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Record Type

Select the type of Workfront record that you want the module to create.

For example, if you want to create a Project, select Project from the dropdown list.

Select fields to map

Select the fields that you want available for data input. This allows you to use these fields without having to scroll through the ones you don't need. You can then enter or map data into these fields.

For fields in custom forms, use the Attach Custom Form field.

Attach Custom Form

Select any custom forms that you want to add to the new object, select the fields that you want to enter values for, then enter or map values for those fields.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

NOTE

When entering the ID of an object, you can begin typing the name of the object, then select it from the list. The module then enters the appropriate ID into the field.
When entering the text for a custom field or a Note object (Comment or reply), you can use HTML tags in the Note Text field to create rich text, such as bold or italic text.

NOTE

Users are created in Deactivated and Pending Approval status. If your organization has been migrated to the Adobe Admin Console, and the Pending Approval badge is not removed within a few minutes, you can approve the user.

Resolve individual users

You can resolve individual users in the Users list.
1. Select the user or users in the Users list.
2. Click the three-dot menu in the list header.
3. Select Approve.
4. After a few minutes, refresh the page.
Resolve users added in a large batch

To resolve users that were added in a large batch, you can add the batch of users to the Adobe Admin Console directly.

For instructions, see Manage multiple users | Bulk CSV upload in the Adobe documentation.

Custom API Call

This action module lets you make a custom authenticated call to the Workfront API. This way, you can create a data flow automation that can’t be accomplished by the other Workfront modules.

The module returns the following information:

Status Code (number): This indicates the success or failure of your HTTP request. These are standard codes that you can look up on the internet.
Headers (object): A more detailed context for the response/status code that doesn’t relate to the output body. Not all headers that appear in a response header are response headers, so some might not be useful to you.

The response headers depend on the HTTP request you chose when configuring the module.
Body (object): Depending on the HTTP request you chose when configuring the module, you may receive some data back. That data, such as the data from a GET request, is contained in this object.

You can map this information in subsequent modules in the scenario.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

URL

Enter a path relative to https://<WORKFRONT_DOMAIN>/attask/api/<API_VERSION>/.

API Version

Select the version of the Workfront API that you want the module to use.

Method

Select the HTTP request method you need to configure the API call. For more information, see HTTP request methods in Adobe Workfront Fusion.

Headers

Add the headers of the request in the form of a standard JSON object. This determines the content type of the request.

For example, {"Content-type":"application/json"}

Note: If you're getting errors and it's difficult to determine their origin, consider modifying headers based on the Workfront documentation. If your Custom API Call returns a 422 HTTP Request Error, try using a "Content-Type":"text/plain" header.

Query String

Add the query for the API call in the form of a standard JSON object.

For example: {"name":"something-urgent"}

Tip: We recommend that you send information through the JSON body rather than as query parameters.

Body

Add the body content for the API call in the form of a standard JSON object.

Note:

When using conditional statements such as if in your JSON, put the quotation marks outside of the conditional statement.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

Delete Record

This action module deletes an object, such as a project, task, or issue in Workfront.

You specify the ID of the record.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Force delete

Enable this option to ensure that the record is deleted, even if the Workfront UI would request confirmation of the deletion.

Async delete

Enable this option to allow the module to delete asynchronously.

Enter the unique Workfront ID of the record that you want the module to delete.

To get the ID, open the Workfront object in your browser and copy the text at the end of the URL after "ID=." For example: https://my.workfront.com/project/view?ID=5e43010c03286a2a555e1d0a75d6a86e

Record Type

Select the type of Workfront record that you want the module to delete.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

NOTE

We recommend the following scenario configuration to avoid the possibility of records not being deleted due to asynchronous operations.

Delete the record synchronously.
Add error handling to the Delete Record module to Ignore the error caused by the 40 second timeout.

Download Document

This action module downloads a document from Workfront.

You specify the ID of the record.

The module returns the document’s content, filename, file extension, and file size. You can map this information in subsequent modules in the scenario.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Document ID

Map or manually enter the unique Workfront ID of the document that you want the module to download.

To get the ID, open the Workfront object in your browser and copy the text at the end of the URL after "ID=." For example: https://my.workfront.com/project/view?ID=5e43010c03286a2a555e1d0a75d6a86e

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

Get a presigned file URL

This action module gets presigned file URLs that can later be used by other APIs.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Document ID

Map or manually enter the unique Workfront ID of the document that you want to get a presigned URL for.

To get the ID, open the Workfront object in your browser and copy the text at the end of the URL after "ID=." For example: https://my.workfront.com/project/view?ID=5e43010c03286a2a555e1d0a75d6a86e

Time to URL expiration

Enter or map the number of minutes that this URL will exist before it expires. The default is 1 minute.

To change this value, you must have this parameter enabled by the Workfront Fusion team. If it is not enabled, the value will remain 1 minute regardless of the number you enter.

Misc Action

This action module lets you perform actions against the API.

NOTE

As of July 2024, the convertToProject action includes the field copyCategories. When set to TRUE, any custom forms will be included in the project that the issue is converted to.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Record Type

Select the type of Workfront record that you want the module to interact with.

Action

Select the action you want the module to perform.

You may need to fill out additional fields, depending on the Record Type and Action you choose. Some combinations of these two settings may require only a record ID, while others (such as Project for the Record Type and Attach Template for the Action) require additional information (such as an Object ID and a Template ID).

For options available to some actions, see Misc action options in this article.

For details about individual fields, see the Workfront developer documentation.

Note: The developer documentation site includes information only through API version 14, but still contains valuable information for API calls.

Select the record type from the left navigation on the Workfront developer documentation page. The following types have their own pages:
- Projects
- Tasks
- Issues
- Users
- Documents
For all other record types, select Other objects and endpoints, and locate the record type on the alphabetically sorted pages.
On the page of the appropriate record type, search (Ctrl-F or Cmd-F) for the action.
View descriptions for available fields under the selected action.

Note:

When creating a proof through the Workfront Misc Action module, best practice is to create a proof without any advanced options, then update the proof using the Workfront Proof SOAP API.

For more information on creating a proof with the Workfront API (which this module uses), see Add advanced proofing options when creating a proof through the Adobe Workfront API

Enter or map the unique Workfront ID of the record that you want the module to interact with.

To get the ID, open the Workfront object in your browser and copy the text at the end of the URL after "ID=." For example: https://my.workfront.com/project/view?ID=5e43010c03286a2a555e1d0a75d6a86e

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

Misc action options

Task
Issue
Project

Task

Action

Options

Copy

clearApprovers
clearAssignments
clearConstraints
clearCustomData
clearDocuments
clearExpenses
clearFinancials

Clears financial data
clearPermissions
clearPredecessors
clearProgress
clearTimedNotifications

Clears reminder notifications

Move

clearApprovers
clearAssignments
clearDocuments
clearConstraints
clearExpenses
clearFinancials

Clears financial data
clearPermissions
clearPredecessors
clearProgress
clearTimedNotifications

Clears reminder notifications

Issue

Action

Options

Copy

clearApprovers
clearAssignments
clearCustomData
clearDocuments
clearPermissions
clearProgress

Convert to task

preserveIssue

Keep the original issue and tie its resolution to this task
preservePrimaryContact

Allow the issues's primary contact access to this task
preserveCompletionDate

Keep the Planned Completion Date of the issue

Convert to project

preserveIssue

Keep the original issue and tie its resolution to this task
preservePrimaryContact

Allow the issues's primary contact access to this task

Project

Action

Options

Copy

clearApprovers
clearAssignments
clearCustomData
clearDocuments
clearExpenses
clearFinancials

Clears financial data
clearPermissions
clearPredecessors
clearProgress
clearTimedNotifications

Clears reminder notifications

Attach template / Save as template

clearApprovers
clearAssignments
clearBillingRates
clearConstraints
clearDeliverables

Clears goals
clearDocuments
clearExpenses
clearFinancials

Clears financial data
clearHourTypes
clearIssueSetup

Clears queue propterties and issues setup
clearPredecessors
clearRisks
clearSharingOptions
clearTimedNotifications

Clears reminder notifications

Read a Record

This action module retrieves data from a single record.

You specify the ID of the record. You can also specify which related records you want the module to read.

For example, if the record that the module is reading is a project, you can specify that you want the project’s tasks read.

The module returns an array of data from the output fields you specified.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Record Type

Choose the Workfront object type that you want the module to read.

Outputs

Select the information you want included in the output bundle for this module.

Output Custom Form

Select the custom forms that you want included in the output bundle for this module, then select the specific fields from those custom forms that you want included in the output.

References

Select any reference fields that you want to include in the output.

Collections

Select any reference fields that you want to include in the output.

Enter the unique Workfront ID of the record that you want the module to read.

To get the ID, open the Workfront object in your browser and copy the text at the end of the URL after "ID=." For example: https://my.workfront.com/project/view?ID=5e43010c03286a2a555e1d0a75d6a86e

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

Update Events Payload Version

Workfront recently released a new version of its event subscription service. The new version is not a change to the Workfront API, but rather a change to the event subscription functionality. This action module updates the event payload version used for this scenario.

For more information on the new event subscription version, see Event subscription versioning in the Workfront documentation

For resources on preserving your Workfront Fusion scenarios during the event subscription upgrade, including a webinar recording, see Preserving Your Fusion Scenarios During the Event Subscriptions V2 Upgrade.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Version

Select the version of the event subscription that you want to use for this payload.

Update a record

This action module updates an object, such as a project, task, or issue. The module allows you to select which of the object’s fields are available in the module.

You specify the ID of the record.

The module returns the ID of the object and any associated fields, along with any custom fields and values that the connection accesses. You can map this information in subsequent modules in the scenario.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Enter the unique Workfront ID of the record that you want the module to update.

To get the ID, open the Workfront object in your browser and copy the text at the end of the URL after "ID=." For example: https://my.workfront.com/project/view?ID=5e43010c03286a2a555e1d0a75d6a86e

Record Type

Select the type of Workfront record that you want the module to update.

Select fields to map

Attach Custom Form

Select the custom forms that you want to provide field values for on the new record. After you select the form, enter the data for the fields on that form.

To provide field values for a form that you are attaching in this module, include the custom form ID in the fields to map section.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

NOTE

When entering the text for a custom field or a Note object (Comment or reply), you can use HTML tags in the Note Text field to create rich text, such as bold or italic text.

Upload Document

This action module uploads a document to a Workfront object, such as a project, task, or issue. This module uploads the document in chunks, which makes the upload process smoother for Workfront.

This module can handle larger files than the legacy module, and is part of a phased rollout to organizations with an Ultimate Workfront package.

You specify the location for the document, the file you want to upload, and an optional new name for the file.

The module returns the ID of the document and any associated fields, along with any custom fields and values that the connection accesses. You can map this information in subsequent modules in the scenario.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Related Record ID

Enter the unique Workfront ID of the record to which you want to upload the document.

Related Record Type

Select the type of Workfront record where you want the module to upload the document.

Folder ID

Depending on the type of related record, you may need to enter or map a folder ID.

Source file

Select a source file from a previous module, or map the source file's name and data.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.

Searches

Read Related Records
Search
Search (Legacy)

This search module reads records that match the search query you specify, in a particular parent object.

You specify which fields you want included in the output. You can map this information in subsequent modules in the scenario.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Record Type

Select the type of the parent record (Workfront object) whose associated records you want to read.

See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module in this article.

Parent Record ID

Enter or map the ID of the parent record whose associated records you want to read.

To get the ID, open the Workfront object in your browser and copy the text at the end of the URL after "ID=." For example: https://my.workfront.com/project/view?ID=5e43010c03286a2a555e1d0a75d6a86e

Collections

Select or map the type of child record that you want the module to read.

Outputs

Select the information you want included in the output bundle for this module.

Search

This search module looks for records in an object in Workfront that match the search query you specify.

You can map this information in subsequent modules in the scenario.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Record Type

Select the type of Workfront record that you want the module to search for.

Custom forms list

Select at least one custom form. Fields from these custom forms will be available for the search query.

Result Set

Select an option to specify whether you want the module to get the first result that matches your search criteria or all the results that match it.

Maximal

Enter or map the maximum number of records you want the module to return during each scenario execution cycle.

Search criteria fields

Select the fields that you want to use for your search criteria. These fields will then be available in the Search criteria dropdown.

Search criteria

Enter the field that you want to search by, the operator you want to use in your query, and the value that you are searching for in the field.

Note: Do not use username in your search criteria. Including username in an API query to Workfront logs the user into Workfront, and the search will not be successful.

Note: In and NotInwork with arrays. The inputs should be in array format.

Outputs

Select the fields that you want to include in the output for this module.

References

Select any reference fields that you want to include in the search.

Collections

Select any collections that you want to add to the search.

Search (Legacy)

IMPORTANT

This module has been replaced with the Search records module. We recommend using that module in new scenarios.
Existing scenarios that use this module will continue to function as expected. This module will be removed from the module selector in May 2025.

This search module looks for records in an object in Workfront that match the search query you specify.

You can map this information in subsequent modules in the scenario.

When you are configuring this module, the following fields display.

Connection

For instructions about connecting your Workfront app to Workfront Fusion, see Connect Workfront to Workfront Fusion in this article.

Record Type

Select the type of Workfront record that you want the module to search for.

Result Set

Select an option to specify whether you want the module to get the first result that matches your search criteria or all the results that match it.

Maximal

Enter or map the maximum number of records you want the module to return during each scenario execution cycle.

Search criteria fields

Select the fields that you want to use for your search criteria. These fields will then be available in the Search criteria dropdown.

Search criteria

Enter the field that you want to search by, the operator you want to use in your query, and the value that you are searching for in the field.

Note: Do not use username in your search criteria. Including username in an API query to Workfront logs the user into Workfront, and the search will not be successful.

Note: In and NotInwork with arrays. The inputs should be in array format.

Outputs

Select the fields that you want to include in the output for this module.

References

Select any reference fields that you want to include in the search.

Collections

Select any collections that you want to add to the search.

Workfront object types available for each Workfront module

Object types available for each Workfront trigger module
Object types available for each Workfront action module
Object types available for each Workfront search module

Object types available for each Workfront trigger module

Watch Record

Watch Field

Watch Events

Approval Process

✓

Assignment

✓

Baseline

✓

Billing Record

✓

Billing Rate

✓

Company

✓

Dashboard

✓

Document

✓

Document Folder

✓

Document Request

✓

Document Version

✓

Expense

✓

Expense Type

Group

✓

Hour

✓

Hour Type

✓

Issue

✓

Iteration

✓

Job Role

✓

Journal Entry

✓

Milestone

✓

Milestone Path

✓

Note

✓

Note Tag

✓

Portfolio

✓

Program

✓

Project

✓

Project User

✓

Proof Approval

✓

Reserved Time*

✓

Report

✓

Risk

Risk Type

Step Approver

✓

Task

✓

Team

✓

Template

✓

Template Task

✓

Timesheet

✓

User

✓

Update

Object types available for each Workfront action module

NOTE

The Download Document module is not included in this table because Workfront object types are not part of its configuration.

Create a record

Update a record

Delete a record

Upload Document

Read a record

Custom API Call

Misc Action

Approval Process

✓

Assignment

✓

Baseline

✓

Billing Record

✓

Billing Rate

✓

Company

✓

Document

✓

Document Folder

✓

Document Version

✓

Exchange rate

✓

Expense

✓

Expense Type

✓

External Document

✓

Group

✓

Hour

✓

Hour Type

✓

Issue

✓

Iteration

✓

Job Role

✓

Journal Entry

✓

Milestone

✓

Milestone Path

✓

Note

✓

Note Tag

✓

Portfolio

✓

Program

✓

Project

✓

Project User

✓

Reserved Time*

✓

Risk

✓

Risk Type

✓

Step Approver

✓

Task

✓

Team

✓

Template

✓

Template Task

✓

Timesheet

✓

User

✓

Update

✓

Object types available for each Workfront search module

Read Related Records

Approval Process

✓

Assignment

✓

Billing Record

✓

Billing Rate

✓

Company

✓

Document

✓

Document Folder

✓

Document Version

✓

Expense

✓

Expense Type

✓

Group

✓

Hour

✓

Hour Type

✓

Issue

✓

Iteration

✓

Job Role

✓

Journal Entry

✓

Milestone

✓

Milestone Path

✓

Note

✓

Note Tag

✓

Portfolio

✓

Program

✓

Project

✓

Project User

✓

Reserved Time*

✓

Risk

✓

Risk Type

✓

Step Approver

✓

Task

✓

Team

✓

Template

✓

Template Task

✓

Timesheet

✓

User

✓

User Delegation

✓

We recommend that you double check to ensure this works the way you would expect it to.

Event subscription filters in the Workfront > Watch Events modules

Filters in event subscriptions allow you to ensure that your scenarios run only when certain parameters are met.

Event subscription filter best practices
Using Advanced filters

Event subscription filter best practices

NOTE

We highly recommend using event subscription filters in your Watch Events modules.
Workfront recently released a new version of its event subscription service. The new version is not a change to the Workfront API, but rather a change to the event subscription functionality. This action module updates the event payload version used for this scenario.

For more information on the new event subscription version, see Event subscription versioning in the Workfront documentation

For resources on preserving your Workfront Fusion scenarios during the event subscription upgrade, including a webinar recording, see Preserving Your Fusion Scenarios During the Event Subscriptions V2 Upgrade.

The Workfront Watch Events module triggers scenarios based on a webhook that creates an event subscription in the Workfront API. The event subscription is a set of data that determines which events are sent to the webhook. For example, if you set up a Watch Events module that is watching for issues, then the event subscription sends only events related to issues.

By using event subscription filters, Fusion users can create event subscriptions that are a better fit for their use cases. For example, you can set up an event subscription in the Workfront API to send only issues that are in a specific project to the webhook, ensuring that the Watch Events module will only trigger for issues in that project. The ability to create narrower triggers improves scenario design by reducing the number of irrelevant triggers.

This is different from setting up a filter in the Workfront Fusion scenario. Without an event subscription filter, your webhook receives all events related to the object type you select. Most of these events would be irrelevant to the scenario, and must be filtered out before the scenario can continue.

The following operators are available in the Workfront > Watch events filter:

Equals
Not equals
Greater than
Less than
Greater than or equal to
Less than or equal to
Contains
Exists
- This operator does not require a value, and the value field is absent.
Does not exist
- This operator does not require a value, and the value field is absent.
Changed
- This operator does not require a value, and the value field is absent.
- This operator ignores the State field.
- When using Changed, select Updated Events Only in the Record Origin field.

IMPORTANT

You cannot edit filters in existing Workfront webhooks. To set up different filters for Workfront event subscriptions, remove the current webhook and create a new one.

INFO

Example: Consider a scenario that processes new issues that are assigned to a specific user, Ana.

Filter events by using an event subscription filter (recommended)

Using the event filter, you can set up the webhook to trigger the scenario when an issue is assigned to Ana when the issue is created. Ana has the userID b378489d8f7cd3cee0539260720a84b7.

If 100 issues are created in a day, but only two of them are assigned to Ana, the scenario would execute twice.

Filter events inside the scenario (not recommended)

To filter events so that only issues assigned to Ana are processed, you could create a filter after the Watch Events module.

If 100 issues are created in a day, but only two of them are assigned to Ana, the scenario would execute 100 times. 98 of the executions would stop at the filter, but the trigger module is still consuming data and performing operations in all of the executions.

For more information on Workfront event subscriptions, see FAQs - Event Subscriptions.

For more information on webhooks, see Instant triggers (webhooks) in Adobe Workfront Fusion

For more information on filters in scenarios, see Add a filter to a scenario.

Using Advanced filters

The Workfront > Watch events module offers two types of filters.

Simple: This filter provides an interface that allows you to select fields, operators, and values, along with AND and OR operators to create a filter.
Advanced: This filter allows you to upload JSON that represents your filter.

Simple vs. Advanced filters

The main difference between the two types is the State of the filter.

Simple: When setting up a simple filter, you select whether you want to filter on a field’s old state or new state. That is, you decide whether you want to activate the scenario when the field changes from a given value, or whether to activate when it changes to a given value. Using AND and OR allows you to include multiple fields and values, but they must share the same state. You cannot use the old state for some fields and the new state for others.
Advanced: You can configure the JSON in an advanced filter to specify values for both old and new states in the same filter. For example, you could specify that you want to trigger a scenario when a project moves from a Planning status to a Current status. This would exclude projects that move from Planning to Dead, or that move from On Hold to Current.

recommendation-more-help

workfront-fusion-help-workfront-fusion