Skip to main content

I have a set of Zaps which would take submitted form information, use the information to build a URL, then submit that URL to the PDF.co HTML to PDF node to turn the content found at the URL into a PDF.

This was working until very recently when it started feeding back PDFs with only the generated URL as content instead of the actual content found at the URL.

I tested PDF.co’s URL to PDF tool and it has no issues generating the correct PDF from the URL it’s given, so appears likely that there’s an error going on where Zapier is passing the URL as HTML content instead of as a URL. I can see in the Zap history that this appears to be the case as it shows “html: https://hrest of url]” in the log for the module,

It looks like the URL and HTML input field is the same field in Zapier? Is there a way to force the field to be recognized as a URL instead of being treated like HTML?

Hi @RBrunskill 

For us to have more info, post these:

  • screenshots showing the DATA IN/OUT from the steps in your Zap Runs having issues
  • screenshots showing how your Zap steps are outlined and configured in EDIT mode so we can see the field mappings

Data In:

Full content of html field:

https://sportgroup-techhub.com/wp-content/plugins/apt-color-selector/views/image-only.php?court=track&tracklanes=black&exchangezones=signal green&sidezones=black&jumplane=black
 
Data out:

Full content of the url field:

https://pdf-user-files.s3.amazonaws.com/2271N88FAN12NTWGBS5EBUL3LFZN7VOF/Sample_track_court_colors_from_rekortan.pdf?AWSAccessKeyId=ASIA4NRRSZPHLSBNG2KY&Signature=2twz7jqZeYOaYRccMjUb5HJxNMI%3D&x-amz-security-token=IQoJb3JpZ2luX2VjEMn%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLXdlc3QtMiJGMEQCIH4Cmc6yFJs1vgvnUxzdOqaBgZLFonmmKdBWs3Oaw39PAiA6ZwtLhWG%2FHiJyAEUnadWYXQMoAkT%2FnvMdC7Ls9UzBSir%2FAwgxEAAaDDg1MzcyODc0MjM1MCIM7T3LnJ%2BiI0%2BjCVDKKtwD3NE9c9aE09TKQ3IjfwJPpPfxYoUUvZIar8QA%2FKomVQvqEfJmFMMEfrVklOuZN%2FdiUZwN08oZ7eBrExco21tEz7DfhTtqu%2B6BH8Jp7YV5VvpWKPcD7%2F1JniGFL0U2241U2x5fDNCU%2FMlFwOHTpUOnJMp%2Bw0UTgQrhNOnNWtdIR14VRhLYBKap4YgZNQZ0AddW3FqHZuIc5FbIv%2BYiukN9fdBsgigbWFtkmaARcA1f9FaDjPintiED1F01VMApwln%2By6p%2BVW5QAD6Bf%2FwOaFvPK2rtUhCH2%2FGZTyJgoYPZb4tQcuiK4bQBySOIbqn4%2FYXu2jYB2SvqOj3KatdJJBxMGLXO4sCMFtlgdmFL3iSKOVHNvNqSrAGc1Z0fjxtDH2o0iMk7tCeCmGnkzO9rvlFgw%2BW0RttWwmrtHuyGBlrGyltSXjKOdrX4Mg9KIwlOjhMdBRtrjjYhkxS39EQTObS%2BF5tDn58MPaluIKOenLQ2veA65IAWNT%2FNk00svwbn7%2BwsN9pPH20OngSU51dKGT7mgtmF%2FovUuYnAVY0Rx62MRawTVhzPLMPBbttxUDq%2B5cqGb4rOAZA%2FXELxMWrpSC2oNlL1zgYTJeIEGMlAVPLHMcA7dUL4I%2FmX1qilc7gw%2FvHEuAY6pgHZrIBgvn4QM6lOaL%2Bg6UitDZ2%2BEZKnlLQDvbFLn2ujuP56TBg3dFePjLJlKmrfO2%2F8yd0h0GKj12PsfkfAIzVBpRpMcTv%2FGy6hUDkz%2FMjI5DLCwrtDwMHz%2B2hug36hnKokK6I6v5AU5KB6VX8vUhQf3qZ6LzCsbT%2FWsg%2F2ZRfxWcNgQsuuBxcAGF6VAoostCKsRLGhqnRsIathHQSs4xgM0iiCY%2B6b&Expires=1729203606

Configuration of the HTML to PDF converter module in one of the affected Zaps:
 

 


@RBrunskill 

This might be something for @PDF.co_API Support to look into.

@RBrunskill 

Possible workarounds to check/try:

Zap Action: PDF.co - Anything to PDF Converter

 

Zap Action: PDF.co - Custom API Call

 

Switching to using “Anything to PDF Converter” fixed the issue. It definitely seems that the HTML to PDF converter is no longer able to discern between HTML and a URL, even though it says you can input either.

@RBrunskill 

Most Zap apps are created and managed by the app developer using the Zapier Developer Platform.

I’d recommend reaching out to PDF.co Support for help troubleshooting their Zap app integration and APIs.

Reply


Terms & Conditions