Custom Fields & Custom Values
Per-account schema extension and templated tokens.
Overview
Custom Fields extend the contact (and other objects) with account-specific data. Custom Values are reusable tokens (like merge fields for business info) that can be dropped into templates so one change propagates everywhere.
What it's for
Capture structured data unique to a business and keep reusable text (phone, hours, address) DRY across templates.
Capabilities
Field types
Text, number, currency, date, dropdown, checkbox, radio, file upload, URL, phone, email.
Contact custom fields
Attach to contact records; usable in forms, workflows, and templates.
Custom Values
Global key/value tokens for business info, inserted into any template with a placeholder.
Merge fields
Insert contact or custom-value data into emails, SMS, and documents.
Required + validation
Mark fields required and constrain formats (e.g. phone, email).
Use cases
Templated business info
Store the business phone as a Custom Value and reference it in every email footer so a single edit updates all templates.
Industry-specific capture
Add a 'service_address' custom field to collect job-site info on a form and use it in a follow-up workflow.
AI prompt patterns
Copyable templates for prompting an AI agent about this feature.
List the custom fields (name, type, required) a [industry] business needs to capture on its lead form to support [automation goal].List the Custom Values (key + description) this account should define so business info stays consistent across email/SMS/funnel templates.Integrations & connections
- Forms write directly to contact custom fields
- Workflows read and set custom fields as conditions and actions
- Templates render custom values as merge tokens
Gotchas & limits
Things an AI should not assume about this feature.