Reply to Asana creative requests with matching NetX assets

Build me an agent workflow that triages new creative requests in Asana by replying on the task with a curated bundle of matching approved assets from NetX, so our designers stop hunting for files.

Trigger: poll Asana for the new_task event, scoped to a single project the user picks at setup (typically called "Creative Requests"). It should fire once per new task in that project.

On each trigger, the agent should read the new Asana task. Pull the task name and description (notes), plus any obvious custom fields like campaign, audience, format, brand, region, or due date. From that, derive the search intent: campaign or theme keywords, target audience, format (image, video, social, print, logo, etc.), and brand.

Then call NetX Search Assets by Query to find candidate assets. Build the search clauses from the keywords above, and pair them with facets/criteria for the attributes that signal an asset is safe to share. Filter for things like approval status = approved, an expiry date in the future (or no expiry), and matching brand/campaign tags where available. Limit candidates to a reasonable working set. For top candidates, call NetX Get Asset Attributes to confirm the required attribute values are populated and pass the filter. Drop any asset that is missing required attribute values, unapproved, expired, or off-brand.

Pick a short final list of 3 to 8 on-brand, approved assets that best fit the brief. For each, construct the NetX permalink as {siteUrl}/asset/{id} using the siteUrl from the NetX credential and the asset id from the search result, so we don't need an extra call.

Then call Asana Create a Comment on a Task on the originating task. The comment should be a tidy, scannable summary that opens with a one-line read on the brief, followed by each selected asset as its own bullet showing the display name, 2 to 4 key attributes (such as brand, campaign, format, approval status, expiry), the NetX permalink, and a one-line rationale for why it fits the brief. Keep the tone neutral and helpful.

Bake in a clear "no good matches" branch. If no candidate clears the approved + on-brand filters, do NOT invent assets or relax the rules. Instead, post a short Asana comment that says nothing matched, briefly lists what was searched for (campaign, audience, format, brand), and @-mentions the librarian Asana user the operator configures at setup so they can intake the request manually.

Setup inputs the workflow should ask for: the Asana project to watch, the NetX attribute names/values that mean "approved" and "expiry", optional brand/region defaults, the bundle size range (default 3 to 8), and the librarian Asana user to tag in the fallback branch.

Operations to use: Asana new_task poll trigger, NetX Search Assets by Query, NetX Get Asset Attributes, and Asana Create a Comment on a Task. Do not modify NetX assets and do not change the Asana task itself beyond commenting.