Template-Based PDF Generation

CraftMyPDF holds reusable templates built with its drag-and-drop editor, with placeholders for the fields that change each time, like a customer name or an invoice line. A Beam agent triggers when a business event happens, such as an order closing, reads the relevant record, and applies the customer's approved template mapping to fill those placeholders before generating the finished PDF. If a required field is missing or a value doesn't fit the expected format, the agent stops before generating and sends the record to a person to fill in the gap.

API-Triggered Document Creation

CraftMyPDF's API lets another system request a finished document without anyone opening the editor by hand. A Beam agent watches for a trigger, such as a new signup or a closed deal, calls the CraftMyPDF API with the customer-approved template and the matching data, and confirms the document that comes back is correctly formatted and complete. Where the API returns an error, an unexpected template version, or a partially filled document, the agent does not deliver it to anyone downstream, it flags the failed request for a person to look into and resolve.

Output Delivery and Filing

Once CraftMyPDF finishes a document, it usually needs to land in a specific place, like a client folder, an email, or a records system. A Beam agent reads the document type and destination rule a customer has approved, then moves or attaches the finished PDF accordingly and updates the source record to show it is done. Where the destination isn't clear, or the document relates to an account the rule doesn't cover, the agent holds the file and asks a person where it should go.