WoodWing Connect: Connecting WoodWing Assets 10 with Workato

Workato is an Enterprise-level automation platform service provider and offers an out-of-the-box way to quickly and easily connect and integrate with hundreds of business applications. 

The Workato service provides customers the ability to build 'Recipes' that connect disparate systems together. These Recipes use ‘Connectors' to connect to various systems such as WoodWing Assets 10.

Connectors encapsulate the APIs of the target system and provide user interface elements that help a person, who may not be a developer, to create these connections.

This article describes how to use the Assets Connector for connecting Workato with the WoodWing Assets system.

Connector components

A Connector will have 2 parts:

1. A Trigger which sets the Recipe in action.
2. An Action which is an action that can be performed within the Assets 10 instance.

Each is explained in detail below.

Triggers

Every recipe must have a ‘Trigger’.

Example: A trigger could be waiting for a Webhook to be sent to it. A trigger could also be a polling operation that queries the source system every x minutes to see if there is any work to do.

It’s also important to note that Triggers can have ‘conditions’. For example, an event can be sent to a Recipe and the trigger can qualify the event by adding a condition such as ‘if the status equals 'New’, and then continue on with the recipe.

Within a Connector, the Trigger is responsible for the following:

1. Logging into the Assets 10 system using a connection and creating a Webhook within Assets 10. The Webhook will then send data to the Recipe for processing. 
2. Deleting the Webhook from the Assets 10 instance when a recipe is stopped.

Triggers, Asset Types and Events

A Trigger event is what a Recipe receives that causes the recipe to start. Every recipe must have a Trigger. In the case of Assets 10 the Connector creates the Webhook that sends data to trigger. 

A Trigger corresponds with an actual EVENT that takes place in Assets 10. For instance, if a user creates a new image in Assets 10 then the recipe will receive an 'Asset Created' Event from Assets 10 via the Webhook when the recipe is started. 

When configuring a Trigger you need to choose one 'Asset Type' and then select one or more Events to serve as the trigger.

Asset Types are a type of filter for the trigger. Below is a list of the Asset Types:

1. Asset - think of this as object like a image or other type of file
2. Collection
3. Folder
4. Share Link

The following is a complete list of the Events that are supported within the connector:

1. Asset Placeholder Created
2. Asset Created
3. Asset Created by Copy
4. Asset Renamed
5. Asset Metadata Changed
6. Asset Metadata Extracted
7. Asset Checked Out
8. Asset Checkout Aborted
9. Asset Checked In
10. Asset Version Promoted

In the following figure, the 6 of the 12 available Events are seen. The blue checkmark indicates that, in this part of the recipe, the ‘Asset Created’ event and the 'Asset Created By Copy' are selected. The selected Events are listed at the top of dialog. This is done so that that when the disclosure arrow is turned up the selected Events are still visible. 

Actions within the Assets 10 Connector

The available Actions appear when a user creates an Action in the recipe and the selects the Assets 10 connector.  In the figure below the user has a new Action selected and the Assets 10 Connector selected. A subset of the Actions are visible on the right side of the image.

Figure: Action Selection dialog within the Connector

The following list are the available Actions in the Assets 10 Connector:

1. Add assets to Collection
2. Copy asset
3. Create asset
4. Create asset new version
5. Create collection
6. Create folder
7. Create share link
8. Download asset file
9. Move asset
10. Move collection
11. Move Folder
12. Remove asset
13. Remove asset from collection
14. Remove collection
15. Remove folder
16. Retrieve asset
17. Retrieve collection
18. Retrieve folder
19. Search assets, collections and folders
20. Update asset
21. Update collection metadata

More actions can be added, as needed, to the recipe to accomplish the required task.

¹ As part of the purchase of WoodWing Connect, the customer is provided with an API License for WoodWing Assets 10. Additional licenses can be purchased.

² Task usage is subject to fair use. Task overage will be evaluated for next year.