Resources · Zapier integration

Adobe Workfront Zapier integrationAutomate Adobe Workfront with Zapier.

The Adobe Workfront Zapier integration gives you 2 triggers, 7 actions and 1 search. New and updated projects can start an automation, and other tools can create projects, file requests, move task statuses and upload documents.

Premium app Zapier reserves this app to its paid plans.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Adobe Workfront Zapier integration does for your team

It connects Adobe Workfront, a work management platform built for large company teams, to Zapier, a tool that chains apps together without code. Zapier can react when a project is created or changed, and it can push projects, requests, task statuses and files into Workfront from the tools your team uses every day.

Three results teams build first. Requests that stop living in inboxes: Create Request turns a form entry or a support ticket into a request in the right Workfront queue, so nobody retypes a brief. Projects visible beyond Workfront: New Project tells a chat channel or a spreadsheet each time a project opens, for people who never log into Workfront. Deliverables filed where they belong: Upload Document drops a file onto a project, and can store it as a proof for review.

Both triggers are polling triggers: Zapier checks Workfront on a timer, every 2 minutes on Professional and every minute on Team or Enterprise. Since Workfront is a premium app, the free plan is out of the picture anyway.

What Zapier does not do here: no trigger for new tasks or new requests, no delete action, and the only search finds users. Anything else goes through API Request (Beta), a technical step. Comparing tools? Our Adobe Workfront Make integration page covers the same app on Make, and Make vs Zapier compares the two platforms.

Vocabulary

Zapier vocabulary in one minute

Eight terms come back on every block of this page. Here they are once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it and ignores everything else.
Action
What the Zap does once it has started: the step that creates, updates or uploads something for you in an app.
Task
The unit Zapier bills. One action completed successfully is one task, and your plan is a monthly allowance of them.
Polling vs instant
A polling trigger is checked by Zapier on a fixed timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it right there otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Premium app
An app Zapier keeps for paid plans and free trials. Adobe Workfront is one, so a free account cannot use it.
Cost

What it really costs you

Adobe Workfront is a premium app: you need a paid Zapier plan, or the free trial, before a single Zap can run.

  • Premium appYes, paid plan or free trial
  • Free planCannot use Adobe Workfront
  • TriggerNever billed
  • Instant triggersNone, both are polled

Once on a paid plan, the trigger never costs a task, and Zapier's checks of Workfront are free however often they run. Every action that succeeds counts once, so a Zap with three actions uses three times the tasks of a one-action Zap. An action that fails is not counted. On a paid plan you can also add filters, searches and extra actions freely, since multi-step Zaps are included there. Just remember that each extra action is one more task per run.

Connect

Connect Adobe Workfront in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Workfront account linked once, then reused by every step that needs it.

  2. 02

    Pick Adobe Workfront

    Search for the app by name in the dialog, select it and click Add connection. A new tab opens on the Workfront side, and that is where you sign in during the next step.

  3. 03

    Sign in and grant access

    Log in to Adobe Workfront in that tab and allow Zapier to reach the account. Use a login with read or write access on the projects and queues you do not own but want a Zap to touch.

First Zap

Your first Zap: file approved deliverables back into Workfront

GoalWhen a project reaches the status you choose, the matching file from cloud storage is uploaded to it as a proof.

  1. 01

    Create the Zap

    Start a new Zap, pick Adobe Workfront and Updated Project as the event, then select the connection you made a moment ago.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from your account, so choose a real project to map fields from.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the status field, the rule and the value. Use a text rule on a text field, or nothing ever passes.

  4. 04

    Fetch the file

    Add a search in your storage app to find the deliverable by the project name. Test it once and check that the right file comes back.

  5. 05

    Upload and publish

    Add Upload Document, map the project, the filename and the file, tick Create Proof? if needed, test, then click Publish.

Triggers

The 2 Adobe Workfront triggers

