Adobe Workfront

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

 Workfront Fusion Custom UI extensions OverviewFusion can display your own web UI inside its interface. Build a small web app (a guest extension), publish it via Adobe App Builder, and Fusion will show a new menu item in its navigation that opens your UI in the main canvas. The guest automatically receives context such as the signed‑in user, organization, team, and other metadata so your extension can adapt to the current environment.The technology underneathYour guest is built with two Adobe technologies:Adobe App Builder — Free hosting and tooling for small web apps and serverless actions. App Builder hosts your static UI on Adobe’s CDN and provides the aio CLI to create, build, and publish the app. Adobe UI Extensibility SDK (UIX) — The libraries that let host and guest talk. Use @adobe/uix-guest in your guest; Fusion uses @adobe/uix-host on its side.Extension pointsAn extension point is a named slot in Fusion where a guest may appear. Extension point names use the format: service/n

 Search input and output bundles in scenario executionsPreviously you could not search the actual input and output bundles shown in an execution. Now you can search both input and output bundles directly from the execution UI — use the module/filter output search bars or the execution search to find specific bundle content, IDs, or events.OverviewWe’ve added the ability to search the text and metadata inside bundle payloads for both inputs and outputs in an execution. This makes it much faster to locate a particular bundle, debug processing logic, or verify that expected data passed through a specific step. You can search at the module/filter level or across the entire execution timeline.What’s newSearch the contents of input bundles shown for a module or filter. Search the contents of output bundles shown for a module or filter. Combine content searches with status filtering to surface only Success, Warning, Failed, Passed, or Failed bundles as applicable.How to search bundle contentO

 Set team or scenario notification options for IMS organizationsIMS organizations can now enable or disable each notification type independently at the team level — the same fine-grained controls previously available only to non‑IMS organizations. Scenario-level notification settings continue to override team settings when present.OverviewTo give teams finer control over the notifications they receive, administrators and team managers in IMS organizations can now choose which situations trigger Fusion notifications. Instead of a single on/off switch for all notifications, you can toggle each notification type independently:Notify on warning — Send a notification when a scenario execution logs a warning. Notify on error — Send a notification when a scenario execution fails. Notify when scenario is disabled — Send a notification when Fusion auto‑deactivates a scenario (for example, after too many consecutive errors).Scenario-level notification settings still take precedence over team-lev

 Adobe Express connector now available in Workfront FusionWe’ve added a new Adobe Express connector so you can automate common Express workflows—like listing tagged documents, creating variations, exporting renditions, and checking operation status—directly from Workfront Fusion integrations and automations.OverviewThe Adobe Express connector exposes the primary Express API surface so you can programmatically interact with Express documents and tagged elements from your Fusion scenarios. The connector maps the Express API endpoints into modules that make it easy to include Express operations in integration flows, automation canvases, and scheduled jobs.Connector capabilities (API endpoints)Tagged documents — List all documents that contain tagged elements so you can discover assets to process. Tagged document details — Retrieve metadata and the tagged-element structure for a specific document to inspect editable regions and element IDs. Generate variation — Create new document variatio

 Product update:mTLS support for custom webhooksTo meet stronger security requirements, you can now use mutual TLS (mTLS) with custom webhooks. Add a client certificate and private key to a webhook so Experience League integrations and automations authenticate to the receiving service using client-side TLS credentials.OverviewCustom webhooks now support Client certificate authorization. When you configure a webhook to use a client certificate, Fusion will present that certificate and private key during the TLS handshake so the remote service can verify the client. This provides an extra layer of security for server-to-server webhook delivery when the endpoint requires mTLS.How to configure mTLS for a webhookOpen the Add a hook dialog for the webhook you want to create or edit and check Show advanced settings. Under Authorization type, select Client certificate. In the Credentials field, click Add. This opens the Create a key dialog. Give the key a descriptive Key name (for example, “My

Product update: Workfront Planning v2 connectorWorkfront Planning v2 connector now availableWe’ve released a new connector that exposes the expanded capabilities of the Workfront Planning API version 2 so you can automate and integrate Workfront Planning resources directly from Experience League integrations and workflows.OverviewThe new Workfront Planning v2 connector adds modules that map to the Planning API v2 surface so you can programmatically manage Workfront Planning workspaces, record types, records, fields, and access workflows. The connector also includes user and permission queries and a generic custom-call module so you can call any remaining endpoints not covered by the dedicated modules.What you can do with the Workfront Planning v2 modulesCreate, read, update, and delete workspaces, record types, records, and fields. Retrieve user-level info such as authorization ID and permissions. Request access to a resource and view pending access requests. Make custom API calls to a

Product update: View and compare scenario versionsThis post introduces a new Review changes experience that makes it easy to see exactly what changed between two versions of a scenario so you can confidently restore older versions when needed. OverviewYou can now open a side-by-side comparison of any two versions of the same scenario to view detailed differences before you restore a version. The Review changes view highlights additions, removals, and edits (colored green and red) and groups changes by logical sections (Scenario, Scenario settings, Modules, Flows, Router routes, Error handlers, and Orphan groups). Restoring a version creates a new version, so all restores are reversible.How to compare scenario versionsClick Scenarios in the left panel and open the scenario you want to inspect. Click the More icon at the bottom of the screen, then choose Previous Versions. From the list of previous versions, click View changes for the version you want to compare. The Review changes panel