Template-Based Document Assembly

DocuMerge assembles a finished document, such as a contract, letter, or report, by combining a template with live data. A Beam agent starts this assembly when a matching event occurs, for example a new record in a connected system, reads the required fields from that record, and applies the account's approved rule for which template applies. The finished file is then placed back into the workflow or a person is notified that it's ready. Records with missing fields, conflicting data, or an unrecognized template request are routed to a person instead of being produced automatically.

Merge Field Mapping

Every DocuMerge template relies on merge fields that pull specific values, like a name, date, or amount, from connected data. A Beam agent reads the source record, matches each value to the correct merge field according to the account's approved mapping, and fills the template accordingly. This removes the manual copying that normally happens when producing repetitive documents from the same layout. Where a field is empty, formatted unexpectedly, or falls outside the approved mapping, the agent routes the record to a person rather than guessing at the missing value or producing an incomplete document.

Regeneration on Source Data Change

Documents built from a template can go out of date when the underlying record changes, for instance an updated address or contract term. Where the connector and account permissions allow it, a Beam agent detects that change, reapplies the approved template rule, and regenerates the affected DocuMerge document so it reflects the current data. The previous version can be flagged or replaced according to the account's setup. Any change that falls outside the agreed rule, such as a term needing approval, is routed to a person before a new document reaches anyone.