I’m experiencing a blocking issue with the Bubble Page to PDF Converter plugin.
The problem is that the “Get token” action and/or the “Token” field cannot grant access to private Bubble files. The plugin’s “Token” feature does not work for private files, and as documented it cannot work.
Expected:
Per your docs, running “Get token”, passing the result into Generate PDF’s “Token” field, and appending it to private image URLs as “?api_key=[token]” retrieves private files.
Actual:
Private images render blank in the PDF after downloaded. The plugin serializes the page and re-fetches each image from its own server without a user session, so Bubble refuses the request.
Root cause:
Bubble ignores “api_key” as a URL query parameter on file routes (/fileupload/…). I tested the same URL with/without the parameter & with/without a raw Bubble API key—all returned 401. Bubble honors credentials on these routes via an Authorization: Bearer header, which cannot be expressed in .
My Ask:
Allow custom request headers (specifically auth) to be sent when the plugin fetches page assets. Until then, please correct the documentation—the “?api_key=” instruction is not functional.
