Adobe Workfront Fusion

OverviewWe’ve made several focused improvements to the new scenario designer to speed up editing on wide monitors, make it obvious which module or filter you’re working on, and let you search across mappings, module settings, and filters. These changes reduce mouse travel for large canvases, keep your context steady while you edit, and help you quickly find where a value is used.Applies toThese updates apply only to the new scenario designer. To use them, toggle Try the new design in the scenario editor. The classic designer is unchanged.What’s newResizable right‑hand panel — drag the left edge of the right panel to make it wider or narrower; double‑click the edge to reset. The width you set is saved to your user preference so your workspace stays consistent across sessions. Canvas stable while editing — opening a module no longer recenters or shifts the canvas. This keeps your position on large screens and reduces panning and mouse movement while you make edits. Clear edit highlights

OverviewWe’ve added an AI‑powered explanation layer that gives short, plain‑language descriptions of errors and suggested fixes alongside the original error details. Read the raw error and the AI explanation together so troubleshooting is faster and more approachable for everyone on your team. What’s newAI explanations next to errors — concise, human‑readable summaries and recommended actions appear next to the original error message so you see both context and guidance in one place. Where explanations appear — available in three locations: Scenario designer: inside a module’s error details panel. Scenario execution history: on the failed run’s details page; when multiple modules failed you can request an explanation per module. Insights page: in the Failed executions table so triage from Insights is faster. Per‑error granularity — request explanations for individual module errors in a run so you can focus on the most critical failures. Human‑friendly remediation steps — suggestions

OverviewThe Insights page has been updated to make it faster and easier to find the information you need. This release adds page customization, a global widget refresh, a first‑time guided tour, improved search matching, dark mode support, tighter access for the Performance widget, and deep links that open Organization Operations pre‑filtered for a scenario and team.What’s newCustomize the page — show or hide widgets and reorder them to surface the metrics that matter most to you. Refresh all widgets — a single control reloads data for every widget on the page while preserving each widget’s filters and state. Search by ID — the Organization Operations and Top Scenarios by Operations widgets now match Scenario and Team on ID as well as name, improving discoverability when names change or duplicates exist. Dark mode — the Insights page and its widgets follow your account or system dark mode setting for a consistent visual experience. Performance widget access — the Performance widget is

 OverviewWe’ve expanded Workfront Fusion’s API observability so you can monitor scenario executions in far greater detail from your own tools. The October release adds two new execution endpoints, exposes new monitoring fields on existing endpoints, and removes the requirement to scope execution listings to a single scenario. Use these capabilities to build alerts, aggregate errors, and troubleshoot runs without switching to the Fusion UI.What’s newGet Execution Details — GET /api/v3/logs/{executionId}/details returns a paginated list of an execution’s activity events (messages, warnings, errors, timestamps) so you can replay the timeline that led to a failure. Get Execution Bundles — GET /api/v3/logs/{executionId}/bundles returns module-level input and output bundles for a single execution, ordered by cycle → module → operation. Inspect the exact data each module received and produced. deactivated & deactivationReason — new fields indicate whether an execution deactivated its scen

OverviewThe Adobe CX Coworker connector for Workfront Fusion lets you call Adobe CX Enterprise Coworker from an automation scenario. Instead of building API calls and parsing JSON yourself, send a plain‑language prompt and let Coworker interpret the request, run the applicable skills, and return a conversational result you can use later in the flow.The connector provides two modules:Run a Prompt — Starts a new Coworker request. By default this module waits for Coworker to finish and returns the result, including both the natural‑language summary and any structured outputs the skill produced. Get Execution Status — Polls an earlier request to check progress or retrieve a result if you started the prompt asynchronously. Use this when you want non‑blocking execution or to coordinate long‑running checks across systems.ImpactThe Coworker connector dramatically reduces the complexity of integrating AI‑driven insights and data validation into automation scenarios. Use cases include:Automatica

OverviewThe new Scenario editor experience gives you a faster, more focused way to build, navigate, and debug scenarios. The underlying scenario behavior—mappings, filters, schedules, connections, routers, error handlers, and execution—remains unchanged when you switch experiences. You can toggle back to the classic editor at any time. If you don’t see the toggle, the new experience may not yet be enabled for your organization. What’s newModule cards — compact cards show app icon, module name, short description, and module ID with curved links and status indicators for clearer canvas readability. Improved navigation — Compact view, zoom, Focus mode, and a minimap make it easier to move around and reason about large scenarios. Use cmd/ctrl + K for fast search. You can navigate between executions with a single click. Foldable routers — Collapse a router to hide its routes and reduce visual noise while you work on other parts of the scenario. Dark mode — Editor color theme for low‑light w

