LeadSquad

Azmarq’s custom connect for LeadSquad maps CRM events to Azmarq sends. It is not a public marketplace listing in this hub, and it is not a new Omni HTTP route — there is no POST /v1/leadsquad.

Enable the connector with Azmarq onboarding (integration@azmarq.com). Custom or server-side sends still use SMS, WhatsApp, and RCS with the apikey header.

Salesforce

WebEngage

SMS API

What the connector is

Use it when LeadSquad should trigger WhatsApp, SMS, or RCS from leads and campaigns inside LeadSquad, without posting Omni JSON yourself.

Sibling custom connects: Salesforce, WebEngage.

Enable it

Ask Azmarq integrations to turn on the LeadSquad connect for your account.
Connect the LeadSquad workspace and the Azmarq dashboard.
Map the lead or campaign event that should send.
Test on a sample lead before production.

When to use Omni HTTP instead

Use the custom connect when LeadSquad users and automations own the send.

Use Omni HTTP when your backend owns the request:

POST /v1/sms
POST /v1/whatsapp
POST /v1/rcs