WebEngage

Azmarq’s custom connect for WebEngage maps journeys and campaigns 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/webengage.

What the connector is

Use it when WebEngage journeys should send WhatsApp, SMS, or RCS from WebEngage, without your engineers posting Omni JSON.

Sibling custom connects: Salesforce, LeadSquad. HTTP CDP connectors with published Omni paths: CleverTap, MoEngage RCS.

Enable it

1. Ask Azmarq integrations to turn on the WebEngage connect for your account.
2. Connect the WebEngage project and the Azmarq dashboard.
3. Map the journey or campaign step that should send.
4. Test on a segment before production.

When to use Omni HTTP instead

Use the custom connect when WebEngage journeys own the send.

Use Omni HTTP when your backend owns the request:

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