To be specific, the flow was:
- Order Shipped in Shipstation (Trigger)
- Find Task in Asana (Task named Customer Name - order Number)
- Found Task in Asana Moves to Specific Column
That sounds like something that should be possible in Zapier.
Thank you for this- it is very helpful.
One thing I am unable to figure out in Flowsana is how to apply compound logic for triggers (i.e. ALL / ANY logic). This is doable within Asana’s Rules, so it is confusing why it wouldn’t be a capability of Flowsana as well.
For example, being able to set a trigger based on the name of a task is one of the best Flowsana features, since it allows rules to be essentially conditional. But without the ability to add additional triggers, this trigger alone doesn’t seem to really be able to help with automation.
Am I missing something, or are Flowsana rules really limited to one trigger only?
Paging @Phil_Seeman, Flowsana Czarsana 
Hi @Rob_Nowicki1,
The ability to have multiple triggers (as well as multiple actions and to edit existing rules) is currently in development; in fact, I’m working on it as we speak (well, OK , I took a break from it to look at the forum)!
2 Likes
I am looking to offboard Asana users using a Zap. I see that there is an Add Users in the outgoing webhook, but has anyone built one for offboarding users? Many thanks!
Concerning news for anyone using the ‘Tag Added To Task’ trigger in Zapier
(I can’t see this has been shared/addressed anywhere else on the forum, apologies if I’ve missed it):
It is now a ‘deprecated’ feature, meaning if you’re using it (which my agency does a LOT), it’s possible it won’t work as reliably moving, and will eventually disappear* 
The ‘new’ Tag Added To Task’ trigger in Zapier now requires a specific project ID :
(once you’ve selected your project, the prompt will appear to select your tag)
The old (now ‘Legacy’) version of this trigger was not project-specific. You would just choose your workspace and tag:
You can no longer use this trigger on new Zaps unless you duplicate an existing Zap that uses it.
As mentioned, we use the old version a LOT (it triggers the creation of all the Dropbox folders that correspond to the Asana task in question). Does anyone have any clue why this change has happened? We put so much work into setting this up and now I think we have to start figuring out an alternative trigger (that isn’t project-specific) for all this automation: 
Two questions:
- Does anyone know how long Zapier usually keeps deprecated triggers going for? I’m messaging them directly also and will update if I hear anything helpful.
- Does anyone have ideas for an alternative (non project-specific) Zap trigger? Here’s the use case:
It’s important to say up-front that we create new Asana projects for each client campaign. When we add a new creative task in one of these projects (via a submission form), one of the custom fields (single-select) is ‘Category’. This category might be ‘logo’ or ‘photography’. Using a custom rule (via Flowsana), a corresponding tag for the selected category is added to the task (e.g. if the new task’s ‘category’ is ‘logo’, a tag is automatically added which is also ‘logo’. This tag is the trigger for all subsequent Zapier automations (e.g. creating the corresponding ‘logo’ Dropbox folders for our creative team and clients).
*here’s Zapier’s definition of ‘deprecated’: “If you’re using a deprecated version, you must update to the latest version. Deprecated versions have a specific end-of-life date and will not work after that date. Any Zaps using deprecated versions will turn off on that date. Zapier will notify you by email whenever a version is deprecated.”
Thanks for noting this.
I’m not sure why Zapier has deprecated that; I’m not aware of an Asana-side change that would warrant it, but perhaps someone else will weigh in here.
I think your best bet would be to check with Zapier support directly.
The only workarounds I can think of would be to use other competing connector apps.
Thanks,
Larry
1 Like
Any way of triggering using ‘if task has not been updated in x time’? I’m thinking it might be possible in Zapier with a recurring task and a filter, but haven’t tried there yet
This doesn’t exist natively indeed. In Zapier I don’t believe so either, only a custom code could look at modified date…
1 Like
We try to keep the Asana-Flowsana-Zapier parts up to date. @Michaela_S can you help with the make.com part or should I remove it?
@ Bastien_Siebman THANK you for taking the time to put this together and saving my team HOURS or trial and error. We essentially have set up several of our projects as a basic CRM and need to trigger auto send of gmails (preferably with attachments. I would like these to be triggered off a task due date rather than a change of stage. Would you suggest Zapier or Flowsana?
Hi @Jen_Baldivid,
Just FYI, we don’t currently support attachments in our Flowsana “Send an email” rule action.
Any reason why you wouldn’t be using the native Gmail integration in Asana rules? is this because of attachments?