Connector framework
Genesys Cloud real-time connectors
70+ real-time connector targets for Streamvane: messaging brokers, BI dashboards, data platforms, CRM, cloud events and observability — one Genesys KPI core.
The specialized middle, not generic plumbing
Enterprise contact centers never have one downstream system. They have WFM schedulers, Microsoft BI estates, AWS data lakes, CRM desktops, NOC dashboards and legacy buses — often at once. Streamvane lets you define KPI semantics once and enable an egress package per destination, following the same architecture already proven with Power BI, REST, HTTP feeds and RabbitMQ.
Every connector ships as a Global.Platform.* package on a shared core — not a rewrite per sink. The same 1,200+ structural KPIs (plus any client-specific metric you define) reach every streaming destination in under a second, whether Streamvane runs as a managed PaaS bridge or embedded in your own cloud on Azure, AWS or GCP.
In platform codebase; deployable today.
Implemented + enterprise deployment pattern.
Platform-package recipe defined; scoped delivery.
Valid industrial standard; built when you need it.
Browse by architecture
Twelve categories, one Reactive Engine
Pick the destinations your architecture already runs on and stream Genesys KPIs in real time to each. The KPI definition stays identical; only transport, serialization and authentication change per connector.
Messaging brokers & event streaming
Event-driven analytics mesh, real-time fan-out to microservices, multi-region streaming.
Analytics, BI & dashboards
Supervisor and exec dashboards, NOC-style ops views, Microsoft-centric BI programs.
Data platforms & warehouses
Enterprise reporting, ML feature stores, historical interval analytics, lakehouse.
CRM, CX & ITSM
Agent desktop context, case correlation, supervisor alerts, ITSM incident triggers.
Cloud-native event buses
Trigger Azure Functions, Step Functions and serverless workflows from KPI events.
File, batch & object storage
Partner batch contracts, data-lake landing, regulatory archive patterns.
Observability & APM
SRE monitoring of contact-center KPIs alongside infrastructure metrics.
WFM & workforce operations
Intraday actuals for staffing — often the first connector in telco and BPO programs.
Custom & on-request targets
Any valid industrial standard, built when you need it — collaboration, ITSM and niche transports on the same core.
Deployable today
Implemented core egress paths
Which connector should you start with?
Most programs begin with one destination tied to an urgent business need, then expand across the same engine. Match your primary outcome to the recommended first connector — the “often add” column shows where teams typically grow next once the KPI definitions are proven.
| Primary need | Start with | Often add | Why start here |
|---|---|---|---|
| Microsoft BI program | Power BI | Synapse, Fabric, Teams | Native streaming datasets put live KPIs in the estate leaders already open. |
| WFM / intraday actuals | HTTP feeds | REST for validation | Schema-controlled contracts match the scheduler imports planners already trust. |
| Event-driven architecture | RabbitMQ or Kafka | Event Hubs, Event Grid | Durable, ordered fan-out drives microservices and serverless reactions in real time. |
| Enterprise warehouse | Snowflake or Synapse | Data Factory orchestration | Interval-grain history lands ready for governed reporting and ML features. |
| CRM-enriched agent experience | Salesforce | REST + Teams alerts | KPI context reaches the desktop where agents and supervisors actually act. |
| Ops / NOC visibility | Grafana or Kibana | Prometheus, Datadog | Contact-center KPIs sit beside infrastructure metrics on one operations wall. |
| Real-time executive dashboards | Power BI or Grafana | Kibana, Fabric | We ship the visualization layer, so leaders watch sub-second KPIs from day one. |
| Multi-cloud / embedded delivery | Event Hubs or EventBridge | Kafka, Pub/Sub | Cloud-native buses keep the engine portable across Azure, AWS and GCP. |
Same semantics, every connector
Whether KPIs flow to Kafka, Power BI or an operational HTTP feed, the definition of queue depth, agent state, skill performance and routing interval never changes. The Reactive Engine enforces consistency — connectors change only transport, serialization and auth. And when you need the visuals, the same KPIs render in the real-time Power BI, Grafana and Kibana dashboards we ship as a visualization layer.
Genesys Cloud → Ingress → Reactive Engine → Metrics store
│
┌─────────────────────┼─────────────────────┐
Power BI Kafka HTTP feed
Grafana Salesforce Event Grid
Snowflake RabbitMQ SFTPMap your Genesys topics to the right connectors
Book a connector assessment and we'll match your KPI families to destinations before recommending modules.
Streamvane by Tessovia · Azure · AWS · GCP · Your data, your keys