Resources · Claude connector

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

Overview

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.

Vocabulary

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

Connect Adobe Workfront to Claude in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (33)

33 tools

Thirty-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.

When it helps
a reviewer mentions "the spring banner" and you need the exact document before checking its approval.
Watch out
two files with close names can both match; confirm which one Claude picked.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

approvals_get_document_by_version_id

Fetches the details of a document version Claude already identified: name, size, upload date and who uploaded it.

When it helps
you want to confirm the file under review is the one the agency sent on Tuesday, not an older upload.
Watch out
it needs the version identifier first, usually found by a search.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
you want the approval status of every asset in a campaign folder, not just one file, before a launch meeting.
Watch out
large folders mean long lists; narrow the scope when you can.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
legal says they never saw the video; you want to know which stage it sits in and who is still expected to decide.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
you want to know which review template your team relies on most before standardising the process.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

approvals_search_template_by_name

Finds approval templates from part of their name, whatever the case.

When it helps
someone mentions the "Marketing Launch" template and you want Claude to locate it before applying it to an asset.
Watch out
partial matches may return several templates; check the one retained.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
rarely now; if Claude reports it unavailable, that retirement is the reason.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
you want the right person added as approver and only remember their first name.
Watch out
deprecated tools may stop working; the directory sheet still shows it.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
you want to add the whole creative team as approvers and need Workfront's exact team record first.
Watch out
Adobe no longer recommends it, yet the directory sheet still lists it.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
historically, finding a project before listing its documents; today another tool does this job.
Watch out
expect Claude to report it unavailable.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
it once listed the projects you own; ask the same question and Claude will pick a current tool.
Watch out
the directory sheet has not caught up with this retirement.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_workspace

Retrieves the full details of a Planning workspace from its identifier or alias.

When it helps
you want to see how the marketing planning workspace is organised before asking Claude to add anything to it.
Watch out
Planning tools need a Workfront package that includes Adobe Workfront Planning.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_workspace_list

Lists every Planning workspace available to you, page by page.

When it helps
you have just joined and want to see which planning workspaces exist across brands and regions before digging into one.
Watch out
long lists arrive in several pages.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_workspace_sharing

Shows who has access to a workspace and at which permission level, the starting point of any sharing question.

When it helps
before an external agency joins, you want to check who can already see the planning workspace and with which rights.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_record_type

Fetches everything about a record type, including its fields and views, the blueprint behind every record of that kind.

When it helps
you want to know which fields a "Campaign" record carries before asking Claude to fill or filter them.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_list_global_record_types

Lists the record types defined centrally for the whole organisation that you are allowed to see, shared across workspaces.

When it helps
you want to know whether a shared "Budget line" type already exists before someone builds a local copy in their own workspace.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_list_addable_global_record_types

Tells Claude which global record types can still be added to a given workspace.

When it helps
you are setting up a new workspace and want to see which company-wide types it could reuse instead of inventing its own.
Watch out
actually linking one goes through planning_add_global_record_type_to_workspace, a separate tool.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_external_record_workspaces

Finds which workspaces and record types are connected to a given external record, such as a Workfront project.

When it helps
you want to know where a Workfront project is referenced across planning workspaces before anyone touches its name.
Watch out
it reads links, it does not follow them into the other workspaces.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_record_type_sharing

Reports who can access a specific record type and at which level, separately from the workspace itself.

When it helps
a colleague says she cannot see the "Budget" records; you want to check the sharing of that type first.
Watch out
record-level sharing can still differ; check the record too.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_record

Opens one record in full from its identifier, every field included.

When it helps
you want every field of the "Q2 Marketing Plan" record in front of you before a planning review, without opening Workfront or scrolling a table.
Watch out
it needs the record's identifier, usually found by a search.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_search_records

Searches and filters the records of a record type.

When it helps
you want every campaign record scheduled for next quarter with a budget above a given threshold.
Watch out
filters rely on the field names of the record type; Claude may look them up first.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_record_change_log

