Asana has round robin built in now, and if it fits your team you should use it. It is an option inside the Set assignee action in Asana Automations, the feature Asana renamed from Rules in September 2026, on Starter, Advanced, Enterprise and Enterprise+, and it rotates a task through an ordered list of teammates that you pick while you build the rule. Nothing extra to install, nothing extra to invite, and the list is exactly who you say it is in exactly the order you set. That is a good deal for a lot of teams. This page is about the other case. Astogi's Round Robin is an Asana user you invite to the project, round-robin@asana.astogi.com. Set a task's assignee to that user and Astogi reassigns the task to the next real member of the project, skipping its own users so work never lands on the bot. The rotation is the project's member list rather than a list inside a rule, which means it follows membership: someone added to the project is in the rotation from the next task onwards, someone removed is out of it, and there is no list to keep in step. It also needs no particular Asana plan, because the only thing it asks for is a project member.
Astogi watches the project through an Asana webhook. When the webhook reports that a task's assignee changed to the Astogi user, a queued job takes it from there. The job reads the task back from Asana first, and if the assignee is no longer the Astogi user it stops. That single check is what protects hand assignments: give a task to a colleague and nothing in the rotation touches it. Picking the person is the next step. The job fetches the project's member list in the order Asana returns it and drops every Astogi user from it, so the rotation can never hand a task back to the automation. It then finds the member it assigned last, which is stored against the project, and takes the one after that. When the last assignee was the final member in the list it wraps around to the first, and the chosen member is written to the task through the Asana API and remembered as the new starting point. That memory is per project. A rotation in one project never consumes another project's turn, so a busy intake project and a quiet one each keep their own place in the line. The trigger is worth understanding, because it is what makes the integration fit around whatever you already do. Astogi does not care how the assignee got set to its user. A person can assign the task by hand, a form can assign on submission, or a rule you already have can do it. Anything that ends with the Astogi user as assignee starts the rotation, and that includes Asana's own Set assignee action if you want to keep the trigger inside Rules. The order is the order Asana returns members in, not an order you set. In practice it is stable and it is the same list you see in the project's member panel, but if you need a specific sequence the native Rules action takes an ordered list and is the better tool for that. Two edge cases are worth knowing before you rely on it. A project with one human member has nowhere to rotate to, so add the people who should receive work first. And if the member who received the last task is removed from the project, the job cannot find them in the list, so that next task goes to a random member rather than the next one in line, after which the rotation carries on in order from whoever got it.
Yes. Round robin is an option inside the Set assignee action in Asana Automations, which Asana renamed from Rules in September 2026, available on Starter, Advanced, Enterprise and Enterprise+. It rotates through an ordered list of teammates you choose in the automation. If that fits, use it: it stays inside Asana and needs nothing extra.
When the rotation should follow project membership rather than a list inside a rule, when the assignment already lands on a user and you only need the hand-off to a person, or when the Rules round robin action is not on your Asana plan.
Yes, indirectly. The rotation is the project member list, so you decide who takes part by adding or removing people from the project. Astogi's own users are filtered out of the list before a person is picked.
Not directly. The order follows the project member list as Asana returns it. If you need a specific sequence, the native round robin action in Asana Rules takes an ordered list and is the better tool for that.
Nothing. Astogi only acts on tasks whose assignee is the round robin user. Assign a task to a colleague and it stays with that colleague, which is deliberate: the rotation handles incoming work, not every assignment in the project.
They keep whatever owner they have. The integration looks at the assignee being set to the Astogi user, so older tasks are never revisited.
No. The Astogi side is an ordinary project member, so it does not depend on a Rules action. Astogi itself is free to try, with paid plans from $29 a month.
Each project has its own rotation and its own stored position, so a task in one project never consumes another project's turn. Add the integration to as many projects as your Astogi plan allows.
You can try Astogi for free on your first project. Need more? Get more for just €29/month.
If you have any question or need support, feel free to contact us, our team is always happy to come up with the best solutions to your problems.
Overvoorde 49,
Amsterdam, The Netherlands
Made with ❤️ in the Netherlands
©Astogi 2026
Registered at the
Chamber of Commerce #42271509