Auto-reply to Asana creative requests with 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.

Additional information

What does this prompt do?

Watches your Asana Creative Requests project and reacts the moment a new task is created.
Reads the request brief to pick up the campaign, audience, format, and brand cues that matter.
Pulls a short, curated bundle of approved, on-brand NetX assets that fit the brief, with a one-line reason for each pick.
Posts the bundle straight back onto the Asana task as a comment, including each asset's name, key details, and a direct NetX link.
If nothing on brand qualifies, it leaves a clear note and tags your librarian instead of inventing matches.

What do I need to use this?

An Asana account with access to the project you want to monitor (typically called Creative Requests).
A NetX login with permission to search assets and read their attributes.
A naming or attribute convention in NetX for approval status, expiry, brand, and format so the agent can filter to safe-to-use assets.
The name or handle of the librarian you want tagged when no good matches exist.

How can I customize it?

Point it at a different Asana project, or extend it to several intake projects at once.
Tighten or loosen what counts as on brand by adjusting the required attributes (approval status, expiry window, brand, region).
Change the bundle size, for example always return 3 hero picks or up to 8 options.
Adjust the comment format, such as grouping by format (image, video, logo) or adding a thumbnail line.
Swap the fallback recipient, or escalate to a Slack channel in addition to tagging the librarian.

Frequently asked questions

Which Asana project does it watch?

Whichever project you choose during setup. Most teams point it at a Creative Requests intake project, but you can use any project that holds new design briefs.

How does it decide an asset is on brand and safe to share?

It only includes assets that pass the filters you set in NetX, such as approval status approved, an expiry date in the future, and matching brand or campaign tags. Anything missing those values is dropped.

What happens if there are no good matches?

Instead of guessing, the agent leaves a short comment explaining what it looked for and tags your librarian so a human can step in.

Will it work if my team uses Asana Free?

Yes for the basics. The agent reads the task and posts a comment using standard task features, which are available across plans.

Does the comment include working links back to NetX?

Yes. Each suggested asset is listed with its name, the attributes that matter most, and a direct link to that asset in NetX so designers can preview and download in one click.