Credit awareness for builders: Know when your AI rules will use credits

Hi Asana Community!

We’ve made credit usage more visible across AI Studio. With a new set of updates, builders can now see when a rule consumes credits and how that usage accumulates, right where they already create and monitor their rules.

:sparkles: What’s new

Clearer credit signals in the builder

When a rule includes AI features, builders now see a banner that makes it clear the rule will consume AI credits. This gives builders a more explicit heads-up while they’re setting up and editing the rule.

Estimated credit usage for rules with run history

For AI rules that have already run, the builder now shows an estimate (the avg. of past runs) for future runs based on that rule’s past executions. This gives builders a better sense of ongoing usage while they review or update a rule.

A quick note: this is not a pre-run estimate for a brand new rule before it has executed for the first time. That’s still on our roadmap.

Warnings when your domain is nearing its credit limit

If a domain has reached 80% or more of its available credits, builders now see an in-product warning so they know the domain is approaching its limit and can reach out to an admin if needed.

More credit visibility in rule execution history

Execution history now includes pool awareness and credit summaries, making it easier to understand how a rule is using credits over time and how that usage relates to the available credit pool.

Why this matters

These updates are meant to make AI rule usage less of a black box. Builders can more easily understand:

  1. when a rule will consume credits

  2. what future runs may cost based on past runs

  3. when their domain is nearing its credit limit

  4. how cumulative rule runs affect overall credit usage

Looking ahead

This is one step toward better credit transparency for AI builders. We know there’s still more to do here, including giving builders a true estimate before a rule runs for the first time.

As always, let us know what you think and what would help you better plan and manage AI usage in Asana.

18 Likes

The most confusing thing ever is these AI credits. When you have to create lengthy explanations for users to understand, or use AI to explain AI, then it’s time to rethink the model and dumb it down.

1 Like

Visibility is certainly helpful. The best outcome would be to have the ability to set limits that will ensure that process interruption is not going to occur because budget for credits is exceeded. For example, when an organization has established a monthly average usage based on current rules and workflows. There should be a way to limit new AI rules until credits are added to the account. That way processes don’t fail or there are no emergency requests.

4 Likes

There should be an option to integrate an OpenAI or Claude account via API to ensure the Builder remains functional after Asana credits are depleted. A workflow that stops working mid-month due to exhausted tokens is of little use. Frankly, Asana credits run out very quickly, even with just a few active processes.

1 Like