Triggered Document Generation

HTML 2 PDF turns a web page or HTML template into a PDF file through an API call. A Beam agent triggers this conversion when an approved event occurs elsewhere in the stack, such as an invoice being finalized or a report being marked ready, passing in the correct template and data for that record. Once the PDF comes back, the agent attaches it to the originating record so the file sits alongside the invoice or report it belongs to. Requests with missing or malformed template data are held back, and the agent flags the record for a person to fix before generation is retried.

Generated File Routing and Storage

Once HTML 2 PDF produces a file, it needs to land in the right place, whether that is a customer record, a shared drive folder, or an email attachment. A Beam agent reads the context behind the conversion and, where the connector allows it, stores the resulting PDF in the corresponding folder or record, naming it per the customer's approved convention. It notes the storage location back on the originating record for easy lookup later. Files tied to a record the agent cannot confidently identify, or a naming conflict with an existing file, are left in a holding folder for a person to place manually.

Conversion Failure Alerts

A conversion can fail in HTML 2 PDF when the source HTML is malformed or a referenced asset like an image or font cannot load. A Beam agent checks the API response for a failure and applies the customer's approved retry rule, such as attempting the conversion again after a short delay for a timeout error. If the retry also fails, the agent notifies whoever owns the originating record that the document could not be generated. Failures tied to a template change or a new, unrecognized error type are routed to a developer to investigate rather than retried indefinitely.