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.
-
In any Adobe Workfront module, click Add next to the Connection field.
-
Fill in the following fields:
-
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.
- 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.
- 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
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 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.
-
Click Add to the right of the Webhook box.
-
Configure the webhook in the Add a hook box that displays.
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.
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.
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
This action module makes one of the following conversions:
- Convert Issue to Project
- Convert Issue to Task
- Convert Task to Project
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.
See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.
- 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.
Create Record (Legacy)
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 action module creates an object, such as a project, task, or issue in Workfront. 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.
This module does not attach custom forms when creating the object. To attach custom forms while creating an object, use the Create a record (attaching custom forms) module.
When you are configuring this module, the following fields display.
See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.
- 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.
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.
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.
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.
When you are configuring this module, the following fields display.
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 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.
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
This action module lets you perform actions against the API.
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.
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
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.
See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.
Read a Record (Legacy)
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 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.
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
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.
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 Record (Legacy)
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 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.
See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.
- 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.
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.
See a list of the Workfront object types for which you can use this module in Workfront object types available for each Workfront module.
Upload Document (Legacy)
This action module uploads a document to a Workfront object, such as a project, task, or issue. It uploads the entire document at once.
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.
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
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.
Search records
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.
Search (Legacy)
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.
Workfront object types available for each Workfront 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
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
Search | 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.