W
Wesley Schiesari
Today, when using the official WhatsApp API within HighLevel, it should be possible to send templates approved directly by the public API, stating the name of the template. Currently, this shipment is not practically exposed by the API for external integrations, even with the use of templates already being part of the product experience in other areas of the ecosystem.
Why is this important
  • Allows external systems, custom integrations, and middlewares to trigger approved templates more easily
  • Reduces dependency on manual submission or flow through the interface alone
  • Facilitates operations at scale with transactional templates, utilities, authentication and marketing, which are part of the official logic of WhatsApp within the platform.
Suggested behavior
  • Accept a parameter such as template_name on the message sending endpoint
  • Allow sending template variables/placeholders
Use case
  • A company that uses the official WhatsApp API on HighLevel wants to trigger an already approved template from its backend, external workflow or CRM, using only the exact name of the template and its variables.
·