How to auto-assign Asana tasks with round robin

The hidden cost of manual triage

When new work lands in a shared project, someone has to decide who picks it up. That decision is small, but it happens constantly, and it is uneven. Some people end up overloaded while tasks sit unassigned waiting for attention. For support queues and intake forms, the delay is the difference between a fast response and a frustrated customer.

Round robin assignment takes the decision off your plate. Each new task goes to the next person in the rotation, so the load spreads evenly and nothing waits.

Asana added its own round robin to Rules in August 2026, so there are two ways to do this now. Start with Asana's if your plan includes it. This page covers what the native rule does, and where Astogi's round robin integration fits when you want something different.

Asana's round robin rule

Round robin is an option inside the Set assignee action in Asana Rules, available on Starter, Advanced, Enterprise and Enterprise+. You build a rule, pick the trigger that suits you (a task added to the project, a form submitted, a custom field changing), and give the action an ordered list of teammates. Each time the rule fires, the task goes to the next person in that list.

That is a good fit when the people who should get work are a fixed group you are happy to maintain inside the rule, and when everyone is on a plan that includes it. It keeps everything inside Asana, which is worth a lot on its own.

Two things to know before you build one. The list is part of the rule, so when someone joins or leaves the rotation you edit the rule. And the action is a Rules action, so it only exists where your plan offers it.

How Astogi's rotation differs

Astogi's round robin is an Asana user you invite to the project, round-robin@asana.astogi.com. When a task's assignee is set to that user, Astogi reassigns the task to the next real member of the project. The rotation is the project's member list, in the order Asana returns it, with Astogi's own users skipped so the bot never hands work to itself.

The trigger is the useful part. Anything that sets the assignee to the Astogi user starts the rotation: a person assigning the task, a request form that assigns on submission, or a rule you already have. You do not need the Rules round robin action for it to work.

	Asana round robin in Rules	Astogi round robin
Where the rotation lives	An ordered list inside the rule	The project's member list
Trigger	Any rule trigger you choose	The assignee being set to the Astogi user
Plan needed	Starter and above	Any plan, since it is just a project member
Adding or removing someone	Edit the rule	Add or remove them from the project
Order	The order you set	The order Asana returns project members
Tasks assigned by hand	Depends on the rule	Left alone

Setting it up

1. Open the Asana project where tasks should be distributed.
2. Invite round-robin@asana.astogi.com to the project.
3. Check the member list. Everyone who should receive work has to be a member, and the order they appear in is the order they get tasks.
4. Create a task and assign it to the Astogi user, or let your form or rule do that. It lands on the next person in the rotation.

The edge cases that matter

A task that already has an owner is not touched. Astogi only rotates tasks that arrive assigned to its own user. If someone assigns a task to a colleague directly, nothing happens to it. That is deliberate: the rotation handles incoming work, not every assignment in the project.

People leaving the rotation. Because the rotation is the member list, removing someone from the project removes them from the rotation. No rule to edit.

People joining. A new project member is in the rotation from the next task onwards. There is nothing to add.

The bot never takes a task. Astogi's own integration users are filtered out of the member list before the next person is picked, so a task cannot be handed back to the automation.

One member only. The rotation has nowhere to go, so add the people who should receive work before you rely on it.

Where it shines

• Support and intake queues where speed of first response matters.
• Shared backlogs that would otherwise pile up unassigned.
• Teams that want a fair split without a manager assigning each item.
• Projects where the assignment already happens somewhere else, for example a form that assigns on submission, and you only need the hand-off to a person.

If a task needs a specific owner, you can still reassign it by hand. Round robin only handles the initial assignment of new tasks.

When to use Asana's own rule instead

If you are on Starter or above and the rotation is a fixed group that does not match project membership, the native rule is the simpler answer: one less integration, one less user in the project, and the list is exactly who you say it is in exactly the order you set. Use it.

Astogi's version earns its place when the rotation should follow project membership, when the assignment already lands on a user and you want the hand-off, or when the Rules round robin action is not on your plan.

FAQ

Does it overwrite assignments people make by hand? No. Astogi only acts on tasks whose assignee is the round robin user. Assign a task to a person and it stays with that person.

Can I set the rotation order myself? Not directly. The order follows the project's member list as Asana returns it. If you need a specific order, Asana's own round robin rule takes an ordered list and is the better tool.

What happens to tasks created before I turned it on? Nothing. Round robin only looks at tasks that are assigned to the Astogi user, so older tasks keep whatever owner they have.

Do I need a paid Asana plan? The Astogi side is a project member, so it does not depend on a Rules action. Astogi itself is a paid subscription; see pricing.

Does it cover more than one project? Each project has its own rotation and its own state, so a task in one project never consumes another project's turn.

For the full details and the exact Asana user to invite, see the round robin page. If your assignment rules are more complex, for example skill-based routing or a rotation that skips people who are out of office, we also build custom Asana integrations.

Back to all guides