Skip to main content

Adobe Workfront Setup

Connecting Adobe Workfront to Caddi

Adobe Workfront is a bring-your-own-application connector. Your organization creates an OAuth Web App in Adobe Developer Console, gives Caddi its credentials and your Workfront API domain, and then each user signs in through Adobe.

Creating the credential needs full system administrator rights for your IMS Organization in the Adobe Admin Console, and the Adobe ID used must belong to the IMS Organization that owns the Workfront instance. If Adobe Workfront does not appear when adding an API, that is almost always why.

Before you start

You'll need:

  • An Adobe Workfront licence for your organization

  • Full system administrator rights for the IMS Organization in Adobe Admin Console

  • An Adobe ID in the IMS Organization that owns the Workfront instance you want to connect

  • Owner or Admin access to your Caddi organization

  • A Workfront administrator who can read the instance domain under Setup → System → Customer Info

Step 1: Create the OAuth Web App in Adobe Developer Console

  1. Sign in to Adobe Developer Console with an Adobe ID that has full system administrator rights for your IMS Organization.

  2. Create a project, or open the project you will use for Caddi.

  3. Select Add API.

  4. Select Adobe Workfront, then choose the Workfront instance Caddi should access.

  5. Create an OAuth Web App credential for the API.

  6. Set https://app.trycaddi.com/oauth-callback as the credential's default redirect URI and as its allowed redirect pattern, then save.

  7. Open the credential details and copy the Client ID and Client Secret. Store the secret securely.

  8. Open the credential's Scopes tab and compare it with Caddi's defaults, openid,AdobeID,email,offline_access,read_organizations,additional_info.projectedProductContext,workfront_api. If the tab lists something different, record it exactly — you will need it in Step 3.

Step 2: Find your Workfront API domain

  1. In Workfront, open Setup → System → Customer Info and note the domain of the instance you selected in Step 1.

  2. Your API domain is <domain>.my.workfront.adobe.com if you sign in to Workfront at experience.adobe.com, and <domain>.my.workfront.com otherwise.

Step 3: Configure Workfront in Caddi

This step must be completed by a Caddi organization owner or admin.

  1. In Caddi, open Settings, then Integrations.

  2. Under Connectors you can configure, find Adobe Workfront - Custom OAuth Web App and click Configure.

Enter the following values:

  • Client ID — from the OAuth Web App credential

  • Client Secret — from the same credential

  • Workfront Domain — the API domain from Step 2

  • OAuth Scopes — leave blank to use Caddi's defaults. Only fill this in if Step 1 found different scopes on the credential; then enter exactly those, comma-separated, and add offline_access.

Click Save Configuration.

Step 4: Connect your account

  1. Go to the My Connections tab and find Adobe Workfront.

  2. Click Connect +.

  3. On Adobe's authorization screen, sign in with the Adobe account for the selected Workfront instance and approve Caddi.

  4. You'll be returned to Caddi with the connection active.

How the connection behaves

  • Caddi acts as the approving Workfront user. That user's access level decides what Caddi can see and change — Adobe's public documentation does not publish a minimum permission set for this, so give the connecting user the Workfront access the work actually needs.

  • offline_access is what keeps the connection alive. Adobe issues a refresh token only when it is part of the grant, and the refresh token is what lets the connection renew itself in the background.

  • The domain pins the instance. One configured domain means one Workfront instance per Caddi organization.

Troubleshooting

Adobe Workfront is not offered when adding an API

The signed-in Adobe ID is in the wrong IMS Organization, or lacks full system administrator rights. Switch organizations, or ask one of its full system administrators to create the project and credential.

Adobe rejects the redirect URI

It must match exactly. Copy https://app.trycaddi.com/oauth-callback into both the credential's default redirect URI and its allowed redirect pattern, save, and try again.

Adobe reports an invalid client, or the code cannot be exchanged

The Client ID and Client Secret are from different credentials, or the secret has been rotated. Reopen the credential in Adobe Developer Console, copy both current values, update them in Caddi, and reconnect.

Authorization fails with a scope error

Caddi asked for a scope this credential does not carry. Copy the scopes exactly from the credential's Scopes tab into OAuth Scopes, comma-separated, add offline_access, and reconnect.

Keeping the connection active in the background

offline_access was omitted, so Adobe issued no refresh token. Add it to OAuth Scopes, then reconnect and approve again.

Caddi connects but reaches the wrong instance, or cannot reach the API at all

Workfront Domain does not match the instance selected for the Developer Console project, or uses the wrong domain format for how you sign in. Enter that instance's API domain and reconnect.

Expected Workfront data is missing

The approving Workfront user does not have access to it. Confirm their Workfront access level, and if OAuth Scopes is filled in, confirm it still matches the credential's Scopes tab.

Still stuck? Contact Caddi support with the exact error message you're seeing and the time it occurred.

Sources

Related Articles
Did this answer your question?