2 events start a Zap when something happens in Adobe Workfront. Zapier checks for them at the interval your plan allows.

1

New Project

Polling trigger

In Zapier“Triggers when a new project is created.”

Starts the Zap whenever a project is created in Workfront, carrying its details into the next step so other tools learn about it without anyone copying them over.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
account managers or freelancers outside Workfront need to know a campaign project has opened, in chat or in a shared sheet.
Watch out
projects that existed before you publish the Zap are never picked up, so import the backlog another way.
2

Updated Project

Polling trigger

In Zapier“Triggers when an existing project is updated.”

Reacts when an existing project changes, which is how a status move or a new date in Workfront can ripple out to reporting and client tools.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a project going to complete or on hold should update a dashboard or warn a client lead.
Watch out
any edit counts as an update, so add a filter on the field you care about, and never let the same Zap run Update Project on it.
Actions

The 7 Adobe Workfront actions

Adobe Workfront gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Project

Action

In Zapier“Creates a new project in Adobe Workfront.”

Opens a new project in Workfront from data that arrives elsewhere, so a signed deal or a campaign brief does not wait for someone to set it up by hand.

When to use it
a won deal in your CRM should become a delivery project straight away.
Watch out
do not pair it with New Project in the same Zap, or it can feed itself.
2

Create Request

Action

In Zapier“Creates a new request (issue) in an Adobe Workfront request queue.”

Files a new request, which Workfront also calls an issue, into a request queue, so incoming asks follow your normal intake process.

When to use it
a web form or a ticketing tool collects creative asks from other departments.
Watch out
the request queue is mandatory, and the connected account must be able to submit to it.
3

Update Project

Action

In Zapier“Updates an existing project in Adobe Workfront.”

Changes an existing project, keeping Workfront in line with what another system already knows about the work.

When to use it
a budget approved in finance or a date moved in the CRM should be reflected on the project.
Watch out
a Zap started by Updated Project that runs this action on the same project can loop endlessly.
4

Update Request

Action

In Zapier“Updates an existing request (issue) in Adobe Workfront.”

Edits a request that is already in Workfront, so changes made by the person who asked are not lost in an email thread.

When to use it
the requester adds details in the original form tool or ticket after submitting.
Watch out
the only search of this integration finds users, not requests, so plan how the Zap will point at the right request before you build it.
5

Update Task Status

Action

In Zapier“Updates the status of an existing task in Adobe Workfront.”

Moves an existing task to a new status, letting work done in another tool show up as progress in Workfront.

When to use it
a developer closes a ticket elsewhere and the matching Workfront task should follow.
Watch out
the Task ID is required, and the integration's only search, Find User, does not look up tasks.
6

Upload Document

Action

In Zapier“Uploads a file as a document or proof.”

Attaches a file to a project as a document, or as a proof when the review workflow needs it.

When to use it
finished assets land in cloud storage and should reach the project for sign-off.
Watch out
project, filename and file are all required; give a full filename, like the mydocument.pdf example Zapier shows in the field.
7

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

A technical step that calls Workfront directly through your existing connection, for whatever the ready-made actions leave out.

When to use it
someone on your team knows exactly which Workfront feature to reach and no action covers it.
Watch out
it only reaches Workfront's own addresses, and Stop on error decides whether a failure halts the Zap.
Searches

The Adobe Workfront search

1 search step looks for data that already exists in Adobe Workfront, so a later step can use it.

A search step finds something that already exists and hands it to the next steps. In the editor, searches sit at the bottom of the event list under SEARCH. Three settings decide what happens when the result is not one clean match.

1

Find User

Search

In Zapier“Finds a user by name or email.”

Looks up a Workfront user from a name or an email address, so a later step can assign or mention the right person instead of a hard-coded one.

When to use it
a form asks who owns the request and you want that person set on the record you create next.
Watch out
names can match several people, so search by email when you have it.

