Hey there, @Fluxus! Thanks so much for reaching out in the community. Great question - I had to do some heavy digging myself.
I wanted to start off with mentioning this particular app is owned and maintained by the team at PDFMonkey. The good news is they’ve created some great resources on their Zapier integration and how to navigate specific setups:
It looks like in, “Reacting to generated documents in Zapier” they mention:
Leveraging meta-data
The Document exposed by the trigger will not contain your payload. If you need any information in the following actions, we recommend adding them to the Document’s meta-data.
So it does appear the change was intentional.
That said, it sounds like they’ve recommend webhooks to retrieve the data you’re after.
Here’s a few more resources on Webhooks by Zapier in case it’s useful but I imagine if you were parsing data in the deprecated app you should be good:
I hope this helps! Let us know if you have any other questions - we’re always happy to lend a hand however we can. 
Hi @Fluxus
Good question.
After updating your Zap to use the newest version of PDF Monkey did you test each Zap step again?
Help article about how to change your trigger data: https://zapier.com/help/create/basics/change-the-test-data-in-your-zap-trigger
