Create these fields in GHL Settings → Custom Fields. Order matters — create Contact fields first, then Opportunity fields.
Create BEFORE configuring the bot. The bot references these field keys in its prompts. If fields don't exist when the bot tries to save data, the data will be lost.
Full bot conversation summary for human handoff context
11
Fecha de descalificación
disqualification_date
Date
When the lead was disqualified (for reporting)
12
Pixel event enviado
pixel_event_sent
Text
"Yes" / "No" — tracks if conversion event was sent to ad platform
Opportunity Fields OPPORTUNITY
#
Field Label (ES)
Field Key
Type
Purpose
Copy Key
1
Fecha de entrada al stage
stage_entered_date
Date
Track pipeline velocity per stage
2
Razón de descalificación
disqualification_reason
Text
Why the deal was lost (copied from contact field)
3
Monto de propuesta
proposal_value
Number
Proposal/projected deal amount for forecasting
4
Fecha esperada de cierre
expected_close_date
Date
Forecasting timeline
5
Origen del deal
deal_source
Text
Attribution: "bot", "manual", "referral"
6
Resumen del bot
bot_summary
Text Area
Bot conversation context for the opportunity
Order: Create all 12 Contact fields first (GHL Settings → Custom Fields → Contact). Then create all 6 Opportunity fields (GHL Settings → Custom Fields → Opportunity). Use the exact field keys shown above — the bot references these by key, not label. GHL auto-generates the key from the label, so verify after creation.
Sierra Nevada Holdings · Custom Fields Table · hl-subaccount-config-v1