Adobe Workfront Fusion

Per this https://experienceleaguecommunities.adobe.com/t5/workfront-ideas/allow-machine-to-machine-oauth-app-credentials-to-establish/idi-p/773411#M27023  and this https://experienceleaguecommunities.adobe.com/t5/workfront-questions/having-trouble-using-oauth2-configuration-to-establish-fusion/td-p/658811 it does not really seem like this is something we can achieve at the moment. I just wanted to check was anyone able to establish Server to Server auth between Fusion and Workfront? Thank you in advance.

Shoutout to ​@SamTaylor, Principal Product Manager, Workfront Automation & Integration, for leading today’s event and sharing his expertise to highlight some of the latest features in Workfront Fusion! If you weren’t able to attend, a summary, links to the slide deck, recording, and additional resources are listed below.New Features Discussed: API-Based Scenario Promotion: New automated capabilities in Workfront Fusion replace the traditional manual clone-and-remap process, including a look at technical setup requirements, current limitations, and roadmap items. Fusion API Enhancements: Recent and upcoming updates for execution logging, detailed error reporting, and improved monitoring options. Webhook Security: New mTLS and OAuth support for stricter access control, along with a retrigger capability that makes debugging webhook-driven scenarios easier. Scenario Versioning & Restore: New tools for comparing scenario versions and restoring deleted scenarios/connections. Connecto

A lot came out last week. Here's a quick breakdown for anyone who hasn't dug into the release notes yet.Unified Review and Approvals connector This is the headline. A native connector for Workfront's approval workflow, create and update approval stages, add participants, send reminders, make decisions, retrieve approval status, and even get suggested approvers. Previously you'd need custom API calls to automate any of this. Now it's native modules, which means cleaner scenarios and easier maintenance.I'm planning to use this as part of a content supply chain automation :- Fusion watches for an approval decision in Workfront, then automatically triggers the downstream action in AEM without anyone manually checking the outcome. Will share more once it's built.New Fusion API endpoints Fusion now has a significantly expanded API for managing Fusion itself. You can programmatically list, clone, and export scenarios, pull execution history, manage connections, data stores, folders, and webho

I know that there are some neat new tools available in Fusion--chained scenarios and functions being front of mind. And, to be honest, the documentation which follows these new releases isn’t great. Many of us want to use these new tools, but parsing through these texts is difficult when we’re juggling all the things most Workfront/Fusion admins do in the day-to-day operation of the system.Having some video tutorials along with the documentation (which used to be the norm with Workfront) should be a minimum ad. But what would be nice would be a webinar demo of these new features. Seeing how these tools are being used in addition with the documentation would be a huge help for many of us second/third career “accidental IT” admins.

Hi everyone! 😁Thought I’d share a tool I’ve used in my own consulting, and am now making open source. Hope others may find it useful. No pitch here, just sharing with the community.Working with Workfront Fusion scenarios gets complicated at scale. You're inheriting large multi-hundred-module workflows, tracking changes across environments, comparing versions, trying to figure out where a single field name is referenced. Without tooling, all of this becomes impossible.That's why I built Tekmera Blueprint Explorer.It has three core functions:🔹 search: find a keyword across multiple blueprints. Critical when a field name changes and you need to find every reference, or when checking for hardcoded values across scenarios. Has saved me hundreds of hours.🔹 diff: compare two blueprints to see what's changed between versions. Critical when promoting from dev to prod, so you know exactly what you're shipping.🔹 report: generate a high-level snapshot of what a Fusion scenario does.There are s

Hi all—looking for some ideas/best practices here!I’m exploring how to automate task completions in Workfront based on proof decisions. From what I understand, this requires the document to live at the task level. If that’s the case, I’m curious how others are handling version control across multiple rounds of edits.Do you typically reuse the same task for each round, or create new tasks for each version? Trying to avoid things getting messy while still enabling automation.Example of what I’m trying to achieve:Design R1 – Designer uploads file to the task and marks complete Creative Review R1 – Proof is created and routed for approval Approved → completes Creative Review and moves to execution Changes Required → completes Creative Review and moves to Design R2 → Creative Review R2 This cycle would repeat until final approval.Would love to hear how others are handling this—especially if you’ve found a clean way to manage versions + automation together. Thanks in advance! 

