Overview
Configure Infobip as a PulseGate provider connection for SMS, WhatsApp, voice, provider webhooks, delivery state, template operations, telemetry, and cost-aware routing.
Capabilities
-
SMS, WhatsApp, and voice provider operations
-
Provider webhook signature verification and normalized event ingestion
-
Delivery, inbound-message, template-status, and provider-state processing
-
Sender identity, provider cost rule, health, telemetry, and balance models
-
Provider error normalization for retry and operational workflows
Setup Steps (5)
-
1
-
2
Step 2
Store provider credentials through the application secret flow and configure connection settings.
-
3
Step 3
Configure sender identities, routing destinations, cost rules, and template mappings as required.
-
4
-
5
Step 5
Verify provider state, delivery receipts, inbound events, and message status in PulseGate.
Limitations
FAQs
Which PulseGate workflows use the Infobip connection?
Provider routing can use the connection for configured SMS, WhatsApp, and voice delivery, while provider webhooks update delivery, inbound-message, template, and provider state.
Where are provider credentials handled?
PulseGate uses protected application secret storage for application-owned credentials and keeps provider configuration and references in its provider-connection model.
Pricing
Starter
USD 219.07 / annual
Team
USD 730.42 / annual
Enterprise
USD 1,826.15 / annual