Use Custom Values to Dynamically Fill Form Fields under Documents and Contracts
Y
Yader Centeno
Use Custom Values to Dynamically Fill Form Fields under Documents and Contracts with birth date, client name, any custom value set. It would fill automatically. The recipient has the option of deleting or updating the field they choose without affecting the rest of the form.
eg.
{{ custom_values.refferedby }}
{{ contact.first_name }} {{ contact.last_name }}
{{ contact.date_of_birth }}
{{ contact.city }}
{{ contact.state }}
Photo Viewer
View photos in a modal
Log In
S
Sales & Marketing
Merged in a post:
MORE custom values in contracts.
A
Allie Burke
Right now I can not put in appointment date or location.
S
Sales & Marketing
Merged in a post:
Pre-populate linked Contract fields from Contact/Opportunity before signing
O
Omar de Santos
Problem: In Contracts, “linked” fields only write back after signing. Senders cannot pre-populate those inputs with existing Contact/Opportunity data. This forces recipients to re-type info we already have, increases friction and errors, and makes the experience inconsistent with Forms (which support sticky/prefill patterns).
Why this matters:
Lower friction & faster completion: Fewer keystrokes → higher completion rates and better mobile UX.
Data accuracy: Using CRM as the source of truth reduces typos and mismatches.
Consistency: Aligns Contracts with Forms behavior (sticky/prefill), and with CRM merge fields that already render data.
Advanced use cases: Service businesses with multiple jobs per customer need Opportunity-level data to prefill job-specific contracts (amounts, dates, locations).
Requested behavior:
When a fillable field is “linked” to a Contact or Opportunity value, auto-populate the input on open with the current CRM value.
Allow toggles per field: Prefill + Editable (default) or Prefill + Read-only.
Support Opportunity and Company fields everywhere merge values are supported.
Preserve existing write-back on completion (so edits still sync if allowed).
Allow prefill via URL parameters or workflow actions when generating the contract (advanced templates).
Benefits: Reduced abandonment, fewer errors, and a more professional e-signature experience; no need for brittle workarounds mixing merge text with separate inputs.