Summary:The native `workfront-maestro:createRecord` Fusion module does not fully abstract field IDs for linked/connection fields (many-to-many relationships), despite Workspace and Record Type being correctly selected by label from the UI. Expected behavior:The native module should handle the internal field key mapping automatically — developers should never need to know or use raw field IDs like `F69d64ac7f0097169d4b252c8` or construct objects with `_id` suffixed keys like `{"F69d64ac7f0097169d4b252c8_id": "Rc69..."}` manually. Actual behavior:For linked/connection fields, the module exposes `fieldID_id` suffixed keys in the nested object spec. Developers must manually construct payloads like:`[{"F69d64ac7f0097169d4b252c8_id": "Rc69..."}]`This defeats the primary value proposition of the native module over a Custom API Call, which is to abstract away raw field and record IDs. Impact:Teams building automations with linked fields are forced to hardcode field IDs into their Fusion scenar

Fusion currently supports Google forms only. MS Forms would be a great addition.

In the Workfront UI, converting an Issue to a Project establishes a native resolving/resolvable relationship, and the Issue status is automatically driven by the Project status.In Fusion, the Convert object module:Immediately resolves the Issue Removes it from active queue visibility Does not allow control over timing of resolutionUsing Create a record:Allows delayed resolution But does NOT create the native resolving object relationship Prevents automatic status synchronizationRequest:Enhance Fusion to support:Creating a Project from an Issue using a template Establishing the native resolving/resolvable relationship Allowing control over when the Issue is resolved (not forced immediately)This would enable automation scenarios that match the native Workfront UX while preserving queue visibility and lifecycle control.Business impact:Prevents automation of intake workflows Forces manual conversion Creates inconsistency between UI and Fusion behavior

Thank you to all of you for joining **L821 – Take-off with Fusion! Go from 0 to Integration in 90 Minutes** at Adobe Summit 2026. Below you'll find everything but the deck from the session.   To revisit the exercises at your own pace we’ve included the .json’s here that were used in the exercises and behind the scenes to populate the firefly generated images.  These can be imported into your Fusion environment by creating a new scenario-->going to the … menu at the bottom of the Scenario designer screen -->selecting import .json. Lab DocumentationFollow the full step-by-step walkthrough here:L821 Lab Workbook ## Questions?Drop them in the comments — the community and our team are happy to help. 

In scenario history, would love the option to add a column for project name or ID. It’s cumbersome to dig thru details to find an offending job when troubleshooting an error. 

Major kudos to ​@JenDesmond for taking us into the world of Fusion templates and demoing the experience of customizing them live! And thank you to ​@SamTaylor for his help answering questions!  If you missed the event, a summary, the slides and recording are included with some helpful resources below.  Senior Technical Success Architect, Jen Desmond, shared a high-level overview of Fusion templates (there are more than 50 available!) and walked us through 5 demos including:Sync Notes Across Objects: Automatically copy updates and replies from issues to converted projects. Auto-Complete Tasks: Mark tasks complete when proofs are approved and notify stakeholders. Custom Notifications: Trigger tailored alerts based on field changes (e.g., task status updates). Project Creation via CSV: Bulk-create projects using a structured CSV file and mapping. Bulk Renaming: Enforce naming conventions across projects with automation. Here are our notes and resources:💻 Slide deck 📽 Webinar recording ⭐

I noticed the new Functions area in Fusion and was intrigued. Although we don’t have a current use for the section, I can imagine that it can be extremely useful in the future.I’ll be honest: I’m a “refugee” from magazine publishing. I’ve got giant sucking-chest-wound-sized holes in my knowledge base. At this point, I’m trying to think through “unknown unknowns” when it comes to using such cool-looking new functionality. So, for people who didn’t yoke themselves to a dying industry for most of their careers, what are you most excited to do with this new functionality? And has Adobe considered a “cookbook” in the way that it has with Fusion?-j (wishing I had a degree in data science)  

We are looking to drive custom notifications and other actions once a task’s Can Start {canStart} updates;Examples of actions when a task can start moves from false to true:  Add note and task assignee informing them their task can begin Review documents and add reference information to updates from previous tasks Review fields on other tasks and update downstream tasks as appropriate     Currently, there does not appear to be a way to watch this field, record or event which watches the system canStart field on a task.  

