Reference · built on requestConnectorWork & ticket management

Adobe Workfront

Projects, tasks, issues, approvals, and hours from Adobe Workfront, with changes pushed by event subscriptions.

Request Adobe WorkfrontAsk about this listing

About

Adobe Workfront is a work management system. Teams plan projects, break them into tasks, log issues against them, route approvals, and record hours on timesheets. Each of these is an object in the Workfront REST API, addressed as /attask/api/<version>/<object>/<id>, and event subscriptions push CREATE, UPDATE, and DELETE messages for those objects to a URL you register.

Through Fibric an operator watches task and issue changes as they arrive, reads the project and assignment around each one, and proposes the next update for your approval. Every proposal leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Adobe Workfront and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

What it reads

  • Projects (PROJ), tasks (TASK), and issues (OPTASK) with status, assignments, and planned dates, read by GET with fields and filters parameters
  • Approvals and approval stages, including the participants assigned to each stage
  • Hours (HOUR) and timesheets (TSHET) as they are logged and submitted
  • Users, teams, portfolios, and programs that own the work
  • CREATE, UPDATE, and DELETE events for subscribed objects, delivered to your URL with oldState and newState
  • Named queries such as /work/myWork and report queries through the same API

Proposed actions

  • Target capability: propose a status or assignment change on a task or issue through PUT on the object
  • Target capability: propose creating an issue against a project through POST
  • Target capability: propose a note on a project, task, or issue
  • Target capability: propose a batch of up to 100 task updates in one request

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Chase the actions a meeting produced

    Tasks created from a meeting are subscribed by objId. When a planned date passes without a status change, the operator drafts a reminder to the assignee for a person to send.

    With Action Follow-up

  • Close the week's timesheets

    Hours and timesheets are read as they are submitted. Unsubmitted sheets are listed by team, and the operator proposes the reminder and the approval order.

    With Timesheet Signoff

  • Prepare the weekly project review

    Projects, their open issues, and tasks past planned completion are pulled once through report queries. The operator drafts the review with each item linked back to Workfront.

    With Weekly Review, Meeting Prep

What it needs

  • A Workfront instance at yourdomain.my.workfront.com and a user with access to each object you read or write
  • A custom OAuth2 application created in Setup, with an RS256 keypair for the JWT flow; an instance may hold up to ten
  • System Administrator access level to create event subscriptions
  • An HTTPS endpoint that returns a 200-level response to each event subscription message
  • A pinned API version in every request; versions are supported for 3 years after release
Authentication
OAuth 2.0 through a custom OAuth2 application (JWT flow for server access, authorization code flow for a signed-in user) or an apiKey parameter; the /login endpoint and username/password are deprecated.

Limits

  • Searches return 100 records by default and 2,000 at most per request; field depth is capped at 4
  • Workfront caps concurrent API threads per instance and publishes no numeric rate; the sandbox has the same cap
  • Undelivered event messages are retried up to 11 times over 48 hours, after which a subscription can be disabled or frozen
  • Adobe stops creation of new custom OAuth2 applications on November 1, 2026 and ends existing ones on February 1, 2027

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Adobe Workfront

Questions and answers

Does Adobe Workfront push changes or must the connector poll?
Both are available. Event subscriptions are created with POST to /attask/eventsubscription/api/v1/subscriptions, naming an objCode, an eventType of CREATE, UPDATE, or DELETE, a URL, and an authToken. Messages carry oldState and newState and usually arrive within 5 seconds. Polling by GET with filters covers objects without a subscription.
Which API version does the connector call?
A pinned one. Requests name the version in the path, /attask/api/<version>/. Version 22 was released May 8, 2026, and each version is supported for 3 years after release. The connector is built against a supported version and moved forward before that version's end of support.
What happens to an event subscription when your endpoint goes down?
Workfront retries any non-200 delivery up to 11 times over about 48 hours. A subscription with sustained failures is marked disabled and retried every 10 minutes until a delivery succeeds. After 2,000 consecutive failures with no success in 72 hours it is frozen and must be re-enabled through the API.
Ask about Adobe Workfront

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Adobe Workfront through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy