This article explains how to create, configure, and use custom data properties to extend your document capabilities beyond the standard fields. Custom data fields can now also be auto-populated by AI when a contract is signed or uploaded, saving you from manual data entry.
What is Custom Data?
Custom Data enables you to define and use your own document properties as a complement to the default properties that all documents have (such as company name, document title, and creation date).
Instead of being limited to standard document fields, you can create custom properties like Project ID, Purchase Order Number, Department, Industry Type, or any other data points relevant to your workflow.
Why Use Custom Data?
The default document properties don't cover every business need. Custom Data solves this by letting you define exactly the fields you need.
Key Benefits:
Better Organization: Filter and search documents using criteria relevant to your business.
Improved Workflow: Set up conditional logic based on your custom properties.
Enhanced Tracking: Monitor documents by project, department, or other custom categories.
Flexible Data Management: Adapt the system to your unique business requirements.
AI Auto-Population: When a contract is signed or uploaded, AI reads the document and fills in your custom fields automatically — no manual entry required.
Supported Field Types
When creating a custom data field, you can choose from:
Text fields – for names, industries, IDs, or free text values.
Number fields – for numeric values like "Number of licenses = 250."
Yes/No fields – for simple choices like "Auto-renewal = Yes/No."
Set values – define a list of approved options like "Plan = eSign/Professional/Enterprise"
These field types make it easier to sync with CRM fields and create smarter conditional content. All four field types are also supported for AI extraction.
Custom Data Capabilities
Custom Data includes three main functionalities:
Custom Data Settings – Configure what properties can be used on documents, templates, and rooms.
Conditional Logic – Set conditions based on your custom fields to show or hide content dynamically.
Filter & Search – Search and filter documents in Contract Management using your custom fields.
Setting Up Custom Data Properties
Creating Custom Properties
Navigate to your Entity Settings.
Select Workflows from the sidebar menu.
Under Custom Data, click Add new.
Configure the field:
Label: Choose a descriptive name (e.g., Project ID).
Key: One word, starting with a letter (e.g., project_id).
If mapping to CRM fields, use merge tags like
custom.project_idorcustom.industry.Remove curly brackets when configuring.
Field Type: Select Text, Number, Yes/No, or Set values.
Adding Custom Data to Templates
Create or edit a template.
Access the Document Properties section.
Add your custom data fields.
When documents are created from this template, those fields will be available for use.
Setting Custom Data Values
During Document Creation: Enter values for your custom fields in the creation form.
Via CRM or API Integration: Automatically populate values using CRM fields or API calls.
Via AI Auto-Population: When a contract is signed or uploaded, AI reads the document and fills in any empty custom fields automatically. AI will never overwrite a value you've already entered manually.
Supported CRMs: Salesforce, HubSpot, Microsoft Dynamics, Upsales, Pipedrive.
Using Custom Data in Conditional Logic
You can show or hide content blocks based on your custom fields.
Steps:
Select the content element you want to control.
Open Conditional Logic settings.
Choose your custom field as the condition trigger.
Define the rule (equals, contains, greater than, yes/no).
Decide what happens when the condition is met.
Searching and Filtering with Custom Data
In Contract Management, you can filter and search documents based on your custom data values.
Steps:
Open the filter panel.
Select your custom fields.
Apply criteria to view documents that match.
AI-extracted values appear as filterable columns in the list view automatically — no extra configuration needed.
AI Extraction for Custom Fields
AI extraction for custom data fields is part of AI Contract Management. When a contract is signed or uploaded to GetAccept, the AI reads the document and automatically fills in any custom fields that are attached to the contract — the same way it already handles standard fields like notice period, payment terms, and contract dates.
This means fields like indexation percentage, SLA tier, region, or any other business-specific data point can be populated without anyone copying values out of a PDF by hand.
How it works:
AI extracts values for any custom fields attached to the contract template or manually added to the contract before signing.
All four field types are supported: text, number, boolean (Yes/No), and set values.
AI only fills empty fields — it will never overwrite a value that was entered manually.
Extracted values appear in the contract details view and as filterable columns in the list view, with no extra configuration required.
AI-extracted values are marked with an AI attribution indicator in the contract details view, so you can always tell where the data came from.
Note: AI extraction for custom fields is available as an add-on on Professional and Enterprise plans. It is not included in the E-sign plan or web/sales trials.
Extracting custom fields from contracts already signed
If a contract was signed before a custom field was added to the template — or if you want to re-run extraction — you can trigger it manually using the retro flow:
Open the signed contract.
Go to the Custom Data section.
Click + Select custom data field to add the field you want extracted.
Click the Re-analyze with AI button at the top of the contract details panel.
Pro-tip: Custom fields must be present on the contract at the time of signing for AI to extract them automatically. If you add a new custom field to your template going forward, use the retro flow above to backfill values on contracts that were already signed.
Limitations of AI custom field extraction
Fields must exist before signing. AI can only extract custom fields that are on the contract at sign-time. Use the retro flow for contracts that were signed before the field was added.
Template-scoped, not contract-type-aware. AI extracts whatever fields are attached to the template, regardless of what type of contract it is. If you use one template across different contract types, AI will attempt to extract the same fields for all of them. The recommended workaround is to use separate templates per contract use case.
No confidence scores yet. AI-extracted custom fields do not currently show a confidence signal. This is planned for a future release alongside standard fields.
No field descriptions yet. Admins cannot yet add a plain-language description to guide the AI on what each field means. This is coming in an upcoming release.
Limitations & FAQ
Q: What field types are supported?
A: Text, Number, Yes/No fields, and Set values.
Q: Can I change the type of a field after it's created?
A: No. Once created, the field type cannot be changed. All existing custom data fields created before this update are treated as Text fields. If you need another type, you'll need to remove and re-create the field.
Q: Why does this matter for CRM integrations?
A: About 20% of CRM fields are numbers or yes/no values. Previously, these couldn't sync into GetAccept. Now they can, making your contracts and automation much more powerful.
Q: Can I use Number and Yes/No fields in conditional content?
A: Yes, these fields can now drive conditional content, allowing you to automatically show or hide clauses based on CRM data.
Q: Does this work with all CRMs?
A: Yes, as long as the backend integration supports the field type (Salesforce, HubSpot, Microsoft Dynamics, etc.).
Summary
Custom Data Properties let you go beyond standard fields by adding Text fields, Number fields, or Set values that sync with your CRM, drive conditional content, and make documents easier to search and filter. This gives you smarter personalization, fewer templates to manage, and cleaner contract workflows.