A small team should start with five Asana rules: assign every request to an owner, set a due date, move tasks when their status changes, nudge the assignee before and after a due date, and classify incoming jobs. Only the fifth needs AI Studio; all five need Starter or above.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowSince October 2026 Asana calls rules "automations" and builds them on a canvas, which you open from a project's Customize menu, then Automations. Plain rules have no run limit. The AI rule draws on AI Studio credits instead: Starter includes 50,000 a month per billing account and Advanced 75,000. Build the four plain rules first, check the data they produce for a fortnight, then add the AI one.
Which Asana plan runs automation rules, and what does AI Studio add?
Asana rules need the Starter plan or above, because the free Personal plan has no rules and no forms and is limited to two users. Rules start at Starter ($10.99 per user per month billed annually, $13.49 monthly), where Asana lists them as unlimited. Advanced ($24.99 or $30.49) adds things that change how you build intake, such as forms with branching logic, approvals and proofing, but nothing in this tutorial needs it.
AI Studio is Asana's no-code builder for rules with an AI step, and it comes in three tiers:
- AI Studio Basic is included on every paid plan, with rate limits, and draws on the plan's monthly credits: 50,000 on Starter, 75,000 on Advanced, 200,000 on Enterprise.
- AI Studio Plus is a paid option for individuals and small teams on monthly or annual plans.
- AI Studio Pro is a paid option on annual plans with more billing controls.
Asana doesn't publish a fixed price per AI rule run. Its community team said in October 2026 that credits depend on the size of the input, the size of the output, the model used and how often the rule runs, and that the rule editor shows credits per task in its top right corner. One more thing to settle first: AI has to be switched on for your domain by a super admin before anyone can build an AI step. For a full breakdown of what the credits buy, see Asana AI Studio pricing and credits per plan.
The five rules at a glance
The illustration used throughout is a seven-person plumbing firm: the owner, an office manager, four plumbers and an apprentice. Jobs arrive through an Asana form on the website and by phone, about 140 a month. The "Jobs" project has six sections: New, Scheduled, In progress, Waiting on parts, Invoicing and Done.
| Rule | Trigger | Action | Needs AI Studio? | Running cost |
|---|---|---|---|---|
| 1. Assign on arrival | Task added to the project | Set assignee (fixed person or round robin) | No | None |
| 2. Response target | Task added to the project | Set due date relative to the trigger | No | None |
| 3. Done goes to invoicing | Job stage field changed to Work done | Move to Invoicing section, reassign to office manager, add comment | No | None |
| 4. Nudge before and after the date | Due date approaching, and overdue | Add comment, or send a Slack, Teams or Gmail message | No | None |
| 5. Classify the job | Task added to the project | AI fills Job type and Priority fields, routes emergencies | Yes | AI Studio credits per run |
Why should every new job get an owner straight away?
Rule 1 gives every new job an owner the moment it lands in the project, so nothing sits unowned in New. Unowned tasks are the most common reason small teams say Asana "didn't work": a request sat in New for two days because everyone assumed someone else had it.
How to build it. In the Jobs project open Customize, then Automations, and add an automation. Choose the trigger for a task being added to the project, then the Set assignee action. You have two choices:
- A fixed owner. Every new job goes to the office manager, who books it. Simple and right for most firms under ten people.
- Round robin. Since August 2026, Set assignee can rotate through an ordered list of people. It's a standard rule, needs no AI and works on Starter. The plumbing firm uses it for quote visits only, rotating between the owner and two senior plumbers.
Watch-outs. Round robin rotates through people, not roles, and doesn't account for workload or holidays. Asana's community team confirmed that rules can't detect out-of-office status and that each task has one assignee. If a plumber is away for a week, take them out of the list and put them back later. Each time the rule runs it assigns the next person, so trigger it once per task (on arrival), not on every update.
Example. Before: an illustrative fortnight with 11 jobs that sat unassigned for more than four working hours. After: none, because there's no longer a moment when a job has no owner.
How do you set a due date that matches your promise to customers?
Rule 2 gives every new job a due date a set number of days out, matching the promise you make to customers. If your website says "we'll call you back within two working days", that promise should exist in Asana as a date. This rule sets it automatically.
How to build it. Same trigger as rule 1 (you can add it as a second action in the same automation, since one trigger can drive several actions). Add Set due date and choose a relative date, two days after the trigger. Asana's date actions can set dates relative to the trigger, and since a 2024 update they can also set them relative to a date custom field on the task, such as a "Preferred visit date" captured by the form.
Watch-outs. Check how the offset treats weekends before trusting it: create a test task on a Friday afternoon and see which date it gets. If it lands on a Sunday, either lengthen the offset for late-week jobs with a condition, or accept it and let rule 4's overdue nudge catch Monday's backlog. Either is fine, as long as the office manager knows which one you chose.
Example sum. At 140 jobs a month and a two-day target, the office manager now sees a due date on every job. In the illustrative first week, the "due today" filter showed 9 jobs on Monday morning, which became the start-of-day call list.
How do finished jobs move straight to invoicing?
Rule 3 moves a job to the Invoicing section as soon as a plumber marks it done on the mobile app, putting it on the office manager's list. Unbilled finished work is real money: if two jobs a week slip through at an illustrative average of $280, that's over $2,000 a month waiting longer than it should.
How to build it. The obvious version is a trigger on the task being marked complete, with actions to move it to the Invoicing section, reassign it to the office manager and add a comment ("Ready to invoice: check parts and hours"). It works, but a ticked task sitting in Invoicing looks finished to everyone, including the person who should be billing it. The version the firm settled on uses a single-select custom field, "Job stage", with the values Booked, On site, Waiting on parts, Work done and Invoiced. The trigger is the field changing to Work done. The plumber changes the field on the mobile app; the rule moves the task to Invoicing, reassigns it and adds the comment; the office manager ticks it complete only once the invoice has gone.
Watch-outs. Asana's community team described a common surprise with the new builder: a rule meant for one section firing for tasks in every section. The fix is a condition. Add a step after the trigger, choose Flow controls, then Paths, and add the condition "task is in section" so the rule only runs where you meant it to. Rules also run on first-level subtasks, so keep the Job stage field on the parent job only; otherwise a plumber setting it on a subtask such as "Photos uploaded" would send half a job to invoicing.
How do you remind people before a due date slips, and after?
Rule 4 is two small rules: one nudges the assignee when a due date is approaching and one when it is overdue. Asana's own rules page describes exactly this use: automatic reminders when a due date is overdue or approaching.
How to build it. Trigger: due date is approaching. Action: add comment, using a variable to name the assignee: "Callback due tomorrow for this job. If it's been rescheduled, change the date." A second rule on the overdue trigger posts a firmer comment and adds the office manager as a collaborator. If your team lives in Slack, Microsoft Teams or Gmail, Asana's rule integrations can send the message there instead of a comment.
Watch-outs. Nudges that fire on every task become noise within a week. Limit the approaching rule to the New and Scheduled sections with a condition, and leave Waiting on parts alone, because a plumber can't speed up a supplier by being reminded.
Sample comment (illustrative):
Reminder: the callback for "Leaking stopcock, two-bed flat" is due tomorrow (Thursday). The customer asked for a morning call. If you've already spoken to them, change the stage to Booked.
How does an AI rule classify each new job?
Rule 5 uses AI Studio to read each new job's description and classify it, and it is the only one of the five rules that needs AI Studio.
What it does. Customers describe problems in their own words: "water coming through the kitchen ceiling", "boiler making a banging noise", "want a quote to move the radiator". This rule reads the description and fills two single-select fields, Job type (Leak, Drainage, Heating, Bathroom, Quote) and Priority (Emergency, This week, Planned), then routes anything marked Emergency to the plumber on call.
Why it needs AI Studio. Rules 1 to 4 act on fields and dates that already exist. Classifying free text is judgement, which is what AI Studio adds. Asana's AI Studio page lists this kind of work under intake: check completeness, classify and score, then route to the right owner.
How to build it. In the same Automations menu, add an automation triggered when a task is added to the project, then add AI steps that fill the two fields, with plain-language instructions. Asana's community team says assigning by expertise or workload needs an AI-assisted step using the Use AI variable with your criteria, so the emergency routing can sit in the same rule. The instructions the firm used:
Read the task name and description (written by a customer).
Set Job type to exactly one of: Leak, Drainage, Heating, Bathroom, Quote.
Set Priority:
- Emergency = water escaping now, no heating or hot water for a
vulnerable person, sewage, or gas smell (gas smell: also add the
comment "Customer told to call the gas emergency line").
- This week = fault but contained.
- Planned = quotes and non-urgent work.
If unsure, choose the more urgent option and add a comment saying why.
A test job and what came back (illustrative):
Description: "Drip from under the bath has stained the ceiling below, bucket under it, not getting worse."
Result: Job type = Leak. Priority = This week. Comment: "Contained leak, customer has a bucket in place."
That's a sensible answer. The one the owner corrected in the first week was "no hot water since yesterday", classified as This week; the customer had mentioned a newborn in the second sentence. The fix was the line about vulnerable people, added to the instructions above.
The credit sum. Suppose the editor shows about 180 credits per task for this rule (an illustrative figure; read yours from the editor before switching it on). At 140 jobs a month that's 25,200 credits, about half of Starter's 50,000. The danger isn't this rule; it's the second and third AI rule someone adds later, such as an AI comment on every update. AI Studio sends alerts at 80% and 100% of credits, and admins can see which rules use the most under Billing, then AI Studio, then the Usage tab.
How do you test each rule before the team relies on it?
Give each rule a fifteen-minute test before the team relies on it, because a rule that misfires quietly is worse than no rule and people stop checking. The test has these checks:
- Write five test tasks that cover each path: a normal job, a Friday-afternoon job, an emergency, a quote, and one with an empty description.
- Read each task's activity feed. Rule actions appear there, so you can see which rule did what.
- Check the rule's activity. Asana has a rule activity log at project level, and AI rules have an Activity tab showing each run, which is where you see the credits a run used.
- Pause what isn't right. Rules can be switched off without being deleted, so pause a misbehaving one, fix it, and switch it back on.
- Delete the test tasks so they don't distort next month's numbers.
The filled-in test sheet the office manager kept for rule 5 (illustrative):
| Test description | Expected | Got | Pass? |
|---|---|---|---|
| "Water pouring from ceiling light" | Leak, Emergency | Leak, Emergency | Yes |
| "Quote to replace bathroom suite" | Bathroom, Planned | Quote, Planned | Partly: two right answers; added "use Quote for any price request" |
| "Kitchen sink slow to drain" | Drainage, This week | Drainage, This week | Yes |
| "Radiators cold upstairs" | Heating, This week | Heating, This week | Yes |
| (empty description) | Comment asking for details | Heating, Planned | No: added "if the description is empty, set nothing and comment" |
Where small-team rules break, and how it showed up
- The owner left, the rule stopped. Since September 2026, standard rules run with their owner's current permissions at the time they trigger. When the apprentice who built the nudge rules was removed from the project, they stopped. Asana's advice: restore the owner's access or have a project admin claim ownership. Build rules from an account that will stay, usually the owner's or the office manager's.
- Two rules arguing. One rule moved tasks to Waiting on parts when the stage changed; another changed the stage when tasks moved section. Tasks bounced. Design each rule so its action can't set off another rule's trigger.
- The same subtask created twice. A rule that adds a "Collect payment" subtask ran again when the task was edited. Asana has no native once-only setting; its suggested pattern is to set a field or tag on the parent when the subtask is created and add a condition that skips tasks already marked.
- Too many steps in one rule. Rules are capped at 20 steps. Long before that, a rule with eight actions becomes hard to test. Split it.
- Rules copied by hand into ten projects. You can duplicate a rule into another project from the builder, and project templates carry rules into new projects. Workflow bundles, which push one set of rules across many projects, are an Enterprise feature. Small teams should build one good project, save it as a template, and start new projects from it.
Rules you can skip until later
Plenty of rules sound useful in week one and only add noise. Leave these until the five above have run cleanly for a month:
- AI summaries on every comment. Each run costs credits and few people read them.
- Cross-project copying. Multi-homing a task into a second project with a rule is handy for a separate "Invoicing" project, but one project with sections is simpler for seven people.
- Scheduled triggers. Asana added time-based triggers in January 2026, starting with creating a task on a schedule and drafting a status update with AI. A plain recurring task, which works on every plan, already covers a weekly van stock check.
If the next problem is getting cleaner information into the project in the first place, the companion tutorial on Asana intake forms that route client requests with AI builds the form these rules sit behind, and forwarding enquiries by email into Asana tasks covers phone and email jobs. Teams weighing Asana against ClickUp can compare ClickUp's first rules for assigning and chasing due dates, and the wider picture is in automating project management for a small team.
If you want help fitting automations into how your team actually works, I offer one-to-one AI consultations for small businesses.
Did the five rules pay for the setup time?
In the illustrative plumbing firm they did: about four hours of building and testing across a week, a figure that depends on how settled your sections and fields are, fixed most of the leaks. Measure the result with numbers you can pull from Asana in ten minutes:
- Jobs unassigned for more than four working hours: before 11 a fortnight, after 0.
- Callbacks made after the promised date: before 14 of 140, after 4 of 140.
- Completed jobs waiting more than three days for an invoice: before 9, after 2.
- AI Studio credits used: 26,000 of 50,000, with rule 5 the only AI rule.
- Misclassified jobs found in the weekly check: 6 in week one, 1 by week four.
Those numbers are illustrative; yours will differ. The pattern is the useful part: rules 1 to 4 cost nothing to run and fixed most of the leaks, while the AI rule improved how fast emergencies reached the right plumber. That's the order to build them in.
If you track these numbers in a spreadsheet, try The Complete Excel Course with AI Integration on Coding Liquids.
Asana rules: plan and credit questions
Can I use Asana rules on the free plan?
No. Asana's pricing page lists unlimited rules from Starter upwards and none on the free Personal plan, which is also capped at two users. Starter costs $10.99 per user per month billed annually or $13.49 billed monthly. Recurring tasks and status updates do work on Personal, so a two-person team can cover some of the same ground manually.
Which Asana automation rules need AI Studio?
Only the fifth starter rule, which classifies incoming jobs, needs AI Studio; the other four are plain rules with no run limit. The AI rule draws on AI Studio credits: Starter includes 50,000 a month per billing account and Advanced 75,000. Build the four plain rules first, then add the AI one.
Do ordinary rules use AI Studio credits?
No. A rule without an AI step counts as a normal rule run, and Asana's community team said rules have no run limit. Credits are only used when a rule includes an AI step, such as an AI-filled field, an AI-written comment or the Use AI variable when choosing an assignee.
What happens to a rule when the person who built it leaves?
The rule can pause or fail. Since September 2026, standard rules run with their owner's current permissions at the moment they trigger, so if the owner loses access, restore it or have a project admin claim ownership of the rule. Asana said bundle rules, AI Studio rules and My Tasks rules weren't affected by that change.
How many steps can one Asana rule have?
Twenty. Asana's community team called it a technical limit in October 2026. For a small team that's plenty; if you're near it, the rule is probably doing two jobs and is easier to test as two separate rules with one trigger each.
Further reads
- Asana AI Teammates: Prepare Meetings and Chase Follow-Up Tasks — When a job needs judgement every week, an AI Teammate may fit better than a rule.
- Asana AI Status Updates: Draft a Weekly Client Report From Tasks — Use clean rule-driven data for a weekly client report.
- Asana to ClickUp Migration: Import Steps and What Breaks — Moving between Asana and ClickUp: what rules survive.
- ClickUp vs Asana vs Monday: Which AI Features Save Time? — Compare automation and AI across the three main tools.
Browse all AI-for-business tutorials
Sources: Asana pricing page and FAQ; Asana rules, forms, project intake and AI Studio product pages; Asana community forum Q&A from the Q3 2026 release webinar, October 2026 release notes, announcements on round robin assignment, rule owner permissions, scheduled triggers and date actions, and user threads on rule actions (all checked 17 November 2026).
