Hey there,
We have been using a Zapier integration to handle comments as tickets on our PM platform. Basic workflow was this
-
New comment triggers the integration
-
We detect the project name to identify the corresponding list on our PM platform
-
We extract the comment, sender, timestamp to create a new ticket
a.If we detect that this is a reply, we also attach the parent comment (using the “ParentID” field of the new comment) -
We extract the exact frame where the comment was left (via the “Thumb” field of the comment itself) and attach it to the ticket.
Everything worked flawlessly until we had to move to v4. We have updated the Zapier integration and found no way to replicate 3.a and 4 from the above, both extremely important to ensure a smooth workflow when managing a large volume of feedback in an organized fashion. We can carry over all the other information we need, but those two elements are missing.
Since I know that one of the features of the migration was feature parity for integrations, I am hoping you may be able to assist with a solution/workaround for the two points above (or confirm that those two features are no longer supported)
Thank you!