Asana Native Integration is a service designed to transfer assets and their associated metadata from Asana tasks directly into Acquia DAM (Widen) (Widen). It eliminates the need to manually download and upload content. This feature is available as a managed integration.
Note
Asana Native Integration described on this page is a background service with no new user interface (UI). If you require a UI to actively search and attach assets in Asana tasks, use Asana Connector.
Benefits
Asana Native Integration provides the following benefits to your team:
Time saving: No need to move from Asana while uploading new content to Acquia DAM (Widen) (Widen).
Automatic tagging: Metadata maps from Asana metadata.
Central source of truth: Finalized assets have a central source of truth.
How the integration works
This integration uses a simple "trigger-and-action" workflow.
Trigger: A new or updated task in Asana. For example, a task marked complete with an attachment.
Action: A new asset is created in Acquia DAM (Widen) (Widen) from the attachment in the Asana task.
Optional actions
Asset metadata can be updated, and asset group, asset category, and metadata type can be assigned.
Optional updates
Task fields in Asana can be updated with information from Acquia DAM (Widen) (Widen), such as Asset URL or ID.
Requirements and limitations
The following requirements must be met for a successful automated workflow:
Controlled metadata: Data used to populate controlled metadata fields must exactly match the controlled metadata value.
Name matching: Data used to assign asset groups, asset categories, metadata types, or upload profiles must exactly match the name in the Acquia DAM (Widen) (Widen).
File support: The integration only processes standard Acquia DAM (Widen) (Widen) supported file types.
Requesting the integration
This feature is powered by a managed integration built by the Business Process Automation (BPA) team. To request this integration, users must follow the formal integration request process.
Asana Native Integration for automated asset upload to Acquia DAM
Asana Native Integration is a service designed to transfer assets and their associated metadata from Asana tasks directly into Acquia DAM (Widen) (Widen). It eliminates the need to manually download and upload content. This feature is available as a managed integration.
Note
Asana Native Integration described on this page is a background service with no new user interface (UI). If you require a UI to actively search and attach assets in Asana tasks, use Asana Connector.
Benefits
Asana Native Integration provides the following benefits to your team:
Time saving: No need to move from Asana while uploading new content to Acquia DAM (Widen) (Widen).
Automatic tagging: Metadata maps from Asana metadata.
Central source of truth: Finalized assets have a central source of truth.
How the integration works
This integration uses a simple "trigger-and-action" workflow.
Trigger: A new or updated task in Asana. For example, a task marked complete with an attachment.
Action: A new asset is created in Acquia DAM (Widen) (Widen) from the attachment in the Asana task.
Optional actions
Asset metadata can be updated, and asset group, asset category, and metadata type can be assigned.
Optional updates
Task fields in Asana can be updated with information from Acquia DAM (Widen) (Widen), such as Asset URL or ID.
Requirements and limitations
The following requirements must be met for a successful automated workflow:
Controlled metadata: Data used to populate controlled metadata fields must exactly match the controlled metadata value.
Name matching: Data used to assign asset groups, asset categories, metadata types, or upload profiles must exactly match the name in the Acquia DAM (Widen) (Widen).
File support: The integration only processes standard Acquia DAM (Widen) (Widen) supported file types.
Requesting the integration
This feature is powered by a managed integration built by the Business Process Automation (BPA) team. To request this integration, users must follow the formal integration request process.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.