Before
Teams had to run conversion scripts locally or use separate third-party tools to turn HTML into PDFs. They then had to encode the resulting file and manually return or forward it to the requester for each conversion request.
How it works
- Receive an HTML-to-PDF request through the secure webhook.
- Convert the HTML into a PDF and encode the resulting file as base64.
- Return the encoded PDF directly to the requesting application in a JSON response.
Workflow details
- Request intake: A system or application sends HTML content to the secure webhook entry point when a PDF is needed.
- PDF generation: The workflow processes the HTML, renders it as a PDF, and allows a short delay for JavaScript content to load before completing the conversion.
- File encoding: The generated PDF is read and converted into a base64-encoded result so it can be transmitted within the response.
- Execution handling: If the PDF conversion fails, the workflow stops instead of returning an incomplete result.
- Result delivery: The base64-encoded PDF is placed in a JSON response and returned directly to the original caller for immediate downstream use.
What changed
PDF conversion is now initiated programmatically from a webhook request and completed without operator involvement. The conversion, encoding, and response formatting happen automatically, while the requesting application receives the result directly instead of relying on a manual handoff.
Work removed
Manually running HTML-to-PDF conversion scripts, waiting for the PDF file to be created, encoding the PDF as base64, formatting the response, and forwarding the result to the requester.
Expected outcome
Each request is expected to complete in seconds and remove at least three recurring manual actions: conversion, base64 encoding, and result forwarding.
