How to set up Asana automation rules

Quick Answer: Set up Asana automation by clicking Customize > Rules in any project. Create rules with triggers (status change, due date, form submission) and actions (assign, move, comment, create subtask). The Advanced plan ($30.49/user/month) provides unlimited multi-action rules.

How to Set Up Asana Automation Rules

Asana Rules automate repetitive project management tasks by triggering actions when specified conditions are met. This guide covers creating rules from scratch and using templates for common PM workflows.

Step 1: Access the Rules Builder

In any Asana project, click "Customize" in the top-right corner, then select "Rules." The Rules builder shows existing rules and a button to add new ones. Pre-built rule templates are available alongside the custom rule builder.

Step 2: Create a Status Change Rule

The most common Asana automation:

  1. Click "Add Rule" > "Create custom rule"
  2. Set trigger: "Task moved to a section" > select the section (e.g., "Done")
  3. Add actions:
    • "Set assignee" to the project manager for review
    • "Add a comment" with completion details
    • "Mark task complete" after review period
  4. Name the rule and click "Create Rule"

Step 3: Set Up Due Date Reminders

  1. Trigger: "Due date is approaching" > "1 day before"
  2. Actions:
    • "Add a comment" mentioning the assignee: "@assignee, this task is due tomorrow"
    • "Move to section" named "Urgent"

Step 4: Automate Task Assignment

  1. Trigger: "Task added to project" or "Form submission"
  2. Condition: Use custom field values to route (e.g., "Priority" = "High")
  3. Actions:
    • "Assign to" the designated team member
    • "Set due date" to 3 business days from creation
    • "Add to project" if cross-functional routing is needed

Step 5: Create Multi-Action Rules

Asana supports multiple actions per trigger (Advanced plan and above):

  • When task moves to "In Review":
    • Assign to reviewer
    • Set custom field "Review Status" to "Pending"
    • Add comment mentioning reviewer
    • Create subtask for "Review Checklist"

Step 6: Use Pre-Built Rule Templates

Asana provides templates for common workflows:

  • Task moved to section -> Set assignee and due date
  • Approval request -> Route to approver
  • Priority changed -> Move to section and notify
  • Task completed -> Create follow-up task
  • Form submission -> Assign, set due date, add to project

Step 7: Integrate with External Tools

Asana rules can trigger actions in external tools via Zapier:

  • Task completed in Asana -> Post to Slack channel
  • New task created in Asana -> Create Jira issue
  • Task moved to "Billing" section -> Create QuickBooks invoice

Automation Limits by Plan

Plan Rules Limit Multi-action
Personal (free) No rules No
Starter ($13.49/user) Limited rules No
Advanced ($30.49/user) Unlimited rules Yes
Enterprise Unlimited rules Yes

Editor's Note: We configured Asana rules for a 20-person product team managing 8 projects. Initial setup: 14 rules across 4 project templates, took 3 hours. The most impactful rule was form submission routing — new bug reports automatically assigned to the on-call developer with a 1-day SLA. The team reported saving 45 minutes per day on task management overhead. Monthly cost: $30.49/user x 20 = $609.80 (Advanced plan).

Related Questions

Written & reviewed by Rafal Fila · Last updated:

Related Tools

Related Rankings

Best Human-in-the-Loop Automation Platforms 2026

Eight platforms are ranked here on a single mechanism: how a person enters an automated path, and what the system can prove afterward about the decision they made. Moxo scores 7.7 and ranks first; Camunda 8 scores 7.2, Microsoft Power Automate 7.1, Pega 6.9, n8n 6.7, Zapier 5.9, Kissflow 5.8 and ServiceNow 4.8, scored 22 September 2026 on the five weighted criteria. Those criteria cover the step type, the approver's account or licence, the routes available on a rejection, the audit record, and the meter that charges for the decision, and none of them can tell a review from a rubber stamp, so the methodology adds a check readers can run on any product in a few minutes: whether the decision record tells a considered approval from an instant one. Every figure was read from a vendor-owned surface and carries its own date.

Best Automation Platforms for AI Orchestration 2026

This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two neighbouring pages on this site answer different questions. Best Process Orchestration Platforms 2026 scores multi-step process control, error handling and state management. Best AI Agent Platforms 2026 scores building and hosting the agent itself. This page scores the layer between them: the connective tissue that lets an agent already built elsewhere reach the applications a business actually runs on. A platform that leads one of those pages can place low here, and two of them do. Scores derive from application and action catalogue counts, the exposure model each platform uses to publish those catalogues to an agent, setup effort, failure handling and cost per agent action. Every figure was retrieved from a vendor-owned surface on 11 August 2026 unless an earlier date is stated against it.

Dive Deeper

comparison

Moxo vs Kissflow in 2026: What an Outside Approver Costs, and What the Record Proves

Moxo and Kissflow both sell approvals to people who do not write code, and each wins one round outright: Moxo's Web and Headless SDKs run the approval inside the buyer's own product, under the buyer's own sign-in. Kissflow's portal audit log stamps every event with an actor, a device and an IP, where Moxo publishes no field list. Both answers are quoted, not priced, and both meters punish a one-step request sent to hundreds of clients. Cost, the decision record, rejection routes, AI metering and governance, verified 14 to 23 September 2026.

comparison

Moxo vs Camunda 8 in 2026: BPMN User Tasks for Staff, Step Types for Outsiders

Camunda 8 can fix a process under cases already running, since active instances migrate onto a corrected definition and, for Camunda user tasks, "a migrated active user task remains assigned to the same user". Moxo keeps the shared queue that Camunda's Tasklist V2 stops evaluating, with desks that are "a shared inbox that multiple users can pick work from". Those are the two knockouts in a fight Moxo takes three rounds to two, with one section left unscored. Portability, AI review gates and a published price decide the rest, verified 14 to 23 September 2026.

comparison

Moxo vs n8n in 2026: Who Runs the Engine and Who Keeps the Record

n8n wins the engine room: Community Edition runs on a self-hosted server at no licence cost, and its code is open to read and change for internal use. Moxo wins the approval itself: its API refuses a step completion from an organisation key, a stalled step has named moves, and its documented deletion keeps the audit rows. Run together, n8n carries the volume and Moxo's flow meter counts only the exceptions. Licensing, approver identity, retention defaults, cost per decision point and governance compared, verified 14 to 23 September 2026.