Triggered Screenshot Rendering

HTML to Image renders a web page, dashboard, or HTML template into an image file through an API call. A Beam agent triggers a render when an approved event occurs, such as a weekly report being ready or a dashboard needing a fresh snapshot for a shared document, passing the correct URL or template and any required parameters. Once the image comes back, the agent attaches it to the record or document that requested it. Requests referencing a page the agent cannot confirm still exists, or missing required parameters, are held back, and the case is flagged for a person to check first.

Rendered Image Attachment and Storage

A freshly rendered image from HTML to Image needs to land somewhere useful, whether that is a slide, a shared report, or a customer record. A Beam agent reads what triggered the render and, where the connector allows it, places the image in the corresponding document or folder, following the customer's approved naming and file structure. It updates the originating record to note where the image now lives. Images tied to a document the agent cannot confidently match, or that would overwrite an existing file with the same name, are held for a person to place manually instead.

Render Failure Recovery

A render can fail in HTML to Image when a source page times out or a referenced asset fails to load. A Beam agent reads the API response for a failure and applies the customer's approved retry rule, such as a second attempt after a short delay for a timeout. If the retry also fails, the agent notifies the owner of the requesting record that the image could not be produced. Failures from a page that no longer exists, or an error type the rule does not cover, are routed to a developer instead of retried repeatedly.