Adobe Workfront Fusion

  OverviewToday we’ve turned on the Fusion MCP server and integrated Fusion with Adobe Coworker. That means you can now interact with your Fusion organization — scenarios, executions, connections, webhooks, data stores, activity logs, and more — via natural‑language in Coworker or any MCP‑compatible agentic platform that supports remote (Streamable HTTP) MCP servers with OAuth.What’s newFusion MCP server is available at https://mcp.fusion.adobe.com/mcp for custom MCP integrations (Claude, ChatGPT, Copilot, Gemini, Cursor, VS Code, and others). Adobe Coworker now includes built‑in Fusion support (standalone Coworker and Coworker in the Fusion right rail). No custom MCP URL or OAuth app registration required for Coworker. All MCP tools described in the Fusion MCP tools reference are exposed to connected agents and follow the same read/write permissions as your Fusion role and team membership.How to get startedChoose the surface you want to use:Coworker (recommended) — Open Coworker (stan

You can now authenticate your Salesforce connections using PKCE (Proof Key for Code Exchange) in addition to standard OAuth 2.0, and enable Refresh Token Rotation for improved long‑term credential security. When creating a Salesforce connection, choose the authentication method from the new Connection type dropdown.OverviewThis update adds two security‑focused options to the Salesforce connector: PKCE for secure, browser‑based authorization flows (recommended for public clients and scenarios where a client secret cannot be safely stored), and Refresh Token Rotation (RTR) to automatically rotate refresh tokens and reduce risk from long‑lived credentials. What’s newPKCE (Proof Key for Code Exchange) — Authenticate without a client secret by using a code verifier/challenge flow. Useful for public clients or environments where storing a client secret is not desirable. Refresh Token Rotation (RTR) — Optionally enable RTR for Salesforce connections so refresh tokens are rotated on each use.

Save time writing scenario summaries — click Describe with AI in a scenario’s Settings panel and Fusion will generate a clear, human‑readable description for you automatically, based on the modules and configuration in the scenario.OverviewThis release adds a Describe with AI action to the Description field in a scenario’s Settings panel. When invoked, Fusion analyzes the modules, connections, triggers, and mapped outputs in the scenario and produces a concise description you can accept, edit, or discard. The feature is designed to help teams keep scenario metadata accurate and useful without having to compose descriptions manually. What’s newDescribe with AI button — One‑click generation of a scenario description from the Settings panel description field. Context‑aware summaries — The generated text reflects the scenario’s modules, triggers, key connections, and primary outputs so descriptions are actionable and relevant. Edit and accept flow — Generated descriptions are presented in

You can now access your Fusion objects from inside a scenario. The new Workfront Fusion connector lets scenarios call Fusion’s own API to create, inspect, modify, and operate Fusion resources.OverviewThis release introduces a first‑party Workfront Fusion connector that exposes Fusion APIs directly inside the scenario canvas. Use it to back up or clone scenarios, inspect dependencies, export activity logs, and gather operational telemetry — all as part of your automation flows.What’s newFull record lifecycle — Create, read, update, delete, list, and clone Fusion records from scenarios. Dependency insights — Retrieve a record’s dependencies so you can understand or safely update resources that are referenced elsewhere. Activity exports — Export activity logs for auditing, troubleshooting, or archival workflows. Queue and hook visibility — List hook queues, read queue items, and get queue statistics to monitor trigger backlogs and failure patterns. Connection & scenario mapping — List

Two new MCP connectors bring conversational, model-driven automation to Fusion. Instead of wiring together many individual modules, a single MCP module accepts an open-ended instruction and lets an AI model determine which Workfront or AEM operations are needed to fulfill it.OverviewThis release adds two first‑party connectors that speak to Adobe's Model Context Protocol (MCP) server: Adobe Workfront MCP and Adobe AEM MCP. Each connector exposes a single, flexible module you place on a scenario canvas and drive with natural‑language instructions (prompts). The MCP module synthesizes the required API calls, executes them, and returns a consolidated, human‑readable result — reducing the need to build long chains of Get/Filter/Transform/Write modules for many common tasks.What’s newSingle conversational module — One module accepts an instruction and lets the MCP model plan and run the necessary Workfront or AEM operations, returning a synthesized answer or structured output. Task examples

New: A faster way to see what broke — Failed Executions Logs in the Insights dashboardWhen multiple scenarios fail across your org, tracking down how many, which ones, and why used to mean opening scenarios one-by-one. The new Failed Executions Logs widget surfaces every failed execution across every scenario in a single table so you can triage incidents fast, at scale.OverviewThe Failed Executions Logs widget lives on the new Insights page (which now also contains the Performance widget). It aggregates failed executions across your organization into a single, filterable table so you get the full picture quickly — no more stitching together results from individual scenario pages.What’s newCentralized failure list — See every failed execution across every scenario in your organization in one table. Powerful filters — Filter by team, scenario, type, error message, and date range. Each filter supports "only these" or "everything except these" to help narrow or exclude results quickly. Rea

Workfront Fusion — Native Adobe Storage (ESM) supportWorkfront Fusion now natively supports Adobe Storage (ESM)Workfront Fusion now connects directly to Adobe cloud storage (Enterprise Storage Management, ESM). Browse and upload assets inside Fusion, automate store lifecycle and access, and generate presigned URLs for secure read/write integrations with external systems.OverviewThis release adds native Adobe Storage support in Fusion using the same ESM layer that powers the Workfront/Frame.io unified review and approval experience and is shared across Frame.io, Document Cloud, and Creative Cloud. You’ll see a new Storage navigation menu for browsing and uploads, plus Adobe Storage modules you can use in scenarios to manage stores, collaborators, and presigned URLs.What’s newStorage navigation — A new Storage menu item in Fusion to browse ESM stores and upload files without leaving the app. Store lifecycle — Create, discard, restore, and delete ESM stores from scenarios for automated pr

Packages is now generally available in Workfront Fusion — build and run your own custom JavaScript functions, backed by Adobe App Builder, and use them directly in your scenario mappings.OverviewPackages let you build and run your own custom logic inside Fusion, without leaving the Fusion interface. When the standard modules don't do exactly what you need, you can write a function to transform data, do a calculation, call an external service, or wrap a routine you want to reuse — then test it, publish it, and call it from your scenarios. A package can bundle everything a function needs: the function itself, reusable variables (like a base URL or API key), outside library dependencies, and automatic version history.What's newFunctions — Write custom logic in JavaScript, define typed inputs, test drafts safely before publishing, and republish or unpublish live functions as needed. Variables — Store reusable values (URLs, IDs, keys) once and reference them across functions. Mark variables

Connect Azure DevOps to Workfront Fusion using a service principalYou can create a connection that uses a service principal (an Application API connection) instead of a personal account. Use this when you want the integration to run as an application or service identity rather than a specific person — for example, to avoid breakage when someone leaves the company or changes credentials. This connection type is available for all Azure DevOps modules.OverviewService principal connections let Fusion authenticate to Azure DevOps as an application identity (an app registration in Microsoft Entra ID) using a client secret. After you register the app and add it as a user in your Azure DevOps organization, create a Service Principal connection in the Azure DevOps module and provide the Tenant ID, Client ID, Client Secret, and organization name.NOTE: Service principal authentication does not support every Azure DevOps feature. A small number of admin-level actions — for example, managing user l