Workfront Fusion → Marketo Integration | Community
Skip to main content
D
devanshu16
Level 2
May 20, 2026
Question

Workfront Fusion → Marketo Integration

  • May 20, 2026
  • 1 reply
  • 32 views

I'm building a Fusion scenario that triggers off a Workfront task status change, clones a Marketo program template, and dynamically updates My Tokens across 25+ fields (bilingual content — EN/FR speaker info, event details, UTM tracking, etc.)

 

Just want to get ahead of 3 specific things before I start:

  1. My Token batch updates — can you update multiple tokens in a single API call, or is it one call per token? With 25+ fields this could get expensive fast if it's one at a time

  2. Access token refresh — Marketo's API access token expires periodically. How are you handling refresh cleanly inside Fusion without scheduled scenarios breaking mid-run?

  3. Cloned program token inheritance — when you clone a program from a template via API, does the cloned program automatically carry over the full My Token structure from the parent, or do you need to do anything post-clone?

 

Happy to share the full build once it's done. Any real experience here is appreciated! 🙌

1 reply

S
Adobe Support
StutiTiAdobe Support
Adobe Support
June 2, 2026

Hi ​@devanshu16,  to help youanswers your three questions:

1. My Token batch updates: Unfortunately, the Marketo Create/Update Token API does not support batch updates. It is one API call per token. With 25+ tokens, you will need to loop through them individually in Fusion using an iterator. To keep this manageable, map your Workfront fields to an array of token name/value pairs and use a single iterator module to fire the update calls sequentially rather than building 25+ separate modules.

 

2. Access token refresh: If you are using the native Marketo connector in Fusion, token refresh is handled automatically. Fusion manages the connection and re-authenticates as needed. If you are using HTTP modules with a custom OAuth 2.0 connection, Fusion also handles refresh automatically as long as you set up the connection using the OAuth 2.0 module with the correct token URL. Marketo tokens expire after 3600 seconds (1 hour), and on expiry Marketo returns a 601 or 602 error both are recoverable by re-authenticating. The native connector is the cleanest approach here and avoids mid-run failures.

 

3. Cloned program token inheritance: Yes,  when you clone a program via the Marketo API, the cloned program inherits the full My Token structure from the template, including token names and their default values. You will still need to call the update token API post-clone to overwrite the values with your event-specific data, but you do not need to recreate the token structure from scratch.

Terms & ConditionsAccessibility statement

Loading footer...