One connector layer, so integration does not become a project.
Omni Connector holds the credentials, webhooks, and mapping for every external system the suite talks to – messaging providers, mailboxes, SIP trunks, and your own applications.
Integrations rot in the same way: credentials in three places, a webhook shape that changed, and nobody sure which system is authoritative. The connector layer centralises that – one configuration per external party, with a visible state.
For developers the useful part is the mapping: incoming payloads are mapped to internal fields through configuration, so a provider change is a settings edit, not a release.
- 1Configuration per external system
- MappedPayload fields mapped without code changes
- SignedSignature verification per connector
- VisibleDelivery attempts and failures in the connector state
Messaging and mail, configured once.
Each messaging provider, mailbox, or webchat site gets a connector with its own credentials, signature settings, and response mapping. Tokens rotate in one place, and the connector shows whether the last handshake succeeded.
- Credentials per provider with rotation
- Signature verification: no signature, shared secret, or key pair
- Response mapping for non-standard payloads
- Handshake and last-error state per connector
Your applications, without a bespoke project each time.
Outbound webhooks, API keys, and inbound endpoint mappings let the suite exchange events with your own systems: a resolved ticket to your data warehouse, a new contact to your ERP.
- Outbound webhooks with retry and delivery log
- API keys scoped per integration
- Inbound endpoints with payload mapping
- Event list documented per module
See the failure before the customer does.
Every delivery attempt is recorded with response code and body. When a provider changes behaviour, the connector state shows it, and the fix is a configuration edit with an audit entry.
- Delivery attempts with response detail
- Retry policy per connector
- Configuration changes recorded with actor
- Test action per connector before going live
What Omni Connector covers
Messaging providers
WhatsApp, Instagram, Messenger, Telegram.
IMAP poll and SMTP send per mailbox.
Telephony
SIP trunk and PBX node configuration.
Webhooks
Outbound with retry and delivery log.
API keys
Scoped per integration.
Mapping
Payload to field mapping by configuration.
Visibility
Connector state, last error, test action.
Questions from the integration side
Do we edit code to add a provider?
No, mapping and credentials are configuration; a genuinely new protocol is a driver addition.
Can we rotate tokens without downtime?
Yes, the connector accepts the new credential and reports the handshake state.
Are webhooks signed?
Outbound webhooks can carry a shared secret; inbound signatures are verified per connector.
Where are credentials stored?
In the platform configuration on your own server in the on-premise deployment.
See this app running on your own data.
We install the suite on your server or in our cloud, then walk your team through the exact flow you described.