Performance marketers need one thing from a CRM that ad platforms cannot supply on their own: proof of which campaigns produced revenue, not just conversions. That requires the lead to carry its source all the way to a closed-won opportunity. Sales teams in India also need WhatsApp and, for commerce-oriented tenants, payment and catalog tools beside the same record.
The chain that has to hold
What Vertex CRM connects today
| Integration | What it does | Where you configure it |
|---|---|---|
| Meta Ads / Lead Ads | Connect ad accounts and ingest Lead Ads into CRM leads | Setup → Integrations |
| Google Ads (where enabled) | Ads visibility and related marketing workflows | Setup → Integrations |
| WhatsApp — AiSensy | BSP Project API send + project webhooks into Inbox | Integrations → WhatsApp |
| WhatsApp — Meta Cloud API | Direct Cloud API send/receive into the same Inbox lane | Integrations → WhatsApp |
| Email marketing | Lists, campaigns, flows beside CRM records | Marketing modules |
| Razorpay / shop payment links | Create shareable payment links from Inbox (shop API preferred) | Integrations (Razorpay / HealthyOme-style shop) |
| Catalog cards (commerce) | Pull live plans / products into WhatsApp replies where configured | Shop / HealthyOme connector |
| Inbound leads webhook | POST /webhooks/inbound-leads for partners and middleware | Org webhook secret |
Integration philosophy: prove one, then expand
Integration projects fail by trying to connect everything at once. Turn on a single flow—usually lead capture from your highest-spend channel, or WhatsApp for India GTM—prove it produces attributable pipeline for a quarter, then add the next. An integration nobody has validated is an unmonitored dependency.
Secrets, without exceptions
- App IDs, secrets, Project API keys, and redirect URLs live in org settings (encrypted) or environment variables—never in source control, never in a shared document
- Rotate tokens after any staff change that touched them
- Grant the narrowest OAuth scopes the integration needs, and re-check them when the vendor expands their API
- Log integration failures somewhere a person actually looks; silent failure is the normal failure mode
OAuth’s role here is to authorise scoped, revocable access between Vertex CRM and a provider account, with refreshable tokens—so an integration can be withdrawn without changing anyone’s password. BSP API keys (e.g. AiSensy) should be treated with the same rotation discipline.
Where each piece sits
Idempotency, or duplicate leads forever
Webhook deliveries retry. If your ingest creates a record per delivery rather than per event, a provider retry becomes a duplicate lead, and duplicates become two sellers calling the same person. Process by a stable event identifier and make repeat deliveries harmless. Vertex CRM exposes POST /webhooks/inbound-leads for middleware and partner systems; treat its shared secret like any other credential. The same discipline applies to /webhooks/whatsapp and /webhooks/aisensy.
What integration cannot fix
If sellers do not record loss reasons, no amount of ad-platform integration will tell marketing why campaigns underperform. Attribution is a data-discipline problem wearing an engineering costume.
Related: WhatsApp CRM in India, marketing and sales alignment, lead tracking, and security for the secrets discussion.
Frequently asked questions
- Where are integrations configured?
- After sign-in, administrators use the Integrations area for what your deployment exposes.
- What is OAuth’s role?
- OAuth authorizes scoped access between Vertex CRM and provider accounts with refreshable tokens.