You must have the following access to use the functionality in this article:
Adobe Workfront plan* | Pro or higher |
Adobe Workfront license* | Plan, Work |
Adobe Workfront Fusion license** |
Current license requirement: No Workfront Fusion license requirement. Or Legacy license requirement: Workfront Fusion for Work Automation and Integration, Workfront Fusion for Work Automation |
Product |
Current product requirement: If you have the Select or Prime Adobe Workfront Plan, your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described in this article. Workfront Fusion is included in the Ultimate Workfront plan. Or Legacy product requirement: Your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described in this article. |
To find out what plan, license type, or access you have, contact your Workfront administrator.
For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.
A scenario defines a sequence of steps to be executed by Adobe Workfront Fusion. For each scenario, you specify the data source, how the data is to be processed, and what data is to be used and what is to be ignored. Workfront Fusion lets you create as complex of scenarios as you need; even the most sophisticated scenarios are possible.
For more information, see Create a practice integration scenario in Adobe Workfront Fusion.
You can use as many modules as you want in a scenario. You can create independent routes and specify which data should flow through them. You can also use results returned by individual actions and then pass them on to the next action.
Yes. Using Workfront Fusion, files can be received, saved, transformed, converted, encrypted, and so on. Moreover, Workfront Fusion provides a wide range of built-in features designed to enable users to work effectively and creatively with the data contained in the files.
For more information, see About mapping files in Adobe Workfront Fusion.
If you use the Email module Retrieve attachments, each attachment is sent individually through the rest of the modules in the scenario. Similar modules are also available in other apps that receive multiple files at once.
For more information, see Email modules.
Common scenarios are run at intervals according to the schedule you specify (for example, every hour, every 5 minutes, once a month, and the like). There are special triggers, called instant triggers (webhooks), that can start your scenario immediately after they receive data from a given service. Instant triggers can be extremely useful. We recommend to use them whenever possible. They help to reduce the number of operations. Received data is processed immediately without waiting for the next scheduled run. For example, the Google Sheets module Watch Changes starts a scenario immediately after a cell is updated.
An Aggregator merges data into one single collection. An example of this is files being compressed into a zip archive and sent as an email attachment.
For more information, see Aggregator module in Adobe Workfront Fusion.
An operation is any task performed by a module. An operation occurs, for example, every time a trigger runs and every time an action performs a task.
Data transfer refers to the amount of data transferred through your scenario. For example, suppose you have a scenario that retrieves a 100KB image from FTP and reduces its size to 50KB and saves both images to Dropbox. The amount of data used in this scenario is 250KB.
A connection is the link between your Workfront Fusion account and the third-party service you want to use. The connection can be easily created when editing a scenario. To add a connection, click the Add button in the module setting and follow the step-by-step instructions.
For more information, see About connecting Adobe Workfront Fusion to an app or service.