Integrations
What it's for
Integrations connects your company's own accounts with outside services, using your own keys: payment gateways (buyers pay into your account), WhatsApp providers (messages from your own number), Facebook and Instagram lead ads, and calling. It also holds the WhatsApp sender card, which decides which number WhatsApp messages go from.
Before you start
- Any ERP module must be active. You need the integrations permission (owners always have it).
- Have the keys from your provider account ready. Use test keys first where the provider offers them.
The page
- WhatsApp sender card at the top: the platform number (default), your own number, or Off. See WhatsApp: platform number or your own.
- Show providers for: India, East Africa or Global narrows the list to providers used there.
- Sections: Payment gateways, WhatsApp, Lead sources and Calling. Each provider card shows its logo, where it is used, and its status.
- Links at the top open Message templates and Message log.
Connect a provider
- On the provider's card press Connect.
- Environment: Test or Live. Use test keys first; live keys are for real customers.
- Paste each key the dialog asks for. Show what you typed lets you check before saving.
- Press Save keys. The status is Not tested yet.
- Press Test connection. The app makes one signed-in call to the provider. Success sets Connected; a failure sets Needs attention with the provider's reason.
- Copy the Webhook URL shown on the card and paste it into the provider's dashboard, so it can tell the app about payments, delivery statuses or new leads.
Statuses
| Status | Meaning |
| Not connected | No keys saved for this provider. |
| Not tested yet | Keys saved; press Test connection. |
| Connected | The test call worked. The provider is used. |
| Needs attention | The last test failed. Check the keys and environment. |
| Disabled | Switched off. Nothing uses these keys until you test again. |
Other actions on a card
- Edit keys: replace keys. Saved keys are never shown again; leave a field empty to keep it.
- Make default (payment gateways only): new payments use this gateway.
- Disable: stop using the keys without deleting them. Remove: delete them.
- New webhook URL (providers that use a token in the URL): makes a new address; the old one stops working at once, so paste the new one into the provider.
How keys are protected
Every key is stored encrypted and is write-only: once saved it is never sent back to the browser and never written to logs. For some providers the last four characters of a public identifier (such as a key ID) are shown so you can tell which account is saved.
What happens automatically
- Saving, testing, making default, disabling, removing and new webhook URLs are written to the activity log.
- Incoming webhooks are checked: signed providers must carry a valid signature; token providers must use the secret address. Anything else is refused.
Tips and common questions
- Connected, but payments or messages fail? Wrong keys often show up only as failed messages or payments. Check the Message log or Online payments → Gateway events.
- I cannot edit gateway keys. Your company's gateway keys may be set by the platform team (Internal controls). Contact support.
- Facebook and Instagram lead ads are set up from the CRM's Lead ads page.
Related: Payment gateways · WhatsApp sender and providers · Webhooks