How to Configure the Asset Version Added Trigger in Automations

Summary

The Asset Version Added trigger lets you automatically start automation workflows whenever a new version is uploaded to an existing asset. This helps close the compliance loop by automatically re-running checks on new versions, so you don’t have to manually re-trigger agents after an asset is updated.

Who?

  • Administrators and users with access to configure workflows within the Automations module.

  • No additional permissions necessary beyond standard automation management access.

Why?

Making sure every version of an asset meets your brand's quality and compliance standards can be tricky if you have to do it manually. This trigger helps by automatically handling the necessary actions as soon as a new version is uploaded.

Common Use Cases:

  • Compliance Re-check: When you upload a corrected version of a non-compliant asset, the brand compliance agent automatically re-runs to make sure the new version passes.

  • Enrichment Refresh: When you add a new version, enrichment agents can automatically update tags and metadata to reflect any changes in the revised asset.

How?

  1. Navigate to Automations and create a new workflow, or open an existing one.

  2. Select Asset version added as the trigger.

  3. Add conditions to narrow down which assets the workflow applies to.

    • Leave the conditions blank if you want the automation to run on every new version uploaded.

  4. Choose the corresponding actions to run.

    • Example: Select a compliance check or a metadata tagging action.

  5. Click Save and then Publish the rule.

Best Practices and Technical Limitations:

  • Trigger Conditions: This automation only triggers when a genuine version is uploaded. It doesn’t activate when you manually switch between current and previous versions on the asset detail screen.

  • File Format Changes: Adding a new version in a different file format won't change the main file type of the parent asset. If your workflow depends on the "Type" condition, it will still check against the original file type. So, workflows using this condition might not work as expected if the file format changes between versions.

Related Articles

Upload New Version of an Asset

How To Use Bynder's AI Automation Workflows

Updated