Returns the field-level history of a record, field by field and revision by revision.

When it helps
a launch date shifted and nobody remembers when it moved or from which date; the history of the record answers without a round of emails.
Watch out
it covers one record at a time, found beforehand.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_record_sharing

Reads the sharing configuration of one specific record, which can differ from its record type.

When it helps
a single sensitive record should be visible to three people only, and you want to confirm that before a meeting.
Watch out
it covers one record; the type may say something else.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_field

Describes a field in detail, including the shape of the values it accepts.

When it helps
before asking Claude to fill a dropdown on many records, you want the list of values the field actually allows, spelled exactly.
Watch out
the field is identified by its ID, found beforehand.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_view

Returns the full details of a view from its identifier.

When it helps
you want to understand why the team's timeline view hides some campaigns, starting with its filters and sort order.
Watch out
it describes the view, not the records inside it.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_view_sharing

Checks who can open a specific view and with which rights, independently of the records it shows.

When it helps
you built a leadership view and want to confirm it is not visible to the whole workspace yet, before the numbers are final.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_template_list

Lists the workspace templates available, with a short summary of each, so you can compare them.

When it helps
ahead of a new regional workspace, you want to see which templates exist and what they contain.
Watch out
the summaries are short; open one template for the full picture.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_get_template

Details one workspace template from its identifier.

When it helps
you want to know exactly which record types and views a template brings before building a workspace from it.
Watch out
it reads the template only; nothing is built from it here.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_search_resources

Searches workspaces, record types and views by name, across everything you can see in Planning.

When it helps
you remember a "Budget tracker" view somewhere but not in which workspace it lives, nor who built it.
Watch out
it matches names, not the content of records.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_search_sharing_data

Finds users, groups, teams, roles and companies by name, the building blocks Claude needs before adjusting any sharing.

When it helps
you ask to share a workspace with the EMEA marketing team and Claude must first find that exact team.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_search_users

Searches for users in Planning, page by page.

When it helps
you want to check whether a new hire already has a Workfront account before giving them planning access.
Watch out
finding a user is not sharing anything with them; that is another tool.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
you ask for every active project of the brand marketing team, or every task assigned to one colleague this week.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

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.

When it helps
you say "planned completion" and Claude needs Workfront's own field name to filter on it.
Watch out
a technical helper; you will rarely see it.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

What Claude writes (32)

32 tools

Thirty-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 rule

Sets up or reworks the approval stages on a document version, either as one track or as several review paths running side by side.

What Claude asks for
No source describes a confirmation specific to this tool; the general approval rule applies.
When it helps
a new brand guideline adds a compliance review and the stages of a document must reflect it.
Watch out
writes only work once your Workfront admin has enabled write tools.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

approvals_create_approval_from_template

Approval: see the rule

Starts an approval workflow on a document from an existing template, including templates with parallel paths.

What Claude asks for
nothing documented for this tool alone; Claude's default approval covers it.
When it helps
your team always reviews launch videos the same way, and you want that routine applied to today's asset in one sentence.
Watch out
pick the template by name carefully; similar names are common.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

approvals_delete_approval_stage

Approval: see the rule

Deletes one stage from an approval workflow, chosen by name or by position.

What Claude asks for
Adobe leaves confirmation to the AI platform, so Claude's general rule is what applies here.
When it helps
a stakeholder left the project and the stage built around them no longer makes sense.
Watch out
Adobe only allows it on stages that have not started yet.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

approvals_send_reminder_to_participants

Approval: see the rule

Sends reminder emails to chosen participants of an approval stage.

What Claude asks for
no tool-specific confirmation is published; see the approvals section below.
When it helps
two approvers are holding up a print deadline and you want to nudge them without writing the email yourself.
Watch out
it only works on stages that are started, not completed and not locked.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

approvals_send_reminder_to_undecided

Approval: see the rule

