Asana Automations: Set Up Rules That Actually Work

Asana automations, called Rules, are trigger-and-action automations that handle routine task moves, assignments, and notifications for you. You build them from the Customize menu inside any project or your My Tasks list. Rules run on paid plans; Personal accounts get only one preset. Here is how to set them up without wasting a plan tier.

I have built Rules across marketing intake boards, client onboarding projects, and a bug tracker that fed three teams. Most of what saves time is simple. Most of what breaks is a condition nobody remembers writing. This guide is procedure-first, because you learn Rules by building one, not by reading about them.

Check your plan before you build anything

This is the first thing to get straight, because the gating is real and it is annoying. Full custom Rules are available on Starter, Advanced, Enterprise, and Enterprise+, plus the legacy Premium, Business, and Legacy Enterprise tiers. On the free Personal plan you get exactly one preset, Due date is approaching, and only inside My Tasks. That is it.

Starter runs $10.99 per user per month billed annually, or $13.49 month to month, and it lists unlimited automations. Advanced is $24.99 annually or $30.49 monthly and adds approvals, proofing, and forms branching, which matter once your Rules start triggering review steps. If you are weighing the jump, our breakdown of Asana’s 2026 pricing tiers lays out what each level actually changes. The honest read: if automating your workflow is the reason you are upgrading, Starter is the floor, and there is no cheaper way to get real Rules.

One correction worth stating plainly, because it circulates in older guides: Asana does not publish a monthly cap on standard rule runs. The pricing page says unlimited automations on paid tiers. If you see a specific number like a 250-runs-per-month limit quoted somewhere, it is not on any official Asana page. The one place real limits exist is AI Studio, which uses a credit pool, and I cover that below.

Build your first rule in a project

Start with something concrete: when a task lands in your intake project, auto-assign it and drop it in a triage section. Here is the full path.

1. Open the project you want to automate and click Customize in the top-right toolbar.
2. Scroll to Rules and click + Add rule. You will see a gallery of preset rules at the top and a Create custom rule option below it.
3. Pick a preset if one matches, or choose Create custom rule to start from scratch.
4. Set the trigger under the When card. For this example, choose Task added to this project. Triggers are the event that fires the rule.
5. Add a condition if you need one. Click Add condition, then decide whether And (all conditions must be true) or Or (any one is enough) applies. Skip this entirely for a simple rule.
6. Under the Then card, click Add action. Choose Assign to and pick a person, then click Add action again and choose Move to section pointing at your triage column.
7. Give the rule a clear name at the top, something like “Intake: assign and triage,” and click Publish or Create rule.

A lightning-bolt icon appears next to any section or field a rule touches, which is how you spot automation later. For the full official walkthrough, Asana’s create-a-rule guide covers the same builder with video. If your rule needs to carry a value from the trigger into the action, like pulling the submitter’s name from a form into a comment, that is what rule variables do, and they are worth learning early.

Recreate the old My Tasks auto-promotion

Asana retired the automatic Today, Upcoming, and Later promotion in My Tasks and handed the job to Rules. If your tasks stopped shuffling themselves as due dates approached, this is why. You rebuild it manually, and you need two rules, not one.

1. Go to My Tasks and click Customize in the toolbar.
2. Click Add rule.
3. Choose the Due date is approaching preset.
4. Set how many days out the rule fires, then pick the section tasks should move into, for example Upcoming at three days away.
5. Repeat steps 2 through 4 to add a second rule that moves tasks into Today when the due date arrives.

Here is the gotcha nobody warns you about: date-based triggers run overnight, between midnight and 1am, not the instant a date rolls over. So a task does not jump to Today the second the clock ticks past midnight in your head; it moves when Asana’s overnight pass runs. If you check at 11pm and wonder why nothing moved, that is expected. Our My Tasks setup guide covers the section structure these rules depend on.

Rule ideas that actually save time

Most Rules people build are busywork dressed up as automation. These are the ones that pay for themselves:

• Round-robin or field-based assignment. When a custom field like Team is set, assign to the right owner. This kills the daily “who is taking this?” thread.
• Status-driven handoffs. When a Status field flips to In Review, move the task to a Review section and assign the reviewer. Pair it with a due date so nothing sits.
• Cross-tool notifications. When a high-priority bug is created, post to a channel. If your team lives in chat, wire this through the Asana-Slack integration or the Microsoft Teams integration so the alert lands where people actually look.
• Template consistency. When a task is added, set default custom fields and add a subtask checklist. This enforces process without a manager policing it. Building from a solid project template means fewer rules to write in the first place.
• Approval routing. On Advanced and up, when an approval is completed, move the task forward and notify the next owner. This is where the higher tier earns its price.

Where AI Studio fits, and where it does not

AI Studio is Asana’s AI-powered workflow builder, and it is separate from standard Rules even though both live under automation. AI Studio Basic is included on paid plans with a pooled credit allowance: 50,000 credits per billing account per month on Starter, 75,000 on Advanced, and 200,000 on Enterprise. Standard Rules do not burn those credits. AI actions inside a workflow do.

The practical takeaway: build routine trigger-and-action logic as ordinary Rules and keep it free of the credit pool. Reserve AI Studio for the work that genuinely needs reasoning, like drafting a summary or classifying free-text intake. If you automate a high-volume intake project entirely through AI actions, you can drain a monthly credit allowance faster than you would expect, and there is no way to top it up mid-cycle on Basic.

Troubleshooting when a rule does not fire

Debugging Rules is the part Asana’s docs undersell. When a rule silently does nothing, work through this in order:

1. Confirm the rule is on. Open Customize and check the rule is toggled active, not saved as a draft.
2. Re-read the trigger. “Task added to this project” does not fire for tasks that were already there, or for tasks multi-homed in from elsewhere in some configurations. Triggers are literal.
3. Check your conditions. An And where you meant Or is the single most common reason a rule looks broken. If two conditions can never both be true, the rule never runs.
4. Remember the overnight timing. Anything keyed to a due date or a date field runs on the midnight-to-1am pass, so give it until the next morning before assuming failure.
5. Look for a conflicting rule. Two rules moving the same task to different sections will fight each other, and the last one wins unpredictably. The lightning-bolt icons help you find overlaps.
6. Verify permissions. A rule cannot assign a task to someone who is not a member of the project, and it will quietly skip that action.

If the rule fires but people say they never heard about it, the problem is usually notification settings on the receiving end, not the rule. Our guide on fixing Asana notifications that stop arriving covers that side. For the logic itself, Asana’s reference on conditions and branching is the one doc worth keeping open while you debug.

When Rules are the wrong tool

Automation has a failure mode where it hides work instead of removing it. Skip a rule when the logic changes every project, because you will spend more time editing the rule than doing the task. Skip it for anything that needs judgment on each run, like deciding priority from a nuanced request. And be careful automating assignments on a team with churn, because rules pointing at people who have left create silent dead ends where tasks land on nobody.

Rules are at their best on repetitive, high-volume, low-judgment steps: triage, routing, status handoffs, reminders. The moment a workflow needs a human to think, let the human think and use the rule only to tee up the decision.

Frequently asked questions

Can I set up Asana automations on the free plan?

Not really. The free Personal plan gives you a single preset, Due date is approaching, and only inside My Tasks. Full custom Rules with triggers, conditions, and actions require Starter at $10.99 per user monthly billed annually, or a higher tier. There is no free path to custom automation.

How many automation runs does Asana allow per month?

Asana does not publish a monthly run cap for standard Rules; the pricing page lists unlimited automations on paid plans. The only real allowance is AI Studio’s credit pool, 50,000 to 200,000 credits per billing account monthly by tier, and that applies only to AI-powered actions, not ordinary rule runs.

Why did my date-based rule not run at midnight?

Date-based triggers do not fire the instant a date changes. Asana processes them on an overnight pass between midnight and 1am, so a task keyed to a due date moves in the early morning, not at the stroke of midnight. If you check late at night, expect the change to appear by morning instead.