Document Merge Fields

Formstack Documents merges field values into a template, producing a contract, invoice, or letter without anyone typing it by hand. A Beam agent watches for a completed form or a new record in a connected app, checks that the required fields are present, and applies the approved rule for which template to use, then generates the document and files it in the agreed location. If a required field is missing, the source record looks incomplete, or the wrong template would apply, the agent sets the record aside and notes what is missing for a person to fill in before the document goes out.

PDF and Signature Delivery

Once a document is generated, it usually needs to reach a signer or a filing system in a specific format. A Beam agent reads the completed document, applies the customer's approved rule for where it belongs, such as a specific folder, an e-signature request, or an email to the recipient on file, and updates the source record to show the document has gone out. Deliveries where the recipient address is missing, the document failed to render correctly, or the destination system rejects the file are routed to a person to fix and resend, with the original error kept for reference.

Template Version Selection

Formstack Documents can hold several template versions for the same form, and picking the wrong one sends out a contract with outdated terms. A Beam agent reads which version the customer has approved as current, applies that rule when a document is requested, and generates the file from the correct template rather than defaulting to whichever was uploaded last. Requests that specify no template, reference one that no longer exists, or come from a form the agent does not recognize are left for a person to route by hand, so version control does not depend on memory alone.