Emails a reminder to every participant of a stage who has not decided yet, whether they were notified, opened the file or only commented.

What Claude asks for
the general approval rule, since neither Adobe nor Anthropic describes one for this tool.
When it helps
a campaign video still waits on half its reviewers and you want one reminder to reach all of them at once.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

approvals_create_template

Approval: see the rule

Builds a new approval template, with stages that follow each other in a line or depend on one another in a more complex graph.

What Claude asks for
Claude's default confirmation, as no source sets a rule of its own for this tool.
When it helps
your process now has a fixed sequence of brand, legal and client review, and you want it reusable for every future asset.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

approvals_update_template

Approval: see the rule

Handles 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.

What Claude asks for
No source describes a confirmation specific to this tool; the general approval rule applies.
When it helps
a new approver joins every brand review and all your templates must include her.
Watch out
bulk edits reach many assets at once; read Claude's plan before you agree.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_create_workspace

Approval: see the rule

Creates an empty Planning workspace, ready to receive record types, fields and data.

What Claude asks for
nothing documented for this tool alone; Claude's default approval covers it.
When it helps
a new product line needs its own planning space, separate from the existing brand workspaces.
Watch out
an empty workspace still needs record types before it is useful.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_create_workspace_from_template

Approval: see the rule

Creates a Planning workspace already filled from an existing template.

What Claude asks for
Adobe leaves confirmation to the AI platform, so Claude's general rule is what applies here.
When it helps
each regional team gets the same campaign planning structure, and you want the next region set up the standard way.
Watch out
the template shapes everything; check which one Claude uses.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_update_workspace

Approval: see the rule

Edits part of a workspace: name, description, icon, sections or owner.

What Claude asks for
no tool-specific confirmation is published; see the approvals section below.
When it helps
the workspace owner is leaving and responsibility passes to a colleague.
Watch out
owner transfers matter; confirm the new owner's name before approving.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_delete_workspace

Approval: see the rule

Permanently deletes a Planning workspace together with all of its data.

What Claude asks for
the general approval rule, since neither Adobe nor Anthropic describes one for this tool.
When it helps
a test workspace from a pilot is cluttering the list and nobody needs its content.
Watch out
Adobe describes the deletion as permanent; nothing in its page mentions a way back.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_convert_workspace_to_template

Approval: see the rule

Saves an existing workspace as a reusable template for future workspaces.

What Claude asks for
Claude's default confirmation, as no source sets a rule of its own for this tool.
When it helps
last year's launch workspace worked well and you want every new launch to start from that structure.
Watch out
Adobe says it requires admin rights in Workfront.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_modify_workspace_sharing

Approval: see the rule

Adjusts who can access a workspace and at which permission level.

What Claude asks for
No source describes a confirmation specific to this tool; the general approval rule applies.
When it helps
a freelance planner joins for three months and needs view access to the campaign workspace only.
Watch out
sharing changes take effect as if you made them in Workfront yourself; check the level Claude proposes.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_create_record_types

Approval: see the rule

Adds one or more record types inside a section of a workspace.

What Claude asks for
nothing documented for this tool alone; Claude's default approval covers it.
When it helps
your planning now tracks influencer partnerships and they deserve their own record type next to campaigns.
Watch out
new types start empty; fields come next.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_update_record_type

Approval: see the rule

Renames or restyles a record type: name, description, icon or colour.

What Claude asks for
Adobe leaves confirmation to the AI platform, so Claude's general rule is what applies here.
When it helps
the team renamed "Initiatives" to "Programs" and the workspace should say the same thing.
Watch out
renaming affects how everyone sees the type across the workspace.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_delete_record_type

Approval: see the rule

Wipes out a record type for good, along with all its records, fields and views.

What Claude asks for
no tool-specific confirmation is published; see the approvals section below.
When it helps
an abandoned record type from an old process still shows up and confuses new team members.
Watch out
it takes every record of that type with it; there is no partial deletion.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_add_global_record_type_to_workspace

