HTML and CSS rendering

This is the core function: the service takes raw HTML and CSS markup and renders it into a static image file rather than a live webpage. A Beam agent calls the API when a workflow needs a visual snapshot, for example turning a generated report or a formatted record into an image for an email attachment or a shared link. The agent supplies the markup, receives the rendered file back, and stores or forwards it as the workflow requires. Malformed markup or rendering errors get routed to a person to inspect and correct the template before the workflow runs again.

On demand generation via API calls

Images are produced only when requested, through a direct API call rather than a manual export step. A Beam agent triggers a render whenever an upstream event happens, such as a new record being created or a document being finalized, and passes the relevant HTML and CSS to the endpoint. The agent then picks up the resulting image and attaches it to the next step, whether that is a notification, a stored file, or an outbound message. Repeated failures or timeouts on a given request are routed to a person, since retrying blindly could mask a broken template or account issue.

High quality image output

The service is built to produce sharp, high resolution images suitable for use outside a browser, such as in documents, emails, or social posts. A Beam agent relies on this when the rendered image needs to look correct at full size rather than as a quick thumbnail, passing along the source markup and waiting for the finished file. Where the output does not meet the expected size or clarity, for instance due to missing fonts or assets in the markup, the agent routes the result to a person rather than shipping a broken image to a customer or channel.