The three settings every search exposes

  1. Successful if no search results are found?
    On its default, a search that finds nobody stops the Zap there. Turned on, the Zap carries on without that user.
  2. Create X if it doesn't exist yet?
    Turns a search into a find-or-create. Workfront has no such variant on Zapier, so this box does not appear here.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match on at once to the following steps.
When it breaks

When it breaks

Most failures here come from how Zaps behave in general, not from Workfront itself.

Zapier publishes a getting-started guide for Adobe Workfront, and the cases below are the ones new users hit first. If a Zap still misbehaves, our Zapier troubleshooting guide walks through the checks one by one.

  • The Zap stops after the trial

    Adobe Workfront is a premium app. Once the free trial ends without a paid plan, the Zaps that use it can no longer run.

  • Existing projects never come through

    A Zap only reacts to what happens after you publish it. Projects already in Workfront are not picked up; moving them is a separate job.

  • Updated Project loops on itself

    If the Zap writes into the very project its trigger watches, each update starts a new run, and your monthly task count drains fast.

  • A bulk import stalls

    After a migration or a mass import, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.
Need help

Need help automating Adobe Workfront with Zapier?

A person reads every message.

FAQ

Adobe Workfront Zapier integration: FAQ

01Is the Adobe Workfront Zapier integration free?
No. Adobe Workfront is a premium app on Zapier, reserved for paid plans and the free trial. A free account cannot add it to a Zap at all. The upside is that a paid plan also removes the free plan's other limit, the two-step cap, so you can chain filters, searches and several actions in one Zap. Check the current plan grid on Zapier before you commit, since prices change often and this page does not publish them.
02How many tasks does an Adobe Workfront Zap use?
One per action that succeeds, and none for the trigger. A new project that starts a Zap with one action costs one task. A Zap with three actions costs three each time it runs through. Zapier's checks of Workfront are free however often they happen, and a failed action is not counted. On a busy instance, the real driver is how many projects are created or updated each month, multiplied by the number of actions in each Zap.
03Does Adobe Workfront send changes to Zapier in real time?
No. Both triggers, New Project and Updated Project, are polling triggers: Zapier asks Workfront for new items on a timer. On Professional that happens every 2 minutes, on Team and Enterprise every minute. The 15-minute interval of the free plan does not really apply, since the app needs a paid plan anyway. On paid plans you can also change the interval or run a check by hand from the editor while testing.
04What does connecting Adobe Workfront to Zapier require?
An Adobe Workfront account, a Zapier account on a paid plan or trial, and access to what you want to automate. You add the connection once from the Apps page, sign in to Workfront in the tab that opens and grant access. If a Zap must touch projects or request queues you do not own, the connected login needs read or write access to them, because Zapier acts with that login's rights and nothing more.
05How does Zapier know which Workfront task to update?
Through the Task ID, which Update Task Status requires. The Workfront integration on Zapier has a single search, Find User, and it looks up users by name or email, not tasks. So the Task ID has to be mapped into the step from a value the Zap already holds. Before building the Zap, check where that ID will come from in your setup. If no step can supply it, API Request (Beta) is the remaining route, and it is a technical step.
06What if the Workfront action you need is not on Zapier?
Start with the seven actions: create or update projects and requests, change a task status, upload a document, and API Request (Beta). There is no action to delete anything and no trigger for new tasks. For what is missing, API Request (Beta) calls Workfront with your existing connection, but it is a technical step that expects someone who knows the Workfront API. Another automation tool may also expose a different set of operations.
07Zapier, Make or n8n for Adobe Workfront?
It depends on your criteria rather than on a winner, and this page only documents the Zapier side. On Zapier, Workfront is a premium app that needs a paid plan, its triggers are polled, and every successful action counts as a task. For what Make exposes, see our Workfront page for Make. Compare on three points: the operations your workflow actually needs, the volume of projects and requests you expect each month, and who on your team will maintain the automation.
Same platform

Other docs you might need on this stack.

Browse all integrations