If you are a fan of automation, you probably quickly realized that even if Asana has triggers and actions available natively, it doesn’t always have what you need. But maybe Zapier or another tool does. You might even want to code the action or the trigger yourself.
Until recently, you would have been stuck. But this is not the case anymore, for 2 reasons.
Asana released an “Incoming Web Request” trigger, allowing you to start your automation somewhere else and finish it in Asana, to use native actions.
We at iDO created the “Outgoing Web Request” action you can use to finish your automation elsewhere! It works to call a zap, call your own server etc… The best part is: it is free to use!
To implement our custom made actions, simply create a native rule, and in the Action editor, make sure to click on the “External actions” and search for it.
This is exactly what I was looking for. When using Zapier, I was disappointed at some of the “limited” built-in triggers for Asana. Now I can use Asana Rules to create a more specific trigger (e.g,. a specific custom field changes to a specific value) and have it send to the Outgoing Web Request.
Then I can use that web request as a “Catch Hook” trigger in Zapier to kick things off the rest of the way.
Are there any limitations I should be aware of, other than the fact that it only returns the Asana task ID that triggered it?
I don’t believe we have limitations. I was not able to stress test it fully, but because our server receives a ping and then simply does an http request, there shouldn’t be any limit. I don’t know if I mentioned it somewhere, but if you plan on going nuts in terms of volumes, let me know, because if I see a massive spike in terms of server resources, we might decide to put some limitations in place.