Adobe Workfront Make integrationAutomate Adobe Workfront with Make.
Can Make keep Adobe Workfront in step with the rest of your tools? The Adobe Workfront Make integration gives you 11 modules: 2 triggers, 8 actions and 1 search. This page is for ops and project leads, and it walks you from the connection to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Adobe Workfront Make integration automate?
The Adobe Workfront Make integration links your Workfront account to Make, a visual tool where you build a scenario (the automation itself: a chain of modules, each one a brick that reads or writes data). Once linked, Make can react to what happens in Workfront, read and change records, and move files, without a line of code.
Intake that lands in the right place. A request typed into a form or an email tool becomes a Workfront record through Create a record. Put Search records in front of it and Make first checks whether a matching record already exists, so the same request never gets filed twice.
Other teams told the moment something moves. Watch events is an instant trigger: Workfront calls Make as soon as the event you picked occurs. Pair it with Get a record to pull the full details, then pass them to your chat or CRM module. A handover between two departments stops depending on someone remembering to write a message.
Files that follow the work. Download a file fetches a document from its URL so the next module can store or send it, and Upload a file pushes a file into Workfront and returns its handle for the following step.
The listed modules do not cover every corner of the Workfront API. When you need an endpoint they skip, Make an API call reaches it with the same connection. The same app also exists as an n8n node; the n8n vs Make comparison helps you pick an editor, and the Make training covers the basics of the Make side if this is your first scenario.
How do you connect Adobe Workfront to Make?
- 01
Open the connection window
In your scenario, add any Adobe Workfront module and click Create a connection. A connection is your Workfront account linked to Make once; every Workfront module in your scenarios reuses it. The Connection name field is optional, but a clear name helps when you run several accounts.
- 02
Enter your domain and API key
In Domain, type your organization's Workfront domain, in the shape of
sampleName.sb01.workfront.com. Then paste your key into API Key. Both come from your own Workfront setup, so keep that tab open while you fill the form. - 03
Save and confirm access
Click Save. If Workfront asks you to sign in and approve access, do it in the window that opens. Back in Make, the module now shows your connection and can list the objects it is allowed to read.
Your first scenario with Adobe Workfront
GoalWhen a new request comes in through another app, Make creates the matching record in Adobe Workfront.
- 01
Create the scenario
Go to the Scenarios page, create a new scenario and click the big +. Pick the app where your requests arrive, a form tool for instance, and its module that watches new entries.
- 02
Add Create a record
Click the + on the right of that first module, search for Adobe Workfront and choose Create a record. Link your account with Create a connection if you have not done it yet.
- 03
Map the request into the record
Fill the module fields. Once the connection exists, Make lists what it can read in Workfront. Drag the answers from the first module into the matching fields, so each bundle (one request) becomes one record.
- 04
Test with Run once
Send a test entry through your form, then click Run once. Read the bundles each module received, and check in Workfront that the record looks right.
- 05
Schedule and switch on
On the first module, set the schedule: every 15 minutes by default. Then switch the scenario on. Each module run counts as an operation, the unit Make counts on your plan.
Adobe Workfront triggers in Make
2 modules start a scenario when something happens in Adobe Workfront. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Adobe Workfront as soon as it happens.
Watch events
Instant triggerIn Make“Triggers when selected event occurs.”
Your scenario starts the instant a chosen event happens in Workfront, with no waiting for the next check. You pick the event when you set up the module, and each occurrence arrives in Make as one bundle ready for the next module.
Watch records
Scheduled triggerIn Make“Triggers when selected record type event occurs.”
This trigger hands your scenario the Workfront records touched by the kind of change you select, for the record type you choose. It suits a flow that can work in batches rather than one item at a time, since Make collects whatever changed since its last look.
What the Adobe Workfront modules do
Adobe Workfront gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Search records
SearchIn Make“Lists records by search criteria.”
Search records finds the Workfront records that match the criteria you set, so your scenario can decide what to do before it writes anything. It can return zero, one or many bundles, and every module after it runs once per bundle.
Create a record
ActionIn Make“Creates a new record.”
Create a record adds a brand new record to Workfront from data another module passes along, so requests stop being retyped by hand. You map values from earlier bundles into the fields Make shows you.
Get a record
ActionIn Make“Gets a record by its ID.”
Get a record pulls one Workfront record in full when you already hold its ID, so the modules downstream have every value they need. It is the quickest route when a trigger or another module has already handed you that ID.
Update a record
ActionIn Make“Updates a record by its ID.”
Update a record changes an existing Workfront record, targeted by its ID, so information decided elsewhere shows up where your team plans the work. You map the new values from earlier bundles.
Delete a record
ActionIn Make“Deletes a record by its ID.”
Delete a record removes the Workfront record whose ID you pass, which keeps test data or cancelled requests from cluttering your views. It works on one record per bundle.
Perform a record action
ActionIn Make“Performs selected action for a specific record.”
Perform a record action runs a Workfront action you select on one specific record, for the moves that go beyond editing a field. You pick the action in the module and point it at the record's ID.
Upload a file
ActionIn Make“Uploads a file and returns its handle.”
Upload a file sends a file from an earlier module into Workfront and gives back its handle, the reference the next module uses to attach or place it. The file itself travels as a bundle from the module before.
Download a file
ActionIn Make“Downloads a file from its URL.”
Download a file fetches a document from its URL and turns it into a file the rest of your scenario can store, send or convert. It is the bridge between Workfront documents and your other tools.
Make an API call
ActionIn Make“Performs an authorized API call.”
Make an API call lets you reach any endpoint of the Workfront API from your scenario, reusing the connection you already set up. It covers what the ten other modules leave out.
Need help automating Adobe Workfront with Make?
A person reads every message.
