Templates and e-signing
Merge-field documents and the signing lifecycle.
01What makes a template
A template is simply a document whose text carries merge fields such as {{customerName}}. Upload an HTML or plain-text file containing them and it wears a Template badge — there is no separate type to choose, and nothing to configure.
02Generating
Generate asks which job to render the template against and fills the fields from it, so a contract is the template plus one booking rather than a file you edit by hand. The result files alongside your other documents, attached to the job it was made for.
03Sending for signature
Send names the signer and how long the request stays open — thirty days is the ceiling the signing link itself enforces. The signer gets their own page and needs no account. Status moves draft to sent to signed or declined, and the audit trail behind it is written and held server-side, never assembled from what the browser saw.
04Voiding
Voiding a sent request stops it being signed from that point on. What already happened stays in the audit trail — voiding closes the request, it does not erase it.
05Doing it automatically
A flow can do both steps for you: Generate document and Request signature are actions you can place on the graph, and the flow can wait for the signature to come back before moving the job on.