Browse docs and guides
Map CRM fields and sync completed DocuSign answers
LC Bridge connects GoHighLevel contact data to DocuSign template fields. After the agreement completes, mapped client-entered answers can return to the configured GoHighLevel contact fields.
Prepare the template and contact fields
Use your existing DocuSign account and template. Identify the recipient roles and fields that need CRM values, and the fields the signer will complete. Create the corresponding GoHighLevel contact fields before mapping.
Use a dedicated destination custom field when the signer supplies an additional person’s details. For example, a co-buyer name should not replace the primary contact’s name.
Map and preview before sending
- Connect DocuSign and choose the intended template.
- Map prefill values to the right GoHighLevel contact or selected recipient role.
- Configure where client-entered values should return after completion.
- Preview the resolved values and document. Check empty fields, date formats, email addresses, and recipient assignments.
- Send the agreement using the configured contact or workflow action.
For a document with several recipients, follow the multiple-signers guide and map each field to the intended selected contact.
Check the completed agreement
Wait until all required signing is complete, then verify the mapped answers on the destination contact. A partially signed agreement and a completed agreement are different states. Review the final values before enabling a workflow that depends on them.
Find the signed PDF
Agreement activity and signed PDF access are connected to the contact record. Contact-file attachment depends on configured storage settings and permissions. Verify your destination and access policy during setup rather than assuming every PDF appears in the same contact file list.
Prevent common mapping mistakes
| Symptom | Check |
|---|---|
| Prefill value is blank | Confirm the source contact has a value and the correct template field/role is mapped. |
| Answer appears on the wrong record | Review recipient-role contact selection and the configured write-back destination. |
| Primary identity changes unexpectedly | Use separate custom fields for secondary-person details and inspect the mapping before sending. |
| Answer has not synced | Confirm all required signers finished and that a return mapping exists. |
| Signed PDF is not in contact files | Check configured storage settings, permissions, and the agreement’s PDF access. |
Next: getting started, workflow configuration, or capabilities and requirements.