Integration Basics

How do I know if Adobe Cloud Storage is enabled in my Workfront instance? Go to Setup → System → Customer Info. Under Preferences, you can change the default to Adobe Cloud Storage when you are ready to move to Adobe Cloud Storage. Make sure testing is done in lower environments first before doing this in production. . We can also move to Cloud Storage portfolio by portfolio by using "Select Portfolios to Convert to Adobe Cloud Storage. Test Cases – Adobe Cloud Storage Migration To be tested once a customer moves to Adobe Cloud Storage: Project Conversion Test converting an existing (legacy) request to a new project on Cloud storage. Template-Based Project Creation Create a new project using an existing template and confirm it functions correctly on Cloud storage. Fusion Scenarios Validate existing Fusion scenarios continue to run without breaking. Specifically test document identifiers: confirm whether Document Version ID and Document ID references still resolve correctly — fla...

  New version of Workfront — Rolls out on Adobe Cloud Storage, but it's opt-in and admin-controlled. Admins choose when to flip the switch, can pilot with specific groups (up to 10), and test in sandbox before going live. Adobe Cloud Storage replaces Workfront's own storage — Workfront, Frame, and Creative Cloud share one storage layer. This requires one Workfront instance paired with one Frame account in the same IMS org . Storage quota (GB per user) is pooled between the two. Frame.io replaces Workfront Proof as the review screen — Once cloud storage is on, Frame.io's viewer becomes the default review/markup tool, with better commenting/markup tools and a mobile app. The old Workfront Proof still works for legacy storage, with no set retirement date. Frame.io Enterprise adds creative work-in-progress features — internal-only commenting, secure external sharing with watermarks, and direct asset editing for creative teams, while Workfront still handles overall work m...

UA = Unified Approval ("the lite version") This approval workflow can be used alone or with the legacy Proofing (ProofHQ) markup viewer/window Keeps the old review/markup screen (legacy Proofing/ProofHQ) — the actual screen people annotate documents on doesn't change. No new contract needed — Adobe just flips a switch on request. Works with legacy Workfront storage . AI Collaborator can be added into the approval template here too — so  a customer can get AI-assisted review even on the "lite" path, without needing to move to Frame.io. (Still needs its own prerequisites: Unified Approvals on + signed Gen AI agreement.) URA = Unified Review & Approval ("the full version," also called "V2") Everything UA has, plus it swaps in a brand-new review/markup screen powered by Frame.io instead of the old proofing viewer. Requires a new contract — A customer would need to sign the "V2 SKU" paperwork to unlock it. Which vi...

  1. First add a Workfront Document Upload module and configure it as shown below

  Logic: If the Event Coordinator field is populated, fetch that value. Otherwise, get the value from the Project Coordinator field. Formula: {{if(2.eventCoordinator; 2.eventCoordinator; 2.projectCoordinator)}} Explanation: This formula reads as: "If 2.eventCoordinator is populated, output 2.eventCoordinator ; otherwise, output 2.projectCoordinator ." Key point: You don't need to explicitly check whether 2.eventCoordinator is not empty — the if() function's truthy check already handles that. A populated field is treated as true by default, so the condition alone ( 2.eventCoordinator ) is sufficient without an additional !isEmpty() or similar check.

  Four Things You Can Automate with the Adobe Workfront Fusion v3 API If you're running Fusion at scale, you've probably hit at least one of these walls: you don't know which of your 200+ scenarios is still active, you blew your operations budget mid-month without a warning, promoting a scenario from dev to prod took half a day, or you woke up to a failure alert with no idea where to start. The Fusion v3 API is the answer to all four. Here's a practical breakdown of what you can automate — and how to get started in under 10 minutes. Before You Begin: Authentication Every call goes to https://fusion.adobe.io and requires four headers: Authorization: Bearer <IMS token> x-api-key: (from Adobe Developer Console) x-organization-id: (your target org) x-gw-region: (your gateway region) Set these up once in Postman as environment variables and every example in this post will work against your own tenant without modification. Setup in ...

Workfront Calendar Visibility Issue Category Adobe Workfront – Calendar Management Affected Role Workfront Administrator Priority Medium   1. Issue Description   A Workfront administrator who originally created several calendars has left the organization and their user account is no longer active. Other administrators are unable to find some of those calendars in the calendar dropdown list. Symptom Calendars missing from the calendar dropdown for other administrators Trigger Original calendar owner's account was deactivated after leaving the organization Impact Calendars are inaccessible to the remaining team, disrupting scheduling and planning workflows   2. Root Cause   The original administrator did not grant other users or administrators access to the calendars they created. In Workfront, calenda...

  1.       Configuration in Admin Console: ·        Log in to the customer's Admin Console using this link: https://adminconsole.adobe.com/ ·        Navigate to Users and search for the user by their email address. ·        Click on the user. ·        Go to Products → click on the three dots (•••) → select Edit Products → click + → add the appropriate Fusion instance. ·        Grant the user access to product profile administration as well   2.       Configuration in Fusion: ·        Log in to the Fusion instance. ·        Navigate to Organization Overview → Users , where you will see the user created without an assigned Team . ·        Go to Team Overview, select the a...

Introduction When working with proof-based workflows, you often need to retrieve a PDF summary of a proof automatically. The Request PDF Summary module makes this easy. All it needs is a Proof ID and a Callback URL.   What You'll Need 1.   The Proof ID of the proof you want to summarize. 2.   A Callback URL — the destination URL where the PDF summary will be delivered. 3.   A custom webhook set up to receive the response.   What Is a Callback URL? The callback URL is simply the URL where the PDF summary of the proof will be sent once it's ready. Think of it as a return address you tell the system where to deliver the result, and it sends the summary there automatically.   Step 1 — Set Up Your Webhook Create a custom webhook to receive the PDF summary.  Step 2 — Configure the Module Open the Request PDF Summary module in your scenario. Enter the Proof ID and paste in your webhook's URL as the Callback URL.    Step 3 —...

The Issue A user was added as a peer reviewer in a Workfront Proof. However, when they opened the proof, they were unable to add comments — the proof appeared in read-only mode . Root Cause The issue was not related to permissions or roles. The real problem: The proof stage was locked. When a stage is locked in Proof HQ, reviewers in that stage cannot interact with the proof — including adding comments. The Fix Follow these simple steps to resolve the issue: Go to Proof HQ Open the proof in question Navigate to the Workflow section Locate the specific stage where the user is added Look for the 🔒 padlock icon Click on the padlock to unlock the stage Pro Tip Before troubleshooting user permissions: Always check if the workflow stage is locked This is a common reason for “read-only” behavior in proofs Final Outcome Once the stage is unlocked: The user regains full commenting access The proof behaves as expected for a peer reviewer

 Introduction When working with APIs or third-party systems in Workfront Fusion, you often need to send date and time in a specific format. If the format is wrong, your API call may fail. So let’s understand this in a very simple way What is Cvent Format? Cvent format looks like this: 2025-06-07T06:25:00.000Z This may look complicated, but it’s actually very simple when broken down. Understanding the Format YYYY-MM-DDTHH:mm:ss.SSSZ Each part means: YYYY → Year (e.g., 2025) MM → Month (01 = Jan, 02 = Feb, etc.) DD → Day (e.g., 07) T → Separator between date and time HH → Hour (24-hour format) mm → Minutes ss → Seconds SSS → Milliseconds Z → Time zone (UTC) Example 2025-06-07T06:25:00.000Z Means: Date → 7th June 2025 Time → 06:25 AM Timezone → UTC   How to Generate This in Workfront Fusion Use this simple expression: {{formatDate(now; "YYYY-MM-DDTHH:mm:ss.SSS[Z]")}}   Important Points Always use capital letters for format (...

Problem While selecting data from an external lookup field, an error occurred. API returned 400 (Bad Request) Cause The API URL was using an old version (v14.0) , which is no longer supported. Fix Just remove the version from the API URL. Before: /attask/api/v14.0/... After: /attask/api/... Result The API will use the latest version automatically Error gets resolved Takeaway If you see a 400 error, check if you're using an outdated API version.

Introduction This article explains some commonly used custom API calls in Workfront Fusion. Custom API Call To Fetch Group ID by Group name URL: GROUP/search?name=Marketing?fields=ID Method GET This API call helps you find the Group ID when you know the Group Name (e.g., “Marketing”). Custom API Call To Fetch Team ID by Team name URL: TEAMOB/search?name=Digital Marketing Team?fields=ID Method: GET This API call helps you find the Team ID when you know the Team Name (e.g., “Digital Marketing Team”). Custom API Call To Find The Role ID by Role name URL ROLE/search?name=Art Director?fields=ID Method GET This API call helps you find the Role ID when you know the Role Name (e.g., “Art Director”). Custom API Call To Find The Company ID by Company name URL CMPY/search?name=Agency X?fields=ID Method GET This API call helps you find the Company ID when you know the Company Name (e.g., “Agency X”). Custom API Call To Find The Document Folder ID by Document ID URL docu/search?ID=69ef41b...