Here’s the scenario: We use Asana to manage our Lead Pipeline in column view. There are 7 stages/columns in our pipeline. We also use Heymarket for our SMS conversations with the prospects inside that same Asana pipeline. Heymarket has what they call “lists”, which we use to group people into based on what part of the Lead pipeline they are in (in asana).
Here’s the here’s the problem: We manage the stages in asana. Everytime we move someone in asana, we have to manually go back to heymarket and also move them… which of course doesn’t happen accurately or at all.
The goal:
Everytime I move a contact in asana to a new stage/column, also automatically update the Heymarket list they are in to match that stage.
Here’s the solution i’m asking for:
Either update your zapier trigger to look for a custom field value (which I can auto update with your Rules as I move them from stage to stage… OR…
Create an automation action within asana Rules that adds a tag when moved to column/section.
Because either way, I have to use Zapier to connect Asana and Heymarket, it’s just that there’s no useful Asana trigger for me to accomplish my goal.
Btw, this would all work if you just made a Zappier trigger that did this: Section/column is updated to a specific value within a project that you choose.
So the breakdown would look this this in Zapier:
Select Trigger = Task Moved To Section/Column
Pick your asana account
Pick which project
Pick which section/column that triggers the following action
Then I can take it from there and update HeyMarket, our CRM, and bunch of other usefull things.
As you’ve (probably painfully) discovered, Asana and Zapier together don’t currently give you the tools you’re asking for to get Heymarket updated.
FYI you can accomplish exactly that with a Flowsana If-Then Rule. Unlike Asana, Flowsana’s Rules support tags (both adding and removing them) both in triggers and actions.
Also FYI, Asana does not currently own or update its Zapier integration work; Zapier does. (Zapier has expressed the desire for Asana to take it over but that doesn’t appear likely at this point; see this forum thread for more.) So for those requested enhancements to Asana’s Zapier integration, you’d need to make those requests to Zapier.
The new rules feature is great. However, the first custom rule I imagined, and wanted to create, would involve using a tag as a trigger or as an action. An example trigger would be “Run this rule when this particular tag is set on a task.” An example action would be “Set this particular tag on a task whenever this rule is triggered.”
On a technical note: Infinite cycles (loops) could possibly be created from such triggers and actions, but preventing long cycle chains would be a consideration with pretty much any types of automated rules.
Thank you for sharing your feedback with us @Blake3. There is an existing thread regarding this topic so I’ve gone ahead and merged your post with it to consolidate feedback. I hope it’s OK.
In the meantime, I would suggest you to have a look at the Integration Flowsana developed by @Phil_Seeman. It should help you to achieve what you’re looking for!
@Natalia, Although my post overlapped with this one, my post was wider in scope. This thread speaks only of allowing tags as actions, but mine spoke of allowing tags as either actions or triggers. Merging these threads in the opposite direction could preserve all individuals feature requests/suggestions. Or unmerging would also work for that.
Agreed, this appears like a obvious feature to add (i.e. allow adding a tag to be a trigger and an action). In fact, we just upgraded from Premium to Business for the “Custom rules builder with conditional logic” on the assumption this would be possible. Seriously considering immediately downgrading now!
Hey, wanted to follow up on the timeline for this request. I work at Facebook and it’s near impossible to use third party integrations. Im aiming to get a hundred plus people using Asana but without auto tagging it’s challenging to show the value of the reporting feature. Would love to plus 10000x this request.
Hi everyone! Just curious if there’s any progress on this (being able to add tags with a rule). My life would be about a million times easier if I could do this. I have rules now with the trigger “task added to this project” and actions that update a field (like Priority), and this seems like it would be really similar to implement…
Well, here I am again. Surprised this isn’t already a thing. AS a CEO of a small business with too much stuff on his plate, I’m working on organizing all of my tasks into tags like “IT”, “Admin”, etc. The idea being to start to use the data from this effort to help me understand when there is enough to justify a new hire. I’ve got some Asana “projects” dedicated to these functions (IT, Admin, etc.).
After batch tagging all of the existing tasks, my next instinct was to automate new tasks going forward as to prevent myself from breaking the habit. “Aha, I’ll just create super basic rule that every time a task is added to the IT project, I’ll have it automatically tag itself as IT.” To my dismay, that wasn’t an option under “Actions.” I’m left wondering, why? The rules function is already there, why limit it?
Of course you could say, just use the project name, “IT” as a way to track this workload. But the thing is, I don’t always remember to put things in the right project nor do I have or want a project for each and every function I want to track. Tags seemed like a solid solution that allows the flexibility for me to apply it, wherever I’m at. In a project, in my tasks, etc. So again, why can’t rules simply have adding a tag as an action? I can’t imagine the lift is high at all…
This would be such a helpful feature! Would be super helpful for Zapier integrations (I copy my sales pipeline through ActiveCampaign linked with Asana) and automating the tags to apply when the task is shifted to a different section (board view) would be incredibly helpful.
This would be ideal. So many times I’ve wanted rules to be able to add tags, for filtering, organizing, etc, to a task.
Example: I add all of my work travel into a section of My Tasks. I then have a rule that also adds it to a “Company Travel” project. In this process, I then have to manually add a tag to this task that says “Travel”, allowing it to be filtered out accordingly.
