Salesforce

Azmarq’s custom connect for Salesforce maps CRM events to Azmarq sends. It is not listed as a public AppExchange package in this hub, and it is not a new Omni HTTP route — there is no POST /v1/salesforce.

What the connector is

Use it when Salesforce should trigger WhatsApp, SMS, or RCS from leads, contacts, or campaigns inside Salesforce, without your team posting Omni JSON.

Sibling custom connects: LeadSquad, WebEngage. Marketplace installs: Zoho CRM, Shopify.

Enable it

1. Ask Azmarq integrations to turn on the Salesforce connect for your account.
2. Connect the Salesforce org and the Azmarq dashboard (sender IDs, WhatsApp numbers, templates).
3. Map the Salesforce object or flow that should send.
4. Test on a sandbox record before production campaigns.

When to use Omni HTTP instead

Use the custom connect when Salesforce users and flows own the send.

Use Omni HTTP when your backend owns the request:

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