Workfront Fusion release activity: Week of October 19, 2026
This page describes all enhancements made in Adobe Workfront Fusion the week of October 19, 2026.
For a list of all recent changes, see Adobe Workfront Fusion release activity.
For a list of recent bug fixes in Workfront Fusion, see the Workfront Maintenance Updates page and check for any updates labeled Workfront Fusion Maintenance Update.
Editable worker pool names
Organization owners and admins can now rename the worker pools assigned to their organization. Until now, each pool showed a fixed, system-generated name. You can now give a pool a custom name, and change it whenever you need to.
For more information, see Worker pools.
New mapping variables
Six new general variables are now available in the mapping panel. They provide ready-to-use scenario and execution links, API URLs, and ownership identifiers, so you can include these values in mapped fields without building URLs or hardcoding team and organization IDs.
scenarioUrl: A link to the current scenario in the Fusion user interface.executionUrl: A link to the current scenario execution in the Fusion user interface.scenarioApiUrl: The Fusion API URL for the current scenario.executionApiUrl: The Fusion API URL for the details of the current execution.teamId: The ID of the Fusion team that owns the current scenario.organizationId: The ID of the Fusion organization associated with the current execution.
These variables extend the existing executionID, scenarioID, scenarioName, triggerTimestamp, and operationsConsumed variables.
For more information, see General functions.
Fusion connector changes
The Workfront Fusion connector now supports more actions for managing your Fusion organization from within a scenario.
New modules and actions
- Clone a record: You can now clone a hook. Use dependencies to map the source hook’s dependencies to the target, as you do when cloning a scenario.
- Delete a record: You can now delete a connection, data store, data store record, data store records (bulk), data structure, hook, key, scenario, or team.
- List records: You can now list DLQs, organizations, teams, and users.
- Read a record: You can now read a DLQ, the current organization, a team, a user, or the authorized user.
- Get record dependencies: You can now get the dependencies of a hook.
- Get record dependents: This new module returns the dependents of data stores, hooks, and scenarios. Run it before deleting a resource to check whether anything depends on it.
Other updates
- Property filters marked as multi-value now accept comma-separated values with the
==and!=operators. Currently, only theidproperty on users supports this (for example,id==123,456). - When deleting a hook’s queue, the
exceptparameter replacesexcludeIdand can be used only when deleting all items. Theidparameter now accepts a comma-separated list. A new 423 response is returned when a delete is already in progress. - When getting scenarios or a single scenario, you can now use the
fieldsparameter to choose which fields are returned.
For more information, see Workfront Fusion modules.
Adobe Fusion MCP connector
The new Adobe Fusion MCP connector lets you send a natural-language prompt to the Adobe Fusion MCP server from within a scenario. A large language model (LLM) interprets your request and calls the Fusion tools needed to complete it.
The connector works only with the hosted Adobe Fusion MCP endpoint.
For more information, see Adobe Fusion MCP modules.