- Home
- Resources
- Integrations
- Adobe Workfront
Claude Adobe Workfront connectorWhat Claude can do in your Adobe Workfront account.
The Claude Adobe Workfront connector exposes 68 tools. 33 read your work data, 32 write to it, and 3 are documented nowhere. Below: what Claude finds, what it changes, the admin switch that gates every write, and the tools Adobe has retired.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for a marketing operations team
Status meetings stop starting with ten minutes of clicking. Ask Claude which projects your team has running, where a video sits in its approval, or which campaigns launch next quarter, and it queries Workfront itself. Once your Workfront admin allows writes, it can also schedule tasks, chase approvers and restructure planning records, asking first where Claude's rules require it.
Unblock an approval. approvals_get_approval_info shows the stage and who has not decided, then approvals_send_reminder_to_undecided emails all of them in one go.
Move work forward. workflow_search_any_object finds overdue tasks, workflow_update_any_object pushes their dates or sets dependencies, and workflow_create_any_object opens the next project with you as owner.
Keep Planning in shape. planning_search_records filters campaign records, planning_bulk_record_actions reassigns twenty of them at once, and planning_create_view gives the events team its calendar.
What it will not do: write tools are off by default on the Workfront side, so a fresh connection only reads until an admin flips that switch. Nothing runs on its own either: no tool fires when a task goes late. For event-driven flows, the Adobe Workfront Make integration covers a different need, and the Integrations hub lists the rest.
The vocabulary in one minute
Five words you will meet while plugging Adobe Workfront into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs on its own, and the directory sheet lists them by name.
- Authorization
- The Workfront sign-in with your Adobe ID, where you hand Claude its access to one instance. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before it goes ahead with a change to your account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Workfront.
Connect Adobe Workfront to Claude in three steps
- 01
Find Adobe Workfront in Claude
Open Claude's settings, go to Customize then Connectors, and look for Adobe Workfront. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on first; Adobe says to ask your Claude admin if it is missing.
- 02
Start the connection
Click Connect and sign in to your Workfront instance in the window Adobe opens. You may have to pick a profile and an instance: that choice decides which workspace Claude reaches.
- 03
Read the authorization screen
Go through the authorization before you accept: it belongs to Adobe, not to Claude, and it sets what the access covers. One connection means one instance; to switch, use Disconnect and connect again.
The 68 tools, sorted by what they do
Adobe Workfront gives Claude 68 tools: 33 that read your account, 32 that change something in it, and 3 no official source describes.
Three groups: what Claude reads, what it writes, and what no official source describes. Adobe labels every documented tool Read or Write itself.
- 33 read
- 32 write
- 3 not documented
Tools index
- approvals_find_document_version_by_name
- approvals_get_document_by_version_id
- approvals_resolve_document_scope
- approvals_get_approval_info
- approvals_list_templates
- approvals_search_template_by_name
- approvals_get_current_user
- approvals_find_user_by_name
- approvals_find_team_by_name
- approvals_find_project_by_name
- approvals_get_projects_by_owner
- planning_get_workspace
- planning_get_workspace_list
- planning_get_workspace_sharing
- planning_get_record_type
- planning_list_global_record_types
- planning_list_addable_global_record_types
- planning_get_external_record_workspaces
- planning_get_record_type_sharing
- planning_get_record
- planning_search_records
- planning_get_record_change_log
- planning_get_record_sharing
- planning_get_field
- planning_get_view
- planning_get_view_sharing
- planning_get_template_list
- planning_get_template
- planning_search_resources
- planning_search_sharing_data
- planning_search_users
- workflow_search_any_object
- workflow_resolve_field_names_any_object
- approvals_create_or_update_approval_workflow
- approvals_create_approval_from_template
- approvals_delete_approval_stage
- approvals_send_reminder_to_participants
- approvals_send_reminder_to_undecided
- approvals_create_template
- approvals_update_template
- planning_create_workspace
- planning_create_workspace_from_template
- planning_update_workspace
- planning_delete_workspace
- planning_convert_workspace_to_template
- planning_modify_workspace_sharing
- planning_create_record_types
- planning_update_record_type
- planning_delete_record_type
- planning_add_global_record_type_to_workspace
- planning_modify_record_type_sharing
- planning_bulk_record_actions
- planning_create_connection_record
- planning_update_records_order
- planning_modify_records_sharing
- planning_create_fields
- planning_update_field
- planning_delete_field
- planning_create_view
- planning_update_view
- planning_delete_view
- planning_modify_view_sharing
- workflow_create_any_object
- workflow_update_any_object
- workflow_delete_any_object
What Claude reads (33)
33 toolsThirty-three tools that look things up without changing your data. Five of them are marked retired or deprecated by Adobe.
approvals_find_document_version_by_name
Looks up the current version of a document from its file name, partial names included, so Claude can then work on the right file.
approvals_get_document_by_version_id
Fetches the details of a document version Claude already identified: name, size, upload date and who uploaded it.
approvals_resolve_document_scope
Expands a project or a folder into the list of document versions it contains, by project, by folder or by folder name.
approvals_get_approval_info
Returns the current approval workflow of a document version: its stages, participants and status, and each path when reviews run in parallel.
approvals_list_templates
Lists the approval templates available in your Workfront instance, filterable by creator or participant and sortable by how often they are used.
approvals_search_template_by_name
Finds approval templates from part of their name, whatever the case.
approvals_get_current_user
Returned the identity of the connected Workfront user, with team details. Adobe's reference says it was retired on August 13, 2026, and points to an Insights tool instead, although the directory sheet still lists it.
approvals_find_user_by_name
Looks up a Workfront user from a full or partial name, returning name, identifier, email and title. Adobe marks it as deprecated in favour of a newer user search.
approvals_find_team_by_name
Finds a Workfront team from a full or partial name. Adobe flags it as deprecated and recommends a newer lookup tool.
approvals_find_project_by_name
Used to look up Workfront projects by partial name. Adobe's tools reference states it was retired on August 13, 2026, while the directory sheet still displays it.
approvals_get_projects_by_owner
Used to list the projects owned by the connected user. Adobe says it was retired on August 13, 2026 and suggests its main Insights query tool instead.
planning_get_workspace
Retrieves the full details of a Planning workspace from its identifier or alias.
planning_get_workspace_list
Lists every Planning workspace available to you, page by page.
planning_get_workspace_sharing
Shows who has access to a workspace and at which permission level, the starting point of any sharing question.
planning_get_record_type
Fetches everything about a record type, including its fields and views, the blueprint behind every record of that kind.
planning_list_global_record_types
Lists the record types defined centrally for the whole organisation that you are allowed to see, shared across workspaces.
planning_list_addable_global_record_types
Tells Claude which global record types can still be added to a given workspace.
planning_get_external_record_workspaces
Finds which workspaces and record types are connected to a given external record, such as a Workfront project.
planning_get_record_type_sharing
Reports who can access a specific record type and at which level, separately from the workspace itself.
planning_get_record
Opens one record in full from its identifier, every field included.
planning_search_records
Searches and filters the records of a record type.
planning_get_record_change_log
Returns the field-level history of a record, field by field and revision by revision.
planning_get_record_sharing
Reads the sharing configuration of one specific record, which can differ from its record type.
planning_get_field
Describes a field in detail, including the shape of the values it accepts.
planning_get_view
Returns the full details of a view from its identifier.
planning_get_view_sharing
Checks who can open a specific view and with which rights, independently of the records it shows.
planning_get_template_list
Lists the workspace templates available, with a short summary of each, so you can compare them.
planning_get_template
Details one workspace template from its identifier.
planning_search_resources
Searches workspaces, record types and views by name, across everything you can see in Planning.
planning_search_sharing_data
Finds users, groups, teams, roles and companies by name, the building blocks Claude needs before adjusting any sharing.
planning_search_users
Searches for users in Planning, page by page.
workflow_search_any_object
Searches any Workfront object, such as projects, tasks, issues or hours, with flexible filters, ordering and pagination. It is Claude's main entry point into your work.
workflow_resolve_field_names_any_object
Translates the field names or labels you use into the names Workfront uses internally, so Claude builds accurate requests.
What Claude writes (32)
32 toolsThirty-two tools that create, edit, delete or send. Only the object deletion has a documented confirmation of its own.
approvals_create_or_update_approval_workflow
Approval: see the ruleSets up or reworks the approval stages on a document version, either as one track or as several review paths running side by side.
approvals_create_approval_from_template
Approval: see the ruleStarts an approval workflow on a document from an existing template, including templates with parallel paths.
approvals_delete_approval_stage
Approval: see the ruleDeletes one stage from an approval workflow, chosen by name or by position.
approvals_send_reminder_to_participants
Approval: see the ruleSends reminder emails to chosen participants of an approval stage.
approvals_send_reminder_to_undecided
Approval: see the ruleEmails a reminder to every participant of a stage who has not decided yet, whether they were notified, opened the file or only commented.
approvals_create_template
Approval: see the ruleBuilds a new approval template, with stages that follow each other in a line or depend on one another in a more complex graph.
approvals_update_template
Approval: see the ruleHandles template work at scale: applying templates to assets, building new ones from scratch or from existing flows, editing them, and bulk operations across templates and assets.
planning_create_workspace
Approval: see the ruleCreates an empty Planning workspace, ready to receive record types, fields and data.
planning_create_workspace_from_template
Approval: see the ruleCreates a Planning workspace already filled from an existing template.
planning_update_workspace
Approval: see the ruleEdits part of a workspace: name, description, icon, sections or owner.
planning_delete_workspace
Approval: see the rulePermanently deletes a Planning workspace together with all of its data.
planning_convert_workspace_to_template
Approval: see the ruleSaves an existing workspace as a reusable template for future workspaces.
planning_modify_workspace_sharing
Approval: see the ruleAdjusts who can access a workspace and at which permission level.
planning_create_record_types
Approval: see the ruleAdds one or more record types inside a section of a workspace.
planning_update_record_type
Approval: see the ruleRenames or restyles a record type: name, description, icon or colour.
planning_delete_record_type
Approval: see the ruleWipes out a record type for good, along with all its records, fields and views.
planning_add_global_record_type_to_workspace
Approval: see the ruleLinks a global record type into a workspace so it can be used there.
planning_modify_record_type_sharing
Approval: see the ruleControls who reaches a record type and at which permission level.
planning_bulk_record_actions
Approval: see the ruleCreates, updates, deletes or restores many records in one request.
planning_create_connection_record
Approval: see the ruleCreates a new record in a connected external system, for example a Workfront project linked to a planning record.
planning_update_records_order
Approval: see the ruleChanges the display order of records within a record type.
planning_modify_records_sharing
Approval: see the ruleNarrows or widens access to one or several records, and sets the level.
planning_create_fields
Approval: see the ruleExtends a record type with one or more fields, the columns of the table.
planning_update_field
Approval: see the ruleReworks part of a field: name, description, options or configuration.
planning_delete_field
Approval: see the rulePermanently removes a field and all the data it holds from a record type.
planning_create_view
Approval: see the ruleAdds a table, timeline or calendar view to a record type.
planning_update_view
Approval: see the ruleEdits an existing view's configuration, filters or sorting.
planning_delete_view
Approval: see the ruleGets rid of a view for good; Adobe states that the records themselves are not affected.
planning_modify_view_sharing
Approval: see the ruleOpens or restricts a view to chosen people, at a given permission level.
workflow_create_any_object
Approval: see the ruleCreates a Workfront object: a project, a task, an issue, an hour entry, an assignment, a program or a portfolio.
workflow_update_any_object
Approval: see the ruleEdits an object's fields, and can also relocate a task or issue to another project, turn a task or issue into a project, an issue into a task, or set task predecessors.
workflow_delete_any_object
Asks you firstDeletes a Workfront object from its identifier, with the same effect as deleting it in the Workfront interface.
Not documented (3)
3 toolsThe directory lists these three names, but Adobe's reference has no tool by these exact names. This page will not guess from a name.
approvals_get_documents_by_project
This name is on the directory sheet, but Adobe's tools reference documents no tool by this exact name, and no Claude page covers it. This page adds nothing a source does not say.
approvals_get_adobe_region
Only its name is public, on the directory sheet: no source describes it, neither Adobe's reference nor Anthropic's documentation. Reading a purpose into the name would be making it up.
planning_remove_global_record_type_from_workspace
Adobe documents a tool with a shortened, different name; no official text describes this exact one from the directory sheet. A close name is not proof, so this page states nothing about it.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. Adobe adds one explicit rule: deleting a Workfront object requires your confirmation before it runs.
Adobe is candid that confirmation otherwise depends on the AI platform, not on Workfront, and advises reading what Claude says it is about to do, especially before a delete. On a Team or Enterprise workspace, Claude owners can cap what the connector may do for the whole organisation. On the Workfront side, an admin controls two switches, read tools and write tools. Claude acts with your Workfront access level and object permissions, with the same effect as doing it yourself in Workfront.
Which plans this works on
None of the 819 sheets in the official directory shows plan availability. The per-connector answer is published nowhere, and that is a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organisation before each member can sign in. For the current state of this one, check the Adobe Workfront sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a task runs late or an approval stalls.
Only Adobe documents this connector; neither Claude's help centre nor Anthropic's developer docs have a page on it. The tool list is an observed floor, not a promise, and Adobe's reference already lists tools the sheet lacks. The partner badge is not a security audit, and Anthropic says on every sheet that it does not guarantee how a publisher's tools behave. Adobe adds that you and your AI provider are responsible for what the platform does in Workfront, and that Workfront stores neither prompts nor responses.
Are all the tools on the Workfront directory sheet still active?
- Claude directory sheet ↗September 2026Out of date68 tools, including approvals_find_project_by_name, approvals_get_projects_by_owner and approvals_get_current_user.
- Adobe's Workfront MCP server tools reference ↗September 2026Those three were retired on August 13, 2026, two user and team lookups are deprecated, and several newer tools do not appear on the sheet.
What this page followsAdobe's reference, updated in late September, is the more precise on tool status: the sheet is a snapshot that still shows five tools Adobe has retired or deprecated. This page documents the sheet and flags those five; the list that counts is the one Claude shows once connected.
Need help connecting Adobe Workfront to Claude?
A person reads every message.