Asana Workflow Automation: Rules, the Workflow Builder, and What Can Start Them
An Asana workflow is a project that moves work along on its own: requests come in through a form, land in the right section, get assigned, and move as people finish their part. Rules do most of it. Bundles copy them across projects on Enterprise plans, script actions add code on Enterprise plans, and a new web request trigger lets something outside Asana start a rule.
Add a rule: open the project, click Customize, then Add Rule, and pair a trigger with one or more actions.
Project › Customize › Add RulePlans: Asana lists Rules on Starter, Advanced, Enterprise and Enterprise Plus. The Personal plan doesn't include them.
See what ran: rule actions show in each task's activity, and the rule activity log covers the project.
Asana's automation pieces and the job each one does
Building a request workflow in Asana, start to finish
A typical internal request process, using only what Asana provides.
- 1
Take requests through a form
Attach a form to the project so requests arrive as tasks with the fields you need, not as free-text messages. See Asana forms for the form side.
- 2
Sort and assign on arrival
Add a rule triggered by the form submission that sets the section and assignee from the request type field. Branching handles different types in one rule.
- 3
Add the approval
When the task reaches the Review section, a rule asks the approver for approval and sets a due date. Once it's approved, another rule moves the task on to the next section.
Watch for: rejected requests. Give them their own section and rule, or they sit in Review forever.
- 4
Tell people outside the project
Use an integration action to post to Slack or Teams, or create a Jira issue, only at the steps that need someone else. Setup is on our Asana integrations page.
- 5
Reuse it
Once it works, save the project as a template, or on Enterprise plans package the rules, fields and sections as a bundle, so the next team starts with the same workflow. Templates are covered on Asana templates.
Running an Asana rule from another system
The web request trigger is the fix for a workflow that waits on something Asana can't see: a payment clearing, a contract being signed, stock arriving.
- 1
Build the rule with the web request trigger
Choose the incoming web request trigger in the rule builder and add the actions it should take, for example move the task to Ready and set the Paid field. Asana generates an endpoint for that trigger.
- 2
Decide what the caller sends
The call names one task and carries an
action_dataobject of key-value pairs, such as an amount or a contract link, for the rule's actions to use.Watch for: during the beta the target is always a task, and it has to be in the project where the rule lives.
- 3
Build the caller on the other side
The payment system, e-signature tool or stock system has to call that endpoint when its event happens, with the right task's ID. That means storing which task belongs to which invoice or contract.
- 4
Watch it run
Each run shows in the task's activity and the rule log. Keep a log on the calling side too, so a missed call is noticed. The endpoint detail is on our Asana API reference.
Where n-frames fits into an Asana workflow
The rules are yours to keep, because the people who own the project can read and change them. n-frames builds the parts outside Asana: the caller that fires a web request rule when Stripe confirms a payment or a contract comes back signed, the lookup that tells it which task to move, and the script actions for Enterprise teams whose logic outgrows the rule menu.
When the result of a step has to land in another system, such as an invoice in QuickBooks or a field on a CRM record, the work moves onto the Asana API. Our Asana API hub covers which jobs belong there.
Questions people ask
What's the difference between Asana Rules and workflow automation in general?
Rules are Asana's own automation: a trigger and actions, set up per project in the Customize menu. "Workflow automation" is the wider idea of a process that moves itself, which in Asana combines rules, forms, sections, bundles and sometimes outside systems calling in.
Can I build a custom Rule in Asana?
Yes, on Starter and higher plans. Pick a trigger, add one or more actions, and use conditions or branching for different cases. Enterprise and Enterprise+ can also add script actions written in Node.js.
Is there an API to create Asana Rules programmatically?
No. Rules are created and edited in the rule builder. The API can run a rule that uses the web request trigger, which is in beta, and on Enterprise plans, bundles cover applying the same rules to many projects.
Can an Asana Rule trigger an action outside Asana?
Yes, through integration actions: Slack and Teams messages, Gmail, Google Calendar and Outlook events, Jira issues, Zendesk, HubSpot and others. Writing to a system that isn't on that list, like your accounting software, takes the API. And with the web request trigger, an outside system can now start a rule too.
How many Rules can I have in one Asana project?
Asana's pricing page lists unlimited rules on paid plans. Fewer rules with branching are still easier to maintain, so combine related cases into one rule where you can.
What is the Asana workflow builder?
It's Asana's no-code, visual way to lay out a project's process: how work comes in, the sections it moves through, and the rules attached to each. Asana lists it alongside Rules on its pricing page.