Skip to main content
What you can do:
  • Ingest Workfront tasks and requests into Gradial with their fields, comments, and documents
  • Filter tasks by project, program, portfolio, status, or custom fields
  • Trigger Gradial execution when tasks match your criteria
  • Write results — previews, links, comments, status updates — back to the Workfront task
  • Discover matching projects and start project work with a configured skill and prompt
  • Answer an activated project’s pending clarification from a Workfront comment
  • Upload an approved PDF and create a proof, optionally with named reviewers and approvers
Access: Automatic ticket intake, project discovery and activation, CX Commenting, and proof creation must be enabled for your organization. Contact your Gradial team for the capabilities you need.

Prerequisites

Service account requirements:
  • A dedicated Workfront integration account for API Key or JWT connections, or the technical account created by Adobe OAuth setup
  • A Workfront administrator to grant the chosen account access; Adobe Developer Console setup also needs an Adobe organization administrator
  • Must have visibility into all tasks and projects you intend to sync
Required permissions for the service account: Permissions are granted through Workfront Access Levels, project- or portfolio-level sharing, or object-level permissions. See Adobe’s documentation on Access Levels and Permissions for configuration guidance. Authentication-specific requirements:

Authentication options

Legacy OAuth2/JWT migration

Gradial supports existing Workfront-native OAuth2/JWT and API-key connections alongside Adobe Developer Console OAuth Server-to-Server connections. Adobe Developer Console OAuth Server-to-Server is the replacement for legacy Workfront-native custom OAuth2/JWT. Adobe’s migration notice sets these dates for Workfront-native custom OAuth2 applications, including the machine-to-machine JWT flow: These deadlines apply to Workfront-native OAuth2/JWT. The notice does not establish an API-key sunset, and Adobe Developer Console OAuth Server-to-Server is the current replacement method. Existing integrations are not automatically migrated. If your existing Workfront integration uses legacy OAuth2/JWT, contact Gradial for help migrating it to Adobe Developer Console OAuth Server-to-Server before February 1, 2027. The replacement uses a different credential type and technical-account permissions; changing only the old credential values does not complete migration.

Connect Workfront to Gradial

Go to Settings → Integrations, select Adobe Workfront, and add an integration. The wizard has Connection, Routing, and Route summary steps. On Connection, name the integration and follow the steps for your authentication method.

Option A — API Key

  1. Enter your Workfront Base URL (e.g., https://your-company.my.workfront.com)
  2. Enter the service account email
  3. Paste your API Key
  4. Click Validate Connection

Option B — Adobe OAuth 2.0 (server-to-server)

  1. Follow Adobe’s credential setup guide to add the Adobe Workfront API to an Adobe Developer Console project and select Server-to-Server for the correct Workfront instance.
  2. Give the resulting technical account access to the Workfront objects Gradial will use. New technical accounts start with limited access; webhook subscription management requires Workfront System Administrator access.
  3. In Gradial, select Adobe OAuth 2.0 (server-to-server) and enter the Workfront Base URL, Client ID, Client secret, and comma-separated Scopes from that credential.
  4. Click Validate Connection, then continue to routing. Gradial obtains and renews access tokens automatically.
If this authentication option is unavailable, contact your Gradial team for access. This option is separate from the existing JWT method below. This connection authenticates general Workfront API calls and, with the required permissions, event-subscription requests. CX Commenting is configured separately below.

Option C — OAuth 2.0 JWT (server-to-server)

  1. Select OAuth 2.0 JWT (Server-to-Server) as your authentication type
  2. Enter your Client ID and Client Secret
  3. Enter the Customer ID and User ID (service account)
  4. Paste the Private Key (PEM)
  5. Enter your Workfront Base URL
  6. Click Validate Connection
Credentials are stored securely and cannot be viewed after saving. When credential editing is available, open the existing integration, re-enter all required authentication fields, validate, and save to replace them in place. Include the separate Adobe IMS fields if CX Commenting is configured.

Optional — CX Commenting

CX Commenting uses a separate Adobe IMS credential alongside the ordinary Workfront connection. When available, configure the Adobe developer client ID, Adobe developer client secret, Adobe IMS organization ID, and Workfront user ID; add the Workfront customer ID only when required for your tenant. Gradial obtains and renews the commenting token automatically. Use a dedicated service user’s Workfront ID. Comments appear as that user, and comments from that identity are ignored as triggers to prevent loops. Using a person’s ID would also suppress that person’s requests. Enabling ordinary Adobe OAuth alone does not configure CX Commenting.

Configure routes

On Routing, add a route and select its destination workspace and environment. Choose the integration’s ingestion mode before configuring mode-specific controls.
  • Scheduled ingestion queries matching work periodically.
  • Webhook ingestion responds to new events. Switching to webhooks stops polling after saving and does not automatically import existing requests.
For webhook routes, configure 1 · Scope before 2 · Triggers: If routing by a Workfront field is configured for the integration, map its values to destination routes. That mapping takes precedence over per-route ticket filters for mention and assignment routing. Missing or unmapped values block routing; eligible automatic-intake requests can receive a workspace-choice prompt. Review Route summary before saving. Turning off assignment intake does not turn off mentions or every other intake path. Configure Routes →

Project follow-ups

For an activated project with a linked Gradial Task, post an @Gradial comment on the Workfront Project to request follow-up work. If that Task is waiting for one identifiable clarification, a reply mentioning Gradial can answer it without submitting the Gradial form. Gradial acknowledges an accepted answer in Workfront. Ambiguous questions and approval requests still need to be handled in Gradial.

Create a proof

Ask Gradial to upload an approved PDF to the exact Workfront task and create a proof. You can name 1–20 people, with their names and email addresses, to add as reviewers and approvers when the proof is created. Everyone in that reviewer list must make a decision. Review the approval card for the document version, reviewers, possible invitations, and tenant defaults. For a basic proof created without reviewers, public sharing and original-file download settings inherit the Workfront tenant’s defaults and may be enabled. This flow does not expose custom privacy settings. The upload happens before proof approval, so declining approval can leave the PDF attached to the task. Proof generation is asynchronous. Gradial checks for successful generation and returns the proof viewer link when ready. Creation does not confirm invitation email delivery. If generation fails or an upload/create has an uncertain outcome, ask your Gradial team to inspect it before starting a replacement review round. Adding reviewers to an existing proof, custom deadlines, staged workflows, standalone proof-viewer comments, and changing proof privacy settings are not available in this flow. Add or adjust those directly in Workfront. Proof creation uses the existing Workfront connection; no separate ProofHQ token is needed for creation-time reviewers.

Troubleshooting

Contact your Gradial Product Specialist or email [email protected] if issues persist.