Instead of manually running the MediaValet Bi-Directional Sync every time, you can set up an Asana rule that automatically pushes task attachments to MediaValet whenever certain conditions are met.

Before you start

1. Click Customize
2. Select Fields

3. Click + Add, then Create New

4. Field Title == "Category Path"

1. Field Type == "Text"
2. Add to mediavalet.com's field library

Without the category path, users cannot run automations

• The MediaValet Asana integration must be enabled for your workspace.
• You'll need permission to create and publish rules on the project.
• Rules are set up once per project and then apply to every task in it (or a branch of it), so plan your trigger and conditions with that scope in mind.

Steps to build rules:

Rule owner best practices will be to have one service account create all rules as only one rule owner per Asana project. If 2 people create rules, one persons rules will not run.

1. Open the project and click Customize in the top-right corner.
2. Under AI Studio, click Rules, then click Add to create a new rule.
3. In the rule builder, set up three parts:

• When… — choose the trigger that starts the rule. In our test, we used Task is assigned, but any trigger works depending on your workflow.
• Check if… (optional) — add a condition that must be true for the rule to proceed. We tested Start date is not empty, which limits the rule to tasks that already have a start date set.
• Do this… — click +, switch to the External actions tab, and search "Media." Select mediavalet upload action (you may see it listed under more than one connected MediaValet environment, e.g. production and QA — pick the correct one for your workspace).

4. With the mediavalet upload action step selected, use the Attribute Mapping panel on the right to map MediaValet metadata attributes (Alt Text, Artist, Asset Type, Campaign, Caption, Description, and many more) to your Asana custom fields. For example, mapping Alt Text to your Category Path custom field means whatever value that field holds on the task gets sent to MediaValet as the asset's alt text.
5. Click Publish rule.

Testing the rule

1. Open a task in the project the rule applies to, and attach the file(s) you want pushed to MediaValet.
2. Fill in whatever custom fields you mapped in step 4 (e.g. Category Path, Marketing Campaign Season) with the values you want carried over as metadata.
3. Trigger the rule's condition — in our test, this meant assigning the task and making sure it had a start date.
4. Asana shows a Running [rule name] notification in the bottom-left corner while the rule executes.

Please verify before publishing

We were able to fully confirm the rule-building steps above (trigger, condition, action, and attribute mapping). However, in our test recording, the rule didn't visibly complete a successful push — the mapped custom fields remained empty even after the trigger conditions appeared to be met, and re-assigning the task a second time didn't change that. Before publishing this article, it's worth doing a clean end-to-end test to confirm:

• Whether the Check if condition (e.g. "Start date is not empty") needs an actual Start date field, and where that field lives on the task if it's not shown by default alongside Due date.
• What confirmation appears on the task (sync summary card, comment, etc.) once the rule successfully pushes attachments to MediaValet — similar to the confirmation shown after a manual push.
• Whether the rule uses a fixed target category, or whether that's controlled by one of the mapped custom fields (e.g. Category Path).

Related articles

• How to set up the MediaValet integration with Asana
• How to upload assets from Asana to MediaValet (manual push)
• How to create a new category path from Asana to MediaValet
• How to insert assets from MediaValet into Asana