Change in Google Doc PDF rendering through Zapier parser
Did Zapier just quietly change/remove the parser in the google doc creation node? I have huge reliance on sending customer documents generated out of a form output and now they are complaining about getting <p> filled, ugly docs with no signature passed…
Page 1 / 1
Hi @JevfromKarla
For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode with the field mappings visible, along with an example of the GDoc issue you mention.
Hi and welcome to the community, @JevfromKarla! 😁
It sounds like you might have been running into a recently reported bug with the Create Document From Text action. The good news is that this has now been fixed, so HTML should display correctly again moving forward. You’ll likely need to re-run the Zaps to regenerate the PDFs though—sorry for any hassle there.
Keep us posted on how it’s going, want to make sure this gets sorted!
Hi, @SamB i’ve done all that and the bug is still there.
I’m so sorry to hear that, @JevfromKarla. If the Zap is running the latest version of the Google Docs app, new documents that are created should be rendering the HTML correctly. I’d suggest reaching out to our Support team so they can investigate this further. They’ll be able to check the logs for your Zap and confirm whether the bug has resurfaced or if there’s something else causing affecting the HTML from being displayed as expected.
Please do keep us updated on what they find—curious to know what’s causing this! 🙏
Now its back to working again. Thanks @SamB
YAY! That’s great news, @JevfromKarla! 🎉🎉🎉
Do keep an eye on things though and let us know if you run into any further trouble. In the meantime, happy Zapping! ⚡