The Meta and WhatsApp integration is the delivery layer of Galantis. Where the Shopify integration provides the data — customer profiles, orders, products, consent — the Meta integration is what turns that data into actual WhatsApp messages reaching customers’ phones. Galantis communicates with Meta through the WhatsApp Cloud API (Meta Graph API v23.0), using your WhatsApp Business Account access token to send messages, submit templates, upload media, and push catalog data. Inbound messages and status updates from Meta arrive via webhooks registered to your WABA.Documentation Index
Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
Use this file to discover all available pages before exploring further.
What the Meta integration provides
- Outbound messaging — campaigns, automation messages, and Inbox agent replies sent via the Message API
- Template management — template creation, submission, and approval status sync via the Template API
- Media upload — images, videos, and documents uploaded for use in template headers via the Media Upload API
- Catalog sync — product data pushed from Galantis to Meta via the Catalog API
- Inbound messages — customer messages received through your WhatsApp number arrive via webhook and appear in the Inbox
- Message status updates — delivered, read, and failed status callbacks for every sent message, used for analytics and automation condition evaluation
Guides in this section
Connecting WABA
The Meta OAuth flow, token storage, phone number registration, and reconnection.
Meta Webhooks
Inbound message webhooks, message status updates, and template status change events.
Multiple Phone Numbers
Adding and managing multiple WhatsApp Business phone numbers per workspace.
Meta API endpoints used
| API | Endpoint | Purpose |
|---|---|---|
| Message API | POST /{phone_id}/messages | Send all outbound WhatsApp messages |
| Media Upload API | POST /{app_id}/uploads | Upload images, videos, and documents (resumable protocol) |
| Template API (create) | POST /message_templates | Submit new templates for Meta review |
| Template API (read) | GET /message_templates | Fetch template list and current approval status |
| Template API (delete) | DELETE /message_templates | Delete a template |
| Catalog API | POST /{catalog_id}/products | Push product data to Meta Catalog |
v23.0. Calls are made by MetaGraphClient using the merchant’s encrypted access token per tenant.
Authentication model
Galantis stores one Meta access token per connected WhatsApp Business Account, encrypted per tenant. The token is obtained via Meta OAuth during the WABA connection flow and used for all subsequent Meta API calls. Access tokens can expire or be revoked if permissions change in Meta Business Manager. When this happens, all Meta API calls from Galantis fail for that workspace. Symptoms include messages not sending, catalog sync failing across all products simultaneously, and template status no longer updating. See Connecting WABA for how to reconnect and refresh the access token.Related guides
- Getting Started — WhatsApp Connection — Initial WABA connection walkthrough
- Catalog — Meta Catalog — How Galantis uses the Catalog API
- Templates — How Galantis uses the Template API