Integration Pack for Network Messaging
Connect Microsoft System Center Orchestrator to the applications, tools and data streams your organisation depends on with Kelverion.
Network Messaging is a practical integration approach for exchanging structured or textual data between systems over common network protocols. In an automation environment, it allows applications, monitoring tools, service desk platforms, CMDBs, scripts and custom solutions to send or receive information through HTTP, HTTPS or TCP connections, so that events, requests and operational data can trigger automated action.
For System Center Orchestrator customers, this means Network Messaging can act as a flexible bridge between Orchestrator runbooks and systems that do not have a dedicated integration pack, formal API connector or modern service interface. Instead of relying on manual copy-and-paste, email handoffs or custom point-to-point scripts, teams can use network messages to trigger, transform and route automation data reliably.
Typical Automation Scenarios
- Custom Application to Service Desk Automation
Receive a message from a bespoke business application and create or update a service desk process through an Orchestrator runbook - Monitoring Event Intake
Listen for HTTP or TCP messages from monitoring tools and route them into diagnostic, remediation or escalation runbooks - CMDB and Asset Data Updates
Transform incoming message data and pass it to configuration management or asset systems as part of a controlled workflow - Legacy System Integration
Bring older platforms into automation without building a dedicated connector for every application - Operational Notifications and Handoffs
Send textual data from Orchestrator to systems that can consume HTTP or TCP streams - Runbook-Driven Message Forwarding
Receive, validate, enrich and forward data between systems while applying Orchestrator logic and governance
Benefits at a Glance
- Extend Automation Coverage
Connect Orchestrator to legacy systems, custom applications and specialist platforms that are not covered by standard integration packs - Reduce Manual Data Transfer
Replace manual rekeying, file movement and email-based handoffs with automated HTTP, HTTPS and TCP message exchange - Improve Service Desk Processing
Include bespoke or legacy applications in service workflows, helping improve consistency, response times and data quality - Trigger Runbooks From External Systems
Listen for inbound HTTP or TCP requests and use received data to initiate Orchestrator automation - Transform and Route Operational Data
Receive message data, process it in a runbook and forward it to platforms such as event management systems, CMDBs and service desks - Standardise Integrations
Use reusable Orchestrator activities instead of creating and maintaining one-off scripts for every messaging requirement - Support Hybrid and Operational Automation
Bridge modern, legacy and custom systems while keeping Orchestrator at the centre of IT process automation
Key Capabilities
- Listen for and respond to HTTP requests from external systems and custom applications
- Listen and respond to incoming TCP requests that can trigger or feed Orchestrator runbooks
- Send textual data to an HTTP server using specified input properties and formats
- Send textual data to a specified server using TCP
- Build repeatable runbook steps without relying on bespoke scripts for every message exchange
- Use Orchestrator runbook logic to transform received data and forward it to operational systems
Integration Activities
| Activity Name | Description |
|---|---|
| Monitor-HTTP | Listen for and respond to HTTP requests from external systems and custom applications |
| Monitor-TCP | Listen to and respond to incoming TCP requests |
| Send-HTTP | Send textual data to an HTTP server using customised input properties and formatting |
| Send-TCP | Send textual data to a specified server |