Daddy Posted April 13, 2022 Posted April 13, 2022 I set up a zap using "visible only" but it's still being called for all files regardless if it's approved or not. rastafari, Jarrod Davis and SeNioR- 1 2
Marc Posted April 14, 2022 Posted April 14, 2022 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. Daddy 1
Daddy Posted April 14, 2022 Author Posted April 14, 2022 (edited) 4 minutes ago, Marc Stridgen said: Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. Thank you. Could you also put in a suggestion to include a new option to include the description but in raw text? This may just be ignorance on my part but the only option I see includes markup which webhooks don't seem to like. I do see a description required property as well but that's almost always empty. Edited April 14, 2022 by Daddy
Daniel F Posted April 14, 2022 Posted April 14, 2022 8 minutes ago, Daddy said: but the only option I see includes markup which webhooks don't seem to like. I do see a description required property as well but that's almost always empty. Could you explain this further? Are you actually talking about version upgrades and not files? Files have a description, but it's required , while version upgrades have a none mandatory description.
Daddy Posted April 14, 2022 Author Posted April 14, 2022 (edited) 5 minutes ago, Daniel F said: Could you explain this further? Are you actually talking about version upgrades and not files? Files have a description, but it's required , while version upgrades have a none mandatory description. For the new files trigger there's 2 properties for description. One called "Description" and another called "Description required" "Description" provides the full description including markup which can't be used through a webhook (to my knowledge) and "Description Required" which seems to be a concatenated version of the description but it's almost always empty. Edited April 14, 2022 by Daddy
Daddy Posted April 14, 2022 Author Posted April 14, 2022 Adding onto this, could we also get the "price" value to be set to "free" if it has no price?
Daniel F Posted April 20, 2022 Posted April 20, 2022 On 4/14/2022 at 9:39 AM, Daddy said: For the new files trigger there's 2 properties for description. One called "Description" and another called "Description required" "Description" provides the full description including markup which can't be used through a webhook (to my knowledge) and "Description Required" which seems to be a concatenated version of the description but it's almost always empty. This is the only description field which I see:
Daddy Posted April 20, 2022 Author Posted April 20, 2022 1 minute ago, Daniel F said: This is the only description field which I see: Weird. But anyways, can we get another one that's stripped? You can't send that through a webhook with markup like that
Daniel F Posted April 20, 2022 Posted April 20, 2022 33 minutes ago, Daddy said: Weird. But anyways, can we get another one that's stripped? You can't send that through a webhook with markup like that Why wouldn't you be able to use it as webhook? This is the Zap: Which results in following request: That said, you can also always use an extra step to remove the formatting via the Zapier formatter. Daddy 1
Daddy Posted April 21, 2022 Author Posted April 21, 2022 @Daniel F Ah, thanks for that! Sorry am noob 😞
Daniel F Posted April 21, 2022 Posted April 21, 2022 No worries, I‘m happy to help:) Zapier can be really tricky and one needs to invest some time to discover all the possibilities😅 That said, the initial issue from the OP was also located and fixed for an upcoming release. Daddy 1
Solution Marc Posted July 11, 2022 Solution Posted July 11, 2022 This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues. SeNioR- and Daddy 2
Recommended Posts