Hi ​@Simone Pardini 

Thanks for taking the time to put together that video, unfortunately we had to remove it as it showed the Zap IDs and contained PII (personally identifiable information). From what you explained in the video though it seems that you’re running into a Zap loop as you’re trying to do a two-way sync between Pipedrive and Asana, which isn’t officially supported. However, it’s not impossible to achieve, you’d just need to implement a way of checking whether a deal/task has already been added by a Zap. 

This can be done by searching for the deal/task to see if it already exists and use a filter to stop the Zap from proceeding if it does.

Alternatively, you could use a filter to check for a unique value. You can learn more about that here: How to avoid a Zap loop.

Hope that helps. If you run into any issues setting that up or have any questions, just let me know! 

Hey ​@Simone Pardini,

You can create a unique Id and filter by it to do a two way sync and avoid infinite loop. I think you should approach it like this to avoid being stuck in a loop-

• For Asana to Pipedrive sync- Only run the Zap if the unique filter is not Pipedrive → Asana. Update the unique record in Pipedrive as Asana → Pipedrive.
• For Pipedrive to Asana sync- Only run the Zap if the unique filter is not Asana → Pipedrive. Update the unique record in Asana as Pipedrive → Asana

You can use any unique id depending on need so it can also be AP for Asana → Pipedrive and PA for Pipedrive → Asana. Hope it helps!