Basic terms in Adobe Workfront Fusion

Adobe Workfront Fusion requires an Adobe Workfront Fusion license in addition to an Adobe Workfront license.
A module that allows you to read or write bundles from or into a selected app or service.
A type of module that merges together multiple bundles (multiple arrays of data) into one single bundle. For more information, see Aggregator module in Adobe Workfront Fusion.
A unique code that identifies the user, developer, or program that is calling a software's API, used for authentication. Since Adobe Workfront Fusion modules work by connecting APIs, API keys are sometimes necessary. API keys are distributed by the app that requires them. For example, if you need an API key for ActiveCampaign, you would request it though your ActiveCampaign account.
App or service

A software application, most commonly.

An app can also be a special function that manipulates data, such as an iterator or an aggregator.

A service is a source of bundles that might include a web API, web page, different types of servers (FTP, SMTP, IMAP), and so on.

App connector
An app that connects to another system.
A bundle is a basic unit that is returned or received by modules. A bundle consists of items.
When adding an app or service to a scenario, most likely you will have to first create a connection between Workfront Fusion and the app or service in order to retrieve or send the selected data. For more information, see Connections overview.
A cycle refers to two phases of the scenario run: operation and commit. The scenario may consists of one or more cycles. For more detailed information, see Scenario execution, cycles, and phases in Adobe Workfront Fusion.
Data Store
A tool that stores data from scenarios or allows you to transfer data between individual scenarios or scenario runs. For more information, see Data Stores in Adobe Workfront Fusion.
Data Transfer
The amount of data transferred through your scenario. For more information, see Scenario details in Adobe Workfront Fusion.
Additional features that can be applied between two modules. A filter allows you to then only work with bundles that fit certain criteria. There are a number of different filters you can apply. For more information, see Add a filter to a scenario in Adobe Workfront Fusion.
A name that is used to uniquely identify a bundle. An ID is usually used to differentiate a bundle that is to be updated or deleted from a given service.
A part of a bundle. Bundles can consist of multiple items. There are several different types of items: text, number, boolean (yes/no), date, time, buffer (binary data), collections, select menu, array, and validation.
A type of module that allows you to take one bundle of data (an array of data) and divide into separate bundles. For more information, see Iterator module in Adobe Workfront Fusion.

A single step within a scenario that performs a function, such as creating a record, within the associated app or service.

Each app or service has various modules that define the way it responds to a request.

There are 4 types of modules: actions, triggers, iterators, and aggregators.

For more information, see Types of modules.


A task performed by a module.

For more information, see Operations in Adobe Workfront Fusion.

Public/Private Keys
Public and private keys are used to encrypt and decrypt data. The public key can be distributed, and anyone with the public key can encrypt data, but only the private key can decrypt it. Similarly, a user with a private key can encrypt data that anyone with the public key can decrypt. The private key encryption assures that the data came from the owner of the private key and serves as validation of the data's source.
Allows you to duplicate data or add new routes to a scenario, so to re-route data and handle different groups of data separately. For more information, see Router module in Adobe Workfront Fusion.

A user-created series of automated steps, each represented and performed by a module. The purpose of a scenario is to move and manipulate data.

For more information, see Create a scenario in Adobe Workfront Fusion.

Workfront Fusion uses transactional processing to capture the scenario lifecycle. A transaction consists of several phases during which data is transformed from one consistent state into another consistent state. There are 4 phases: initalization, operation (reading or writing), commit/rollback, and finalization.
A module that allows you to grab bundles that were added or updated since the last run of a scenario. There are 2 types of triggers: polling and instant (webhooks). For more information, see Instant triggers (webhooks) in Adobe Workfront Fusion.
A special type of trigger that allows you to run a scenario immediately after a new bundle is available. For more information, see Instant triggers (webhooks) in Adobe Workfront Fusion.