OverviewThe new Adobe Fusion MCP connector lets you send a plain‑English prompt from a Fusion scenario to the hosted Adobe Fusion Model Context Protocol (MCP) server. An LLM interprets your request, invokes the Fusion tools required to fulfill it, and returns the result plus execution metadata.What’s newSingle‑prompt MCP integration — send one natural‑language instruction to the hosted Fusion MCP server directly from a scenario module. Optional BYO LLM — use Adobe Managed AI by default, or supply an LLM key (OpenAI, Anthropic, Amazon Bedrock) and model if you prefer a different provider. Tool restrictions — restrict which read‑only and write/delete Fusion tools the MCP model may call to enforce least privilege for unattended runs. Audit and summary outputs — the module returns a Response, an Audit Trail of tool calls and results, and a Summary (counts and final status) for transparency and downstream logic.How it works (quick)Add the Adobe Fusion MCP module to your scenario. Create a c

 OverviewTo reduce reliance on long‑lived secrets and make connections more secure and manageable, we’ve added federated connection support to the AWS S3, Azure DevOps, and SharePoint connectors in Fusion. You can now authenticate these connectors using your organization’s identity provider (Azure AD / Microsoft Entra ID or AWS IAM federation) so Fusion obtains short‑lived credentials at runtime instead of storing client secrets or static keys.What’s newFederated connection option — a new connection type for AWS S3, Azure DevOps, and SharePoint that uses your identity provider to mint temporary credentials or tokens. Consistent auth model — setup follows the same federated/OIDC or IAM role pattern you already use for other Azure AD or AWS identity integrations. No long‑lived secrets — Fusion uses short‑lived tokens/credentials returned by your IdP or AWS STS, reducing secret sprawl and rotation overhead. Admin controls — organizations can enforce which identity providers and roles are

 OverviewYou can now connect Workfront Fusion directly to the Adobe Marketo Engage MCP server using the new Adobe Marketo Engage MCP connector. The connector exposes an instruction‑driven module that lets you provide open‑ended, plain‑English instructions; an AI agent then determines and executes the Marketo actions required to fulfill your request.What’s newAdobe Marketo Engage MCP connector — a new connector that talks to the Marketo MCP server and exposes Marketo tools to MCP‑compatible agents. Instruction module — enter free‑form, plain‑English instructions (for example, “Create a nurturing program for new trial users in EMEA and add a 3‑step email sequence”) and let the agent translate them into concrete Marketo operations. Action restrictions — admins can explicitly limit which read, write, and delete actions the agent is allowed to perform so unattended runs remain within the approvals you set. AI provider flexibility — by default the module uses Adobe’s managed AI service; you

OverviewWe’ve added a new HTTP module: HTTP > Make a JWT request. This module mirrors the behavior of the existing HTTP > Make a request module but builds, signs, and injects a short‑lived JSON Web Token (JWT) based on the claims you provide. By default the signed JWT is sent as an Authorization: Bearer <jwt> header so you can call APIs that require signed JWT authentication without a separate token‑generation step in your scenario.What’s newMake a JWT request module — a new HTTP module that creates, signs, and attaches a JWT to the outgoing request. Claims input — provide standard and custom claims (iss, sub, aud, exp, nbf, jti, and custom claims) in the module UI. Automatic signing — the module signs the JWT with the key material you supply and inserts it into the request (default: Authorization Bearer). Request parity — supports the same HTTP method, headers, body, query, timeout, and retry controls you already use in the HTTP Make a request module.How it worksOpen your

 OverviewWe’ve added a new field to the HTTP modules: Additional Retry Status Codes. This lets you list extra HTTP response codes that should be treated as retryable connection errors when Evaluate all states as errors (except 2xx and 3xx) is enabled. Previously Fusion retried only the built‑in retryable statuses (408, 429 and all 5xx). Now you can extend retry behavior to other status codes (for example, 422 or 404) when your integration needs it.What’s newAdditional Retry Status Codes — a free‑form field on the HTTP Make request module where you can add numeric HTTP status codes (comma or space separated) that should be treated as retryable. When Evaluate all states as errors (except 2xx and 3xx) is enabled, any code listed here is reclassified as a retryable connection error and will be retried according to the module’s Retry Count. Default retryable statuses (408, 429, and all 5xx) remain unchanged and continue to be retried even if this field is empty.How it worksEnable Evaluate a

OverviewWe’ve added service‑account authentication options to the Jira Software connector in Fusion. You can now create Jira connections using a service account API token or service account OAuth 2. These options let teams build reliable, machine‑level integrations that aren’t tied to an individual user account.What’s newService account — API token: Authenticate the Jira connector with a service account identity using an API token. Service account — OAuth 2: Authenticate via OAuth 2 using a registered OAuth client tied to a Jira service account. Both connection types appear alongside existing user‑based connection options in the Jira connector dialog.Why this mattersStability — Service accounts reduce disruptions caused by employee changes or credential expirations. Auditability — Activities generated by connector operations are scoped to a dedicated service identity, making logging and compliance easier. Enterprise fit — Supports machine‑to‑machine integration patterns and centralized

  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