Docs/ReferenceReference
Using custom fields in Sendify
Custom fields are what you already know about a lead. Sendify can put them in a message, hand them to the AI as context, and write new answers back.
On this page
Where your fields come from
| Account type | Where fields are defined | How values arrive |
|---|---|---|
| GoHighLevel | Your GoHighLevel sub account | Contacts sync with their custom field values when the sub account is connected |
| Sendify Direct and API | Settings, Contact Custom Fields | Sent as customFields keyed by field key on the contact endpoints |
Keys have to match
Putting a field in a message
The reliable way is the picker: click the tag icon next to the field you are editing and it pulls up every available field to choose from. If you would rather type it, start with the merge field prefix and pick the field you want.
Merge field
{{contact.custom.xxx}}Replace xxx with the field you are referencing. Use the picker to get the exact name rather than guessing at it, since a field that does not resolve is worse than not personalizing at all.
Merge fields work inside initial messages and throughout your prompting, which is covered in initial messaging and lead context.
Fields as AI context
Anything the field already tells you is something the AI does not need to ask. A lead whose service interest, city, or budget band is populated should get a conversation that starts from there. Feed those fields in as lead context and let the qualification questions cover what is genuinely still unknown.
Capturing answers back into fields
When the AI learns something worth keeping, an automation trigger can write it to a contact field or a custom field. Triggers can also generate a summary, notify a rep, and switch AI behavior. See automations and triggers.
For GoHighLevel accounts that write lands on the contact in your CRM. For API accounts you receive the contact.updated event with the changed fields, documented in the API reference.
Blank and missing fields
Write every message so it still reads naturally with the field empty, and test with a deliberately blank contact during your launch checks. On the API, custom fields shallow merge on update: keys you do not send are preserved, and sending a key as null removes that value.
FAQ
How do I insert a custom field into a message?
Click the tag icon next to the field you are editing and pick from the list, or start typing {{contact.custom. and choose the field you want.
Where do custom fields come from?
GoHighLevel accounts inherit the sub account's custom fields. Sendify Direct and API accounts use the fields defined in Settings, Contact Custom Fields, and push values by key over the API.
Can the AI read custom fields?
Yes. Field values are part of the lead context the AI sees, so it can reference what you already know about the lead instead of asking again.
Can the AI write to a custom field?
Yes, through an automation trigger that updates a contact field or custom field.
What if the field is empty?
Never write a message that only reads correctly when the field is populated. Use the picker to confirm the field is the one you mean, then test with a contact that has it blank before you launch.
Still need a hand?
If your volume is going to run past the daily or hourly limits, or something is not behaving the way these docs describe, talk to our team.