Rules are now Automations: meet the new automation builder 🤝

Asana Community Product Announcements
,
1

Hey, Community!

Rules are now Automations! with a redesigned vertical builder that shows your whole workflow from start to finish, and brings project and portfolio automations into one place.

What’s new

:link: One automation, multiple objects
A single automation can now act across tasks, projects, and portfolios.

  • Task field changes → update fields, dates, status, or ownership on a project
  • Project changes → update its reporting portfolio
  • Project change meets a condition → bulk-update filtered tasks in that project (handy for reassigning work when someone leaves the team)

:robot: AI Studio goes beyond tasks
AI steps aren’t limited to tasks anymore. You can bring AI into your workflow to read context, make decisions, and take action on your projects and portfolios.

:white_check_mark: Nothing to migrate
Your existing Automations keep running. No rebuilding, no converting.

Not in this rollout
Sequential multi-step Automations and approval / human-in-the-loop workflows are coming later. Supported object combinations and availability may vary as we roll out.

Try it
Open Automations from a supported project or portfolio → choose your trigger → configure what happens next → review conditions and paths → publish. Need help? Check out our Help Center article.

automations

What process will you automate first? :backhand_index_pointing_down:

4 Likes
2

Awesome!!

What process will you automate first?

Definitely AI Studio in a portfolio :smiling_face_with_sunglasses:

3

@Nadeen_Saleh,

Looking forward to this, but . . .

When will this be fully rolled out and what status is it in now? It’s not in the one Phoenix env nor the regular env I just checked.

Thanks,

Larry

Feature: project-level rule actions on task-level rules
4

I’m seeing this on my end now. But I’m running into an issue when changing the scope. I’m not able to choose “Project Contents” when trying to set up an action/automation. It’s inactive.

2 Likes
5

Is there a way to opt into the old view if you want for certain rules? For rules with a lot of initial “else if” branches, the former layout was MUCH easier to navigate (easier to scroll down a bunch of branches than it is to scroll across).

2 Likes
6

I’ve run into the same issue, if the scope for the trigger card is set to “Project Contents” it won’t allow me to set the scope for the action card to “Project Contents” and viceversa. I’ve tried adjusting the triggers and actions to see if any would allow me to have “Project Contents” set for both but it remains inactive.

7

Does this allow rules on a project to trigger actions on a Portfolio? Or are we not there yet :wink: