Allow checked boxes in contracts to be linked to custom fields and be used in workflows
E
Eric Langley
Allowing contract checkboxes to link to custom fields and be used in workflows will enable updating contact records based on which boxes are checked in a contract and triggering workflows with those updates.
Log In
S
Sales & Marketing
Merged in a post:
Make Checkboxes in Documents Functional and Connected to Workflows
N
Nitay Ben Zvi
While GoHighLevel currently supports checkboxes in Documents and Contracts, they are unfortunately static and non-functional. Right now, a user can check or uncheck them, and even choose from grouped options — but the platform does nothing with that input.
To make checkboxes truly useful, they should behave more like checkboxes in Forms and be tied into automation or values, allowing the system to store the data and act on it. Here’s what’s needed:
1. Link checkbox values to contact fields or custom fields, so that when a signer selects an option, it’s saved as part of their profile or deal.
2. Use checkbox selections in workflows, enabling follow-up actions (e.g., “If Checkbox A is selected, send onboarding email A”).
3. Allow labels and values for each checkbox, so it’s easy to identify the selected option and use it in automations or internal logic.
4. Make grouped checkbox logic actionable, especially for multiple-choice or mutually-exclusive selections.
5. Store checkbox selections in document submission data, so that it’s visible in contact activity, notes, or internal summaries.
Checkboxes have huge potential for capturing client preferences, service selections, consents, upsells, and more — but currently, they’re mostly aesthetic. With a bit of functionality, they can become a powerful tool for interactive documents and contracts.
R
Ricardo Gomez
I came to the feedback board to literally leave this same suggestion. It would be extremely useful to have conditional logic enabled for checkboxes within contracts and documents or through automations whichever is fine. I have a document that i need to sent to clients and it asks for their gender and preferred language. I created a pdf document where the lead can click a check box for their gender and preferred language, but come to find out that the checkboxes basically have little to no backend use.
A
Andrew Langhammer
I’m creating a document with Opportunity record fields and Contact record fields. When I use a Contact with an Opportunity created against it, the Contact information is added, but the Opportunity information isn’t. How do I get the form to recognise the Opportunity information?
Why does the form builder allow you to select Opportunity fields within the Contact field tree if it's to going to fill them?
C
Christy Allison
This would make how we use Contracts and Documents infinitely more powerful.
M
Michael Danklefs
I was just trying to implement using the checkboxes in a contract to act on it. What use is the checkbox if there is no action behind it? Please add the ability to map this to a contact field, opportunity field, or even access it in the workflow to take different actions, like Nitay stated.