Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hello Community,

Unito will do this - but it is too pricey for my solo business and I am trying to find a Zap or combination of Zaps that will do the following.

I have successfully created a Zap that makes a new Trello Card when an Asana Task is added. 

I would like to create a Zap that adds a comment to the Trello card created above when a new comment is added to the Triggering Asana Task.

I would also like to do the reverse - update the Asana Task with a comment if a new comment is added to the Trello Card. 

 

I understand this may create a circular problem (if it can even be done.) But I wondered if that could be overcome by a delay?

 

Example:

 

Asana Task “A” created -→ Trello Card “A” Created.

Asana Task “B” created -→ Trello Card “B” Created.

Comment “1” on Asana Task “A” --→ Comment “1” added to Trello Card “A”

Comment “1” on Asana Task “B” --→ Comment “1” added to Trello Card “B”

Comment “2” on Trello Card “B” --→ Comment “2” added to Asana Task “B”

 

Is this possible?

Hi ​@Ollyt,

We do almost this exact thing, syncing between Linear (for internal task/project tracking) and Notion (for a client-facing version). The key layer in between is Zapier Tables. We have one Table that maps issue IDs from Linear to page IDs in Notion, and a second Table that maps comment IDs between the two.   This, of course, requires a set of Zaps to create/update records in each table, but the beauty of Zapier Tables is that those actions don’t count against your task usage. You could do it with a Google Sheet, but depending on your volume of tasks and comments, that could get expensive quickly.

Happy to share more if helpful! 

Thanks ​@DennisWF , I am new to Zapier and didn’t even know about Tables.  My knowledge around automation is limited to Trello so I have some learning to do! (Specifically, how to map TaskID (Asana) and CardID (Trello). ) I’ll dig into it and if/when I get stuck take you up on your offer to share more.  Thank you!

Right. ​@DennisWF , I think I am a bit overwhelmed. Can you let me know if the below sequence is correct in broad strokes?

-Make a zap that creates new Trello Card when a new Asana Task is created.

-Create a Z table that records fields/data of Asana Card.

-Create a Z Table that records fields/data of a Trello Card

-Link relative fields between two tables

-Make a zap that updates the respective Z Table when an change (comment. due date etc...) is done to either the T Card or the A Task.

-Make a zap that updates the correct T Card or A Task with updated record in Z Table

 

I don’t know how to accomplish the linked Tables and linked Cards/Tasks to records part, but is the broad process sort of correct?

Hey ​@Ollyt , you’re on the right track. But the purpose of the Table is just to map the IDs of the Asana tasks and the corresponding Trello cards, so that you know which Trello card to update when an Asana task is updated.

Then you’ll need a second Zapier Table to map the IDs of comments between two systems, same principle.

If you’re trying to set up a sync that goes in both directions, though, things get significantly more complicate, because you can easily end up creating perpetual loops - an Asana update triggers a Trello update, which triggers another Asana update, and so on. There are safeguards you can put in place to prevent this, but it gets complicated quickly, and I wouldn’t advise trying to use Zapier for this kind of 2-way sync because you’ll have to spend a lot of time maintaining and troubleshooting it in all likelihood.

 

Thanks ​@DennisWF That’s what I was afraid of and I guess that’s why Unito gets the big bucks, because I believe it allows this kind of thing...

Hey ​@Ollyt yeah - for reliable two-way syncing, I would definitely recommend a dedicated service. Besides being much less of a headache to maintain, two-way syncing via Zapier can quickly get expensive from a task consumption standpoint. There are cheaper options than Unito out there - it doesn’t support Asana or Trello, but I used SyncPenguin for a while for other tools, and it was quite reliable and affordable.

If you need just one-way sync, Zaps and Zapier Tables can work. Still complicated, but I’m happy to help walk you through it in more detail.

Terms & ConditionsAccessibility statement