Skip to main content

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.

Connecting your WhatsApp Business Account (WABA) to Galantis is a one-time OAuth flow that authorizes Galantis to send and receive messages on behalf of your business’s WhatsApp number. The resulting access token is stored encrypted per workspace and used for all subsequent Meta API calls — message sending, template management, media uploads, and catalog sync.

​
What this covers

  • The full OAuth connection flow step by step
  • How tokens are stored and used
  • Phone number registration
  • Catalog token connection
  • How to reconnect when a token expires or is revoked

​
The OAuth connection flow

1

Initiate the connection

In the Galantis dashboard, go to Settings → WhatsApp Connection and click Connect WhatsApp. This calls WhatsappConnectionController@prepareToConnect, which retrieves the Meta OAuth authorization URL for your workspace.
2

Authorize in Meta Business Manager

You are redirected to Meta. Log in with the Meta account that owns the WhatsApp Business Account you want to connect. Review the permissions Galantis is requesting and click Continue to authorize.
3

Token exchange

After authorization, Meta redirects back to Galantis with an authorization code. WhatsappConnectionController@connect exchanges this code for an access token and stores it encrypted in the Galantis tenant database.
4

Select your phone number

Galantis fetches the phone numbers registered on your WABA and presents them for selection. Choose the number you want to use for messaging in this workspace. The selected number is registered as the active sending number.
5

Connect a Meta Catalog token (optional)

If you plan to use product message formats (SPM, MPM, Whole Catalog), connect a Meta Catalog access token from the same settings screen. This is a separate token from the WABA access token — it specifically grants permission to read and write to your Meta Catalog. See Catalog — Meta Catalog for catalog setup.

​
How tokens are stored

Access tokens are stored encrypted per tenant using Galantis’s multi-tenant encryption layer. Each workspace’s token is isolated — one merchant’s credentials cannot be accessed by or affect any other workspace. Tokens are used exclusively for API calls scoped to that workspace’s phone number and catalog. MetaGraphClient handles all Meta API calls and injects the correct encrypted token per tenant at request time.

​
What the access token enables

A connected WABA access token enables:
  • Sending messages via the Message API (POST /{phone_id}/messages)
  • Creating and submitting templates via the Template API
  • Fetching template approval status
  • Uploading media assets for template headers
  • Receiving inbound messages and status callbacks via Meta webhooks
A separately connected Meta Catalog token additionally enables:
  • Reading from and writing to your Meta Catalog via the Catalog API (POST /{catalog_id}/products)
  • Pushing product data from Galantis to Meta
  • Syncing catalog updates via SyncMetaCatalogJob

​
Token expiry and reconnection

Meta access tokens can expire or be revoked when:
  • Permissions are changed or revoked in Meta Business Manager
  • The Meta user account that authorized the connection changes their password or two-factor authentication
  • The app authorization is manually revoked in Meta’s app permissions settings
  • The token reaches its expiry period (long-lived tokens have a defined validity window)
Symptoms of a lapsed token:
  • Messages fail to send across all campaigns and automations simultaneously
  • Template status stops updating in Galantis
  • Catalog sync fails for all products at once (if the catalog token is affected)
  • The Meta webhook connection stops receiving inbound messages
How to reconnect:
1

Open WhatsApp Connection settings

Go to Settings → WhatsApp Connection in the Galantis dashboard.
2

Reconnect

Click Reconnect or Connect WhatsApp — the same OAuth flow runs again. You will be redirected to Meta to re-authorize and a new token will be issued and stored.
3

Verify the connection

After reconnecting, confirm the phone number is still selected and active. Send a test message from the Inbox to confirm outbound messaging is restored.
4

Reconnect the catalog token if needed

If the catalog token was also affected, reconnect it separately from the same settings screen and verify catalog sync resumes by checking Catalog → [Product] status.
Reconnecting generates a new access token. The previous token is invalidated. If the same Meta account authorization is being used by other tools or integrations alongside Galantis, reconnecting in Galantis does not affect those other tools — each has its own token. However, ensure the authorizing Meta account’s permissions in Meta Business Manager have not been reduced before reconnecting, as a token issued with insufficient permissions will not restore full functionality.