If the html source is already loaded on the frontend why not use html2pdf.js library and build a custom component that generates the pdf on the client side?
I have a good experience with PDF.co (and automate/configure it with Make.com). The PDF.co module can pass parameters in the URL when accessing your Weweb site - obtaining the required dynamic data.
Make.com and PDF.co both require a subscription by the way.
Recently PDF.co was unavailable for over 6-8 hours - during office hours. They themselves were unaware of the downtime, neither did they know when their services were back up and running.
So I tried PDFShift.io and that turned out to be a huge improvement in many ways:
They have a status page where you can see their (current and historic) uptime, so you won’t be guessing if things go wrong
They print twice as fast (my documents of about +10 pages print in about 4 seconds, with PDF.co this was +10 seconds)
PDFShift.io sends the PDF-file in its API-response (where PDF.co gives you download link that takes about another 2 seconds to be operational, so from an automation perspective the PDFShift.io approach is faster and more reliable)
And a nice gesture: PDFShift.io has a sandbox mode, so you can endlessly try the services without using your credits.