Approval: see the rule

Links a global record type into a workspace so it can be used there.

What Claude asks for
the general approval rule, since neither Adobe nor Anthropic describes one for this tool.
When it helps
the finance team's shared budget type should appear in the marketing workspace too.
Watch out
the link brings the shared definition, not a private copy.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_modify_record_type_sharing

Approval: see the rule

Controls who reaches a record type and at which permission level.

What Claude asks for
Claude's default confirmation, as no source sets a rule of its own for this tool.
When it helps
the finance records should be visible to managers only, not to the whole workspace.
Watch out
permissions apply to every record of the type.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_bulk_record_actions

Approval: see the rule

Creates, updates, deletes or restores many records in one request.

What Claude asks for
No source describes a confirmation specific to this tool; the general approval rule applies.
When it helps
twenty campaign records need the same new owner after a reorganisation.
Watch out
one request touches many records; read Claude's summary of what will happen before you agree.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_create_connection_record

Approval: see the rule

Creates a new record in a connected external system, for example a Workfront project linked to a planning record.

What Claude asks for
nothing documented for this tool alone; Claude's default approval covers it.
When it helps
a planning record was approved and should now become a real Workfront project that teams can execute.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_update_records_order

Approval: see the rule

Changes the display order of records within a record type.

What Claude asks for
Adobe leaves confirmation to the AI platform, so Claude's general rule is what applies here.
When it helps
leadership wants campaigns listed by priority, not by creation date, in the planning view.
Watch out
it affects presentation, not the content of the records.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_modify_records_sharing

Approval: see the rule

Narrows or widens access to one or several records, and sets the level.

What Claude asks for
no tool-specific confirmation is published; see the approvals section below.
When it helps
a confidential acquisition campaign must be hidden from everyone outside the core team.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_create_fields

Approval: see the rule

Extends a record type with one or more fields, the columns of the table.

What Claude asks for
the general approval rule, since neither Adobe nor Anthropic describes one for this tool.
When it helps
the team now needs to track the agency in charge of each campaign, as a new column.
Watch out
new fields are empty on existing records.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_update_field

Approval: see the rule

Reworks part of a field: name, description, options or configuration.

What Claude asks for
Claude's default confirmation, as no source sets a rule of its own for this tool.
When it helps
a dropdown of campaign statuses needs a new "On hold" option.
Watch out
renaming or removing options can affect existing values; check the plan first.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_delete_field

Approval: see the rule

Permanently removes a field and all the data it holds from a record type.

What Claude asks for
No source describes a confirmation specific to this tool; the general approval rule applies.
When it helps
an old "Legacy code" column nobody fills any more clutters every view.
Watch out
the values go with it; export them first if you might need them.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_update_view

Approval: see the rule

Edits an existing view's configuration, filters or sorting.

What Claude asks for
Adobe leaves confirmation to the AI platform, so Claude's general rule is what applies here.
When it helps
the weekly review view should only show campaigns launching in the next month, sorted by date.
Watch out
shared views look different for everyone after the edit.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

planning_modify_view_sharing

Approval: see the rule

Opens or restricts a view to chosen people, at a given permission level.

What Claude asks for
the general approval rule, since neither Adobe nor Anthropic describes one for this tool.
When it helps
the leadership view is ready and the directors should now get access to it.
Watch out
view access does not replace record permissions.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

workflow_create_any_object

Approval: see the rule

Creates a Workfront object: a project, a task, an issue, an hour entry, an assignment, a program or a portfolio.

What Claude asks for
Claude's default confirmation, as no source sets a rule of its own for this tool.
When it helps
a new sandbox project must start on a given date with you as owner, and a first task inside it.
Watch out
write tools are off by default until your Workfront admin enables them.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

workflow_update_any_object

Approval: see the rule

Edits 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.

