We’ve been hard at work making Flowsana even more powerful and flexible for your Asana workflows. Here’s a look at the latest updates we’ve rolled out to help you streamline your task management and gain more control over your automation.
🗣️ @Mention Now Works with {project.Owner} Too!
Previously, Flowsana only supported smart @mentions in comments using {task.Assignee}—automatically turning it into a real @mention in the Asana comment when the rule ran.
We’ve expanded the @mention capability: You can now use {project.Owner} in a comment within a Flowsana rule action, and it will automatically convert to an @mention of that person in Asana!
📅 New Date-Based Rule Triggers and Conditions
We’ve added two new options under rule triggers and conditions:
- Start date is not within (# days…)
- Due date is not within (# days…)
✅ New Option: “Only Run Rule Once Per Task”
You’ll now see a checkbox on the rule creation screen:
Only run rule once per task
This is especially useful for date-based rules, like:
- Start/Due date is not within (# days…)
- Start/Due date is past by at least (# days…)
Otherwise, a task due in a month with a rule like “If the task is due more than 3 days out…” might fire every day for almost a month, which would not be desirable.
The “Only run rule once per task” option may also helpful as a general fail-safe, to make sure rules like “add tasks” or “add subtasks” don’t run more than once per task. Just check the box and rest easy knowing your rule won’t repeat unnecessarily.
🧩 Now Supporting Asana Custom Task Types
Flowsana now supports custom task types in Asana! 🎉
This enhancement opens up new ways to tailor your workflows even more precisely.
👉 Read our full blog post on custom task type support
Got questions or suggestions? Dive into our Help documentation, or feel free to reach out to our support team at support@flowsana.net—we’re here to help.
Happy automating!
—The Flowsana Team