🚀 Talk to Marketo in Plain English with Workfront Fusion!
Workfront Fusion now has a new Adobe Marketo Engage MCP connector. Instead of building long scenarios module by module, you describe the outcome you want, and an AI agent works out the Marketo steps for you.
✅ Find and export leads with a simple instruction ✅ Create marketing programs and email sequences ✅ Work with emails, forms, lists, and folders ✅ Control what the AI can read, write, or delete
💡 Tip: Start with read-only tasks, check the results, then allow changes.
Use classic Fusion modules for precise, repeatable logic, and the MCP connector for flexible, multi-step tasks. Combining both works well too.
🚀 New in Workfront Fusion: Tell Your HTTP Module Which Errors to Retry!
Ever had an automation fail because of an error that would have worked if it just tried one more time?
Fusion's HTTP "Make a request" module has a new field: Additional Retry Status Codes.
Quick background: Every time Fusion talks to another system, it gets back a number called a status code. 404 means "not found." 422 means "I couldn't process that." Fusion already retried a few errors on its own: 🔁 408 (timed out) 🔁 429 (too many requests) 🔁 5xx (the other system had a problem)
Now you can add more codes to that list.
Why you'll like it: ✅ More control over what counts as "worth another try" ✅ No extra loops or steps in your scenario ✅ More reliable automations when systems have short-lived glitches
How to try it: 1️⃣ Open the HTTP Make a request module 2️⃣ Turn on Evaluate all states as errors (except 2xx and 3xx) 3️⃣ Type your codes into Additional Retry Status Codes (like 422, 404) 4️⃣ Set your Retry Count and Timeout, then save and test
Example: Set Retry Count to 4 and add 422. If the other system replies with a 422, Fusion will try again up to four more times before giving up.
⚠️ Watch out for these:
Add codes on purpose. Adding 404 means Fusion will keep retrying even when something truly doesn't exist. Timeout is how long Fusion waits per attempt, not a pause between retries. Worst-case time is roughly Timeout × (Retry Count + 1).
Have you run into errors that just needed a second try? Tell me which status codes you'd add 👇
🚀 New in Workfront Fusion: Jira now supports Service Accounts!
Fusion's Jira connector can now log in as a dedicated "robot" account (called a service account) instead of a real person's account.
What's new: 🔑 API Token: the simple option, like a username and password for the robot 🔐 OAuth 2: the more secure option, with tighter control over what the connection can do
Why you'll like it: ✅ Your automations keep running when people change roles or leave ✅ Easy to tell what a person did and what an automation did in Jira ✅ Better fit for company security policies
How to try it: Fusion → Connections → Create Connection → Jira Software → pick Service account: API token or Service account: OAuth 2 → Save → run a quick test.
💡 Tip: Give the service account only the permissions it needs, nothing more.
🔐 Important Workfront Fusion Security Update — Effective August 23, 2026
If you're using Workfront Watch Event modules in Adobe Workfront Fusion, there's an upcoming security change you should know about.
Starting August 23, 2026, Workfront Watch Event subscriptions will use authToken-based verification by default — for both new and existing subscriptions.
🔑 What is authToken?
Think of an `authToken` as a shared secret between Workfront and the webhook receiver. It helps verify that webhook requests are genuinely coming from Workfront and aren't spoofed requests.
⚙️ Do you need to configure anything in Fusion?
No. For standard Workfront Watch Event → Fusion scenarios:
✅ No manual authToken configuration is required ✅ Fusion/Workfront handles the secured subscription automatically ✅ Existing Watch Event subscriptions will be updated automatically
📌 What should you do?
👉 No action is required for standard Workfront Watch Event modules.
👉 After August 23, keep an eye on your existing Watch Event scenarios and check for any unexpected failures.
👉 If you experience a compatibility issue, you can disable Enable secured hooks in the webhook settings. However, this should only be used as a temporary compatibility workaround because disabling it removes the additional security protection.
🚀 The Adobe Workfront Fusion team has introduced several exciting new features designed to improve automation management, visibility, and overall user experience.
Here’s what’s new:
🔗 Edit Webhooks for Workfront & Workfront Planning You can now edit existing webhooks directly from the module or the Webhooks list — no more deleting and recreating them.
📝 Scenario Descriptions Fusion now allows you to add up to 240-character descriptions to scenarios, making automations easier to organize and identify.
🔍 Execution History for Chained Scenarios Gain better debugging visibility by viewing execution history and tracking the exact data passed between chained scenarios.
⚙️ New Veeva Vault Modules Five new modules have been added to the Veeva Vault connector: • Extract Multiple Files • Retrieve Extract Results • Load Multiple Files • Retrieve Load Results • List Items at a Path
The Adobe Workfront Fusion team has introduced a new restriction on hook priority updates. This capability is now limited to specific roles, including:
• Team Admins • Organization Admins • Organization Owners
This change has been implemented to ensure that engine pool resources and their usage through hooks are managed responsibly by the appropriate stakeholders across organizations.
I just published a new Medium article explaining how to generate Client ID & Client Secret for calling Workfront APIs using OAuth authentication explained in a very simple way.
If you're working on Workfront Fusion, API integrations, or automation projects, this will definitely help 💡
Vipin Jayanarayanan
🔐 Simplify API authentication with the new JWT request module in Adobe Workfront Fusion!
Adobe has added an HTTP module that generates a signed JSON Web Token (JWT) and makes the authenticated API call in a single step.
💡 Why it matters
✅ Fewer modules and less token mapping in your scenarios
✅ Easier to build, maintain, and troubleshoot JWT-based integrations
📌 Example: When a Workfront request is approved, create an event in an external system, with Fusion signing and sending the JWT for you.
⚠️ Tip: Match the module to your API’s authentication. JWT and OAuth 2.0 aren’t interchangeable.
🔗 Official documentation: experienceleague.adobe.com/en/docs/workfront-fusio…
#WorkfrontFusion #AdobeWorkfront #JWT #JSONWebToken #APIIntegration #HTTPModule #Automation
1 week ago |[YT] | 0
View 0 replies
Vipin Jayanarayanan
🚀 Talk to Marketo in Plain English with Workfront Fusion!
Workfront Fusion now has a new Adobe Marketo Engage MCP connector. Instead of building long scenarios module by module, you describe the outcome you want, and an AI agent works out the Marketo steps for you.
✅ Find and export leads with a simple instruction
✅ Create marketing programs and email sequences
✅ Work with emails, forms, lists, and folders
✅ Control what the AI can read, write, or delete
💡 Tip: Start with read-only tasks, check the results, then allow changes.
Use classic Fusion modules for precise, repeatable logic, and the MCP connector for flexible, multi-step tasks. Combining both works well too.
Click here to get all the details.
experienceleaguecommunities.adobe.com/adobe-workfr…
What would you automate first? Tell us in the comments! 👇
Hashtags:
#WorkfrontFusion #AdobeWorkfront #Marketo #AdobeMarketoEngage #MCP #ModelContextProtocol #AIAgents #MarketingAutomation #Automation
1 week ago |[YT] | 0
View 0 replies
Vipin Jayanarayanan
🚀 New in Workfront Fusion: Tell Your HTTP Module Which Errors to Retry!
Ever had an automation fail because of an error that would have worked if it just tried one more time?
Fusion's HTTP "Make a request" module has a new field: Additional Retry Status Codes.
Quick background:
Every time Fusion talks to another system, it gets back a number called a status code. 404 means "not found." 422 means "I couldn't process that." Fusion already retried a few errors on its own:
🔁 408 (timed out)
🔁 429 (too many requests)
🔁 5xx (the other system had a problem)
Now you can add more codes to that list.
Why you'll like it:
✅ More control over what counts as "worth another try"
✅ No extra loops or steps in your scenario
✅ More reliable automations when systems have short-lived glitches
How to try it:
1️⃣ Open the HTTP Make a request module
2️⃣ Turn on Evaluate all states as errors (except 2xx and 3xx)
3️⃣ Type your codes into Additional Retry Status Codes (like 422, 404)
4️⃣ Set your Retry Count and Timeout, then save and test
Example: Set Retry Count to 4 and add 422. If the other system replies with a 422, Fusion will try again up to four more times before giving up.
⚠️ Watch out for these:
Add codes on purpose. Adding 404 means Fusion will keep retrying even when something truly doesn't exist.
Timeout is how long Fusion waits per attempt, not a pause between retries.
Worst-case time is roughly Timeout × (Retry Count + 1).
Have you run into errors that just needed a second try? Tell me which status codes you'd add 👇
#WorkfrontFusion #Automation #HTTP #Workfront #Adobe #NoCode
2 weeks ago |[YT] | 0
View 0 replies
Vipin Jayanarayanan
🚀 New in Workfront Fusion: Jira now supports Service Accounts!
Fusion's Jira connector can now log in as a dedicated "robot" account (called a service account) instead of a real person's account.
What's new:
🔑 API Token: the simple option, like a username and password for the robot
🔐 OAuth 2: the more secure option, with tighter control over what the connection can do
Why you'll like it:
✅ Your automations keep running when people change roles or leave
✅ Easy to tell what a person did and what an automation did in Jira
✅ Better fit for company security policies
How to try it:
Fusion → Connections → Create Connection → Jira Software → pick Service account: API token or Service account: OAuth 2 → Save → run a quick test.
💡 Tip: Give the service account only the permissions it needs, nothing more.
#WorkfrontFusion #Jira #Automation #Workfront #Adobe
2 weeks ago (edited) |[YT] | 0
View 0 replies
Vipin Jayanarayanan
🔐 Important Workfront Fusion Security Update — Effective August 23, 2026
If you're using Workfront Watch Event modules in Adobe Workfront Fusion, there's an upcoming security change you should know about.
Starting August 23, 2026, Workfront Watch Event subscriptions will use authToken-based verification by default — for both new and existing subscriptions.
🔑 What is authToken?
Think of an `authToken` as a shared secret between Workfront and the webhook receiver. It helps verify that webhook requests are genuinely coming from Workfront and aren't spoofed requests.
⚙️ Do you need to configure anything in Fusion?
No. For standard Workfront Watch Event → Fusion scenarios:
✅ No manual authToken configuration is required
✅ Fusion/Workfront handles the secured subscription automatically
✅ Existing Watch Event subscriptions will be updated automatically
📌 What should you do?
👉 No action is required for standard Workfront Watch Event modules.
👉 After August 23, keep an eye on your existing Watch Event scenarios and check for any unexpected failures.
👉 If you experience a compatibility issue, you can disable Enable secured hooks in the webhook settings. However, this should only be used as a temporary compatibility workaround because disabling it removes the additional security protection.
#AdobeWorkfront #WorkfrontFusion #AdobeFusion #Workfront #Automation #Webhook #Integration #Adobe
2 months ago (edited) |[YT] | 1
View 1 reply
Vipin Jayanarayanan
🚀 The Adobe Workfront Fusion team has introduced several exciting new features designed to improve automation management, visibility, and overall user experience.
Here’s what’s new:
🔗 Edit Webhooks for Workfront & Workfront Planning
You can now edit existing webhooks directly from the module or the Webhooks list — no more deleting and recreating them.
📝 Scenario Descriptions
Fusion now allows you to add up to 240-character descriptions to scenarios, making automations easier to organize and identify.
🔍 Execution History for Chained Scenarios
Gain better debugging visibility by viewing execution history and tracking the exact data passed between chained scenarios.
⚙️ New Veeva Vault Modules
Five new modules have been added to the Veeva Vault connector:
• Extract Multiple Files
• Retrieve Extract Results
• Load Multiple Files
• Retrieve Load Results
• List Items at a Path
#Adobe #AdobeWorkfront #WorkfrontFusion #Fusion #Automation #WorkflowAutomation #EnterpriseAutomation #Integration #VeevaVault #DigitalTransformation #ContentSupplyChain #NoCode #LowCode
4 months ago |[YT] | 0
View 1 reply
Vipin Jayanarayanan
🚀 New Adobe Workfront Fusion Update
The Adobe Workfront Fusion team has introduced a new restriction on hook priority updates. This capability is now limited to specific roles, including:
• Team Admins
• Organization Admins
• Organization Owners
This change has been implemented to ensure that engine pool resources and their usage through hooks are managed responsibly by the appropriate stakeholders across organizations.
#Adobe #Workfront #Fusion #AdobeWorkfront #Automation #WorkflowAutomation #EnterpriseAutomation #Integration #ContentSupplyChain #DigitalOperations
4 months ago |[YT] | 0
View 0 replies
Vipin Jayanarayanan
Hey everyone 👋
Adobe has launched the first Public API endpoint for Fusion – Activity Logs API 🚀
👉 Workfront Fusion Public API is now LIVE in Production!
The first endpoint lets you access Activity Logs via API, which means:
Programmatic access to scenario logs
Better monitoring
Powerful reporting
This opens up huge possibilities for Fusion developers & architects.
Full details & docs: developer.adobe.com/workfront-fusion-apis/
#Workfront #Fusion #AdobeAutomation #APIs #TechUpdates
8 months ago (edited) |[YT] | 1
View 2 replies
Vipin Jayanarayanan
Hey everyone,
I just published a new Medium article explaining how to generate Client ID & Client Secret for calling Workfront APIs using OAuth authentication explained in a very simple way.
If you're working on Workfront Fusion, API integrations, or automation projects, this will definitely help 💡
👉 Read here:
medium.com/@vipinjayanarayanan/how-to-create-clien…
#Workfront #OAuth #API #Automation #WorkfrontFusion #AdobeWorkfront
8 months ago |[YT] | 1
View 0 replies
Vipin Jayanarayanan
Hey everyone 👋
I just published a new Medium article where I explain how to generate Client ID & Client Secret for Adobe PDF Services API in a very simple way.
If you're working on automation, integrations, or Workfront Fusion, this will be super useful 💡
medium.com/@vipinjayanarayanan/how-to-generate-cli…
8 months ago |[YT] | 2
View 0 replies