What Claude asks for
No source describes a confirmation specific to this tool; the general approval rule applies.
When it helps
the design review slips to next Friday and development should start once design finishes.
Watch out
Adobe says these actions have the same effect as making them yourself in the Workfront interface.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

workflow_delete_any_object

Asks you first

Deletes a Workfront object from its identifier, with the same effect as deleting it in the Workfront interface.

What Claude asks for
Adobe states this tool requires your explicit confirmation before the deletion runs.
When it helps
an old test campaign project is still counted in the team's workload.
Watch out
Adobe advises checking exactly what is about to be deleted before you confirm.

Sourceexperienceleague.adobe.com · September 25, 2026 ↗

Not documented (3)

3 tools

The 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.

Watch out
the general approval rule covers it.

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.

Watch out
it falls under the same general approval rule as every tool.

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.

Watch out
Claude's default approval applies to it, whatever it does.
Approvals

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.

Plans

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.

Limits

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.

Two official sources disagree

Are all the tools on the Workfront directory sheet still active?

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

Need help connecting Adobe Workfront to Claude?

A person reads every message.

FAQ

FAQ about the Claude Adobe Workfront connector

01What can Claude do with the Claude Adobe Workfront connector?
Claude can find and manage Workfront work from a conversation. Thirty-three read tools look up documents and their approvals, approval templates, Planning workspaces, record types, records, fields, views and sharing, and search any Workfront object. Thirty-two write tools create, edit or delete projects, tasks and other objects, build and adjust approval workflows, send reminders to approvers, and restructure Planning. Three more appear on the directory sheet without any official description. Writes only work after a Workfront admin enables them.
02Can Claude create, change or delete things in Workfront?
Yes, 32 of the 68 tools write, but only once your Workfront admin has turned on the write tools, which are off by default. Claude can then create projects, tasks, issues, hours and portfolios, edit their fields, relocate tasks, set dependencies, delete objects, manage approval stages and templates, email reminders to approvers, and create, edit or delete Planning workspaces, record types, fields and views. Adobe states that these actions have the same effect as doing them yourself in the interface.
03Does Claude ask before acting in Workfront?
For deletions of Workfront objects, yes: Adobe documents that this tool requires your explicit confirmation before it runs. For the other write tools, no source sets a specific rule, so Claude's default applies: it asks before actions it takes on an account for you. Adobe itself says confirmation depends on the AI platform, not on Workfront, and recommends reading what the assistant intends to do before approving, especially when data is about to be deleted.
04Which plans is the Adobe Workfront connector available on?
No official source publishes availability per plan, connector by connector, and no directory sheet shows it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner must switch the connector on before members can sign in individually. The connector's sheet in the official directory is the only place that shows its current state for your account, so check it there.
05Does Claude see everything in our Workfront instance?
No, only what your own Workfront account can reach. Adobe says the platform acts with your access level and object permissions, so you can do nothing through Claude that you could not already do in Workfront. Each connection is tied to one instance, chosen through the profile you pick when signing in. A Workfront admin controls whether read and write tools are switched on at all. Separately, a Claude owner on Team or Enterprise can restrict what connectors may do.
06Why can Claude find Workfront items but not update them?
Because the Write MCP tools switch is off by default on the Workfront side. Adobe ships read tools enabled and write tools disabled, and only a Workfront administrator can turn writes on in System Preferences. Adobe's guidance for that exact symptom is to ask your Workfront administrator to enable write actions. Keep in mind that Claude acts with your own Workfront permissions, so an item you cannot edit yourself stays closed to it as well.
07Claude or an automation tool for Adobe Workfront?
They answer different needs, so it depends on the job. Claude works inside a conversation: you ask for overdue tasks or a stalled approval, it finds, reschedules or reminds, and nothing happens once you stop typing. It does not react on its own when a task goes late or a document is uploaded. Anything that must run on a schedule or on an event belongs to an automation tool. For on-demand status checks and quick fixes, the connector is the better fit.