Adobe Workfront is a work management platform for enterprises looking to strategically prioritize, assign, and complete projects quickly at any scale. With its central dashboard, you can quickly launch projects by seeing available resources and assigning tasks using templates and automation.
The Workfront integration allows you to sync new assets, add new asset versions, and map new metaproperties using Workfront Metadata from your Workfront documents into your Webdam via a Workfront status update. The integration will check for new assets every five minutes.
This enables teams to work more efficiently without having to use two separate systems and ensures that content is always current.
This integration is part of the Integrations Hub
How to enable this connector/ integration in your portal?
Reach out to your Customer Success Contact to learn more about enabling this integration and any associated costs.
Before Setting up the Integration
Please ensure the following is enabled in both your Workfront and Bynder accounts.
-
Set up Bynder metaproperties you would like to map to the Workfront metadata.
Note
Note: If you do not know the fields you would like to set up beforehand, you can always start setting up the integration and then go back to setting up the field mapping. The setup will save regardless of whether you’ve set up fields mapping.
-
Add the Task Status in your Workfront account that you would like to use as the trigger for this integration.
-
You must set up the status in Task, not Project.
-
You can add multiple statuses to trigger the Workfront/Bynder workflow.
-
If you delete the connected task status, the integration will be disconnected.
-
Click here to learn more about how to add task statuses in Workfront.
-
-
The Workfront Task documents are the assets synced into Webdam, NOT the Project documents. To ensure successful integration, please let your teams know to upload the assets you want in Webdam into the Workfront Task document section.
-
The integration will sync all documents that appear in your Workfront task folder.
How to Set up Workfront Integration
Admins will be able to set up and configure the integration.
-
Navigate to Settings > Advanced settings > Portal settings.
-
Click the Premium tab, where you will see Workfront.
-
Click Configure.
Note
You can only configure one Workfront Account.
-
Enter a Name for this configuration, then click Save.
- Select your Webdam authentication method. Add your Webdam credentials (portal domain, Webdam login information). Learn how to create your Client ID and Client Secret.
-
Select your Workfront Authentication method and add the following information.
-
Authentication name
-
Workfront Username
-
Workfront Password
-
Workfront Subdomain
-
-
Click Next.
-
Configure the setting under Weddam settings. Select the Webdam Folder you want to sync assets to.
-
Configure Workfront Settings
-
Workfront Task Status: Assign the Workfront status you previously created that you would like to act as a trigger to send documents into your Webdam Portal. For example, if you previously created a Workfront Task Status called “Ready for Webdam,” select that status in the dropdown.
-
- (Optional) Select Use Custom Form Fields for Metadata.
- Selecting this option will show all the fields in the fields Mapping on the selected custom form. (Supported Custom Forms are TASK and DOCUMENTS only.)
-
Click Next.
-
Field Mapping: In the table, select which fields from Webdam fields should have values written from Workfront Metadata.
- If Custom Form Fields is enabled, click here to learn how to map your metadata.
- If Custom Form Fields is not enabled, most available fields listed are system fields for tasks and documents. Follow the steps below.
- To create a custom value, select Add to Configuration and select Set.
-
Click Next.
Note
Establish the fields in your Webdam before setting up this integration. If you need to add fields to your Webdam account, you can X out of this integration setup, and your information will be saved.
-
Click Next >Finish.
Field Mapping with Custom Form Fields
- A dropdown for selecting custom form fields will appear
- If you select “ONLY STANDARD FIELDS” it will only show the standard field in the mapping.
- If you select a Custom Form, it will have the fields available in the fields mapping.
- Once selected, you can configure custom fields or system fields from Webdam fields with values written from Workfront Metadata.
- Select Add to Configuration in the Workfront Metadata column and choose Webdam fields.
- Click Finish.
How to Use the Integration
After configuration, you can update your Workfront task status to start syncing the related task documents into your Webdam. Moving forward, any time your task status changes to the selected Workfront synced status or a new document is uploaded into a previously synced task; it will appear in your Webdam after roughly 5 minutes.
Edit the Integration
You can edit the configuration to disable the integration or update your settings and workflows.
-
Navigate to Settings > Advanced settings > Portal settings.
-
Click Active Integrations in the left sidebar
-
Click Edit in the connection section you would like to update.
-
Make your changes, then click Save.
Delete or Disable Integration.
If you want to disable or delete the integration, follow the above steps: click on and disable or delete.
Setting up a Custom OAuth App
- Navigate to oAuth apps
- From the profile flyout, select Setup.
- Under the system, you will find OAuth2 Applications.
- Click Create app integration.
- In the popup modal, select Web Application and name the app.
- A Client ID will be automatically generated.
- Copy that value into a secure location.
- Under redirect URI, enter the following exact URL: https://auth.tray.io/oauth2/token.
- Under Client Secret, select Add Client Secret.
- Copy the value generated in this pop-up window.
- Once closed, a client secret cannot be retrieved. If lost, the only option is to create a new client secret.
- Under the Refresh token setting
- Do not opt to Rotate refresh token everytime it is used. The integration does not currently support this.
- Under Absolute expiration, we recommend the longest possible lifespan your organization will allow. Workfront’s maximum lifetime is two years. This option sets the maximum lifetime a login is valid for. So, if you select two years, you will not need to re-authenticate in the hub for two years. Shorter lifetimes will mean that a user will need to re-authenticate the hub more often.
- To Re-authentication, you must edit the integration and update the authentication.
- Set the Inactivity expiration to any reasonable amount of time. This shouldn’t be an issue, as the Workfront API runs at a 5-minute interval. Anything longer than that should be sufficient.
- Click Save.
- Input the Subdomain, Client ID, and Client Secret.
FAQs
What types of files are supported?
All file types are supported.
What happens if I delete the asset from Workfront (or vice versa)?
If you delete an asset in Workfront, it will remain in Webdam. If you delete an asset in Webdam, it will remain in Workfront.
What if I use a SAML login for my company's Workfront Account?
See here for steps to create a custom OAuth to integrate Webdam and Workfront.
What happens if you upload a new version of the file in Workfront?
Adding a new version to the existing Webdam file will only work if you enable the Version uploaded assets with same name setting. Otherwise, the file will be uploaded separately with the same name and version number.
What will happen if I delete the synced task status in Workfront?
Deleting the synced task status in Workfront will disconnect the integration. To fix this, you must re-add the task status in Workfront and edit the integration in Webdam to select that new status.
How long will it take for assets to appear in my Asset bank?
Your asset will sync after approximately 5 minutes.
What Custom Forms are supported for mapping?
Currently, TASKS and DOCUMENTS are the only Custom Forms supported for field mapping. Learn more about Custom Form Fields here.
- field mapping.webp30 KB
- field mapping.webp40 KB
- finsih.webp30 KB
Updated
Comments
0 comments
Article is closed for comments.