Workfront Fusion vs Make: the decision memo

The verdict

One gate before either column: check your Workfront plan. Per Adobe's licensing documentation, a Workfront Ultimate plan includes Fusion with unlimited operations — if that's you, the price comparison is already over and the rest of this memo is about capability, not cost. On Prime or Select, Fusion is a separately purchased, operations-priced add-on, and the comparison below is live.

So, for the Prime/Select buyer: choose Fusion if your organization has the budget, your builders would rather configure than code, and procurement prefers everything under the Adobe umbrella. Choose Make if your team likes to tinker, can learn an API, and the price difference matters — which, at roughly $20,000 a year against a few hundred, it usually does. Everything Fusion can do for Workfront, Make can do too. The difference is who has to know what, and what they pay.

FIG. 1 — The verdict, itemized. Same outcomes either column.

Finding of fact: same engine

Fusion is, functionally, a carbon copy of Make.com — same engine, Adobe's paperwork. This isn't an insult; it's a licensing arrangement, and it has a practical consequence worth knowing before you buy: new capabilities appear on Make first, and reach Fusion later — sometimes much later.

We watched this happen with three features, and both vendors' own materials let us date the lag:

FIG. 2 — The changelog gap, reconciled from both vendors' release notes.

The receipts: Make shipped visual route ordering in September 2023; Adobe's release notes record route labels arriving on Fusion the week of March 9, 2026 — about two and a half years. The filter inspector — click a filter, see how many bundles passed, which turns filter debugging from guesswork into reading — is in Make's current documentation and appears nowhere in thirteen months of Fusion release notes. Custom JavaScript functions reached Fusion in March 2026 through Adobe App Builder, which requires its own license — Make has run custom functions for years, included. And Make announced AI Agents in April 2025; Fusion's MCP Agent module followed in February 2026. If you build on Fusion, you are building on Make's yesterday. Usually that's fine. Occasionally you'll read Make's changelog like a preview of your own tooling's next year.

What Fusion buys you

Real things, priced into that license:

• Workfront modules out of the box. More of them, covering more operations, maintained by Adobe. On Make you'll reach the same endpoints over HTTP — but you'll be reading API documentation to do it.
• Auth that just works. Fusion's Workfront connection is a sign-in. On Make, you're managing API keys or OAuth apps yourself.
• Event subscriptions without the API. Watching Workfront events on Fusion is a module configuration. On Make, event subscriptions are built by hand with API calls — more on that below, because it's the single biggest tax on the cheaper route.
• Enterprise posture. Support through Adobe, procurement inside an existing vendor relationship, no new-vendor security review.

For a novice builder, the first three are a big deal — this is where "the same engine" stops meaning "the same experience." And for larger organizations with proper budget, our recommendation is Fusion nearly every time.

What Make asks of you

The learning curve, mostly. Everything Fusion does for Workfront is doable in Make via the Workfront API — we've run Workfront automations on Make for clients — but the conveniences become your responsibilities.

The one that earns its own paragraph: event subscriptions. Workfront pushes events (a project changes, a task completes) to a webhook you register — and registering it on Make means making the API calls yourself: create the subscription, point it at your Make webhook, manage its lifecycle. The first time, this is an afternoon of reading. The third time it's a routine. Like most API work, it's a skill you acquire, not a wall — but somebody on your team has to want to acquire it.

That's the real gate. Not capability. Aptitude and appetite.

The money

Numbers, as of July 2026:

Fusion: the structure first, because it decides everything. On a Workfront Ultimate plan, Fusion is included with unlimited operations — Adobe's documentation says so plainly, and for those orgs Fusion's marginal cost is zero. On Prime or Select, Fusion is purchased separately and priced by monthly operations: typically around $20,000 a year in the add-on quotes we've seen. And a note from experience: discounts on that add-on are difficult to impossible, regardless of how deep your Adobe licensing already goes. Budget the list price.

Make: published pricing, read from their slider on July 29, 2026 (annual billing): the Teams plan runs $38/month at 10,000 credits — Make's word for operations now; most module actions consume one — up to $10,700/month at 8 million, with Enterprise above that. Core caps out at 300,000; Pro runs cheaper than Teams throughout. So a modest Workfront automation workload costs a small fraction of a Fusion license — but volume cuts both ways: past roughly a million actions a month on Teams, Make's annual bill overtakes a typical $20,000 Fusion quote. The estimator below does this arithmetic with the real curve.

The comparison shopping trips on one number nobody knows off-hand: operations. Make prices by them, and estimating your monthly count is the homework everyone skips. So, the estimator — a scenario run consumes roughly one operation per module it executes:

Whether either license is justified at all is a different question — the calculator in our Fusion examples guide does that math, and the honest answer is sometimes "neither; your volume doesn't warrant it yet."

The friend test

Strip away the feature tables and the decision we actually give people is this: if figuring out an API makes you shiver, get Fusion. If you like to tinker and learn new things, get Make and keep the difference.

The math is always important. It's just not the only factor — a $20,000 license a team uses confidently beats a $500 one nobody wants to touch. Know your builders before you know your budget.

Interrogatories