With the recent UI changes to Fusion, it is now less clear when a route is disabled.The previous UI showed a red circle with a line through it to indicate a disabled route, the new UI just greys out the connecting line between modules.For enabled routes, the color of the connecting dots depends on the modules that link connects. Particularly between a router and a Tools module, the color change for an enabled vs a disabled route is very slight.This will make it more difficult to quickly see that a route has been disabled. Please bring back the red circle with the line through it.

As an enterprise organization, managing, tracking and auditing changes in our Fusion scenarios that are driving business automation and processes is required.    We currently manage this manually on spreadsheets and such but this is a challenge to ensure its always updated. Idea!   Incorporate the ability to Check Out and Check In a Fusion scenario to better track and control changes.   Other options could include simply include requiring admin update comments (modal form to capture?) upon activation of any scenario.What are we looking for?  Ability to identify which scenarios are being worked on Ability to require updates and comments related to changes that are being made Ability to limit turning on scenarios that have not been checked in (risk control) Ability to better report on changes by who, when and what update notes were included

Airtable has deprecated API keys in favor of Personal Access Tokens for some time now and PAT are the recommended way to connect through the Airtable API.  https://airtable.com/developers/web/api/authenticationI am requesting that Fusion allow connections to Airtable using a PAT rather than Client ID / Secret and OAuth login.We currently have a technical email account setup with access to Airtable but due to our companies Entra policies this account cannot login through SSO to Airtable.  Because of this I cannot get through the login screen to grant access to Airtable when setting up a connection in Fusion.  I can however have a PAT setup from our system admin of Airtable for this account.Please add the ability to use a PAT when setting up an Airtable connection using the standard out of the box Airtable connector.

Setting up a forum for any additional questions that we didn’t get to as part of the Workfront Fusion Foundations: The Scenarios Every Beginner Should Know session. We’ll have Adobe Workfront Champions on deck to help answer 😀

I want to build scenarios as belowScenario 1 - Reads tasks along with its Assignee and other custom fields. Based details found need to route the scenarios to multiple paths(with Webhooks to call scenario 2 )Scenario 2 - to receive the data validated and set variables from scenario 1 to do further actions in this scenario. Please advise me with any ideas. Thanks in Advance!

I would like to create a Fusion scenario where, when a proof that is still pending a decision goes past the due date a notification can be automatically sent to the approver following up on a decision.  We have a standard decision due date of 2 days. I've searched for quite a while with no success, maybe i overlooked something. Any assistance is appreciated. 

​@Sven-iX Here is my overdue response to this post, Workfront Boards GraphQL API Documentation. FYI I could not re-comment on the post so I am tagging you here. The problem I had with fusion automation and searching boards is the redundant number of operations used to search. I have found a way to reduce this to 4 operations.The body is filled with this query and based on an inspect I used on the Get Board module. I have added the portion below to it to reduce operations for searching in a scenario. There is a lot of irrelevant information in the call but I am too lazy to remove it. I start the scenario using a instant webhook with task status change and assignedToID = Desired user, I get the card information in the getBoard() query, then use iterator to make an array and filter via card obj id = taskID, then move the card to the columnID that I got in the getBoard() query. ADDED CODE:cards {\n      id\n      name\n connectedObject {\n         objectId\n      status\n      }\n } BODY:{

Hello EveryoneI have a Workfront Search module that returns multiple attachments. The challenge is that I want to send all these attachments in an HTTP form-data request in one module (e.g., to one API endpoint that expects multiple files)  How can I achieve this ?  

Hello,  Trying to update fusion certificate secret ID.  Can someone share how to this in Fusion? Luis

It is cumbersome when scrolling through a long list of options (such as from Search Criteria Fields, Select Forms to Map, Outputs, etc.) to see which are checked.  It is especially so when you have long custom forms hundred of fields long.I suggest incorporating an action where if boxes in Fusion Scenario Modules are checked that they could be automatically pinned to the top for easy reference.

 Hello,We’re looking to add a part-time Fusion contractor to our team to support a few current and upcoming projects.If you’re interested in learning more, please reach out to Trevor at Trevor@syncpointdigital.com.