E
Elion Leci
Currently GHL only supports WhatsApp Flows built natively inside
GHL (Settings > WhatsApp > Flows), which are limited to
appointment booking with minimal customisation.
Meta's Flow Builder allows significantly more complex and
customisable Flows - multi-screen forms, custom data capture,
conditional logic, styled screens - that GHL's native builder
cannot replicate.
The feature request is:
  1. Allow Meta-published WhatsApp Flows to be selectable in GHL
workflow WhatsApp Flow actions, in the same way Meta-approved
templates already sync and appear in workflow actions.
  1. Allow Meta-created templates with Flow buttons to resolve GHL
contact field variables ({{1}}, {{2}} etc.) in the same way
GHL-native templates do.
This would allow businesses to build sophisticated WhatsApp Flow
experiences in Meta - qualification forms, intake forms, feedback
surveys - and deliver them through GHL workflows with proper
variable resolution and contact field mapping.
The infrastructure is partly there - Meta templates sync to GHL
workflow actions already. Extending this to include Flow button
templates and Meta-published Flows is the logical next step.