Integrations
Works With the Tools Behind Your Infrastructure.
StackHeal is the layer between the systems that generate operational work and the systems that do it. 30 integrations across 6 categories, 16 of them maintained native connectors — and every status labelled honestly.
Connected systems
Service desk
Virtualization and cloud
Monitoring
Automation
Before you browse
What the status labels mean
We would rather be specific than imply that every product named here has a working native connector.
- Native connector
- A maintained StackHeal connector with configuration, authentication and action mapping built in.
- Beta connector
- A connector in active development and available to design-partner customers. Scope may change.
- Via API or webhook
- No native connector. The system is integrated through its REST API, webhooks or CLI using StackHeal's generic HTTP and script actions.
- Planned
- On the connector roadmap. Not available today — tell us if you need it and we will tell you where it sits.
Directory
Browse integrations
Search by system or by capability — try “restore”, “provision” or “alert”.
30 of 30 integrations
Ticketing and service management
Where requests arrive and where outcomes need to be written back.
WHMCS
Native connectorRead tickets and account context, and write replies, notes and status back.
- Ticket intake
- Account and service lookup
- Reply and status updates
Jira Service Management
Native connectorTrigger workflows from issue events and record outcomes on the issue.
- Request intake
- Transition on resolution
- Comment with findings
Zendesk
Beta connectorTicket intake, tagging and reply drafting for support teams.
- Ticket intake
- Tagging by intent
- Draft replies
Freshdesk
PlannedTicket intake and outcome write-back.
- Ticket intake
- Reply updates
ServiceNow
PlannedIncident and request intake with change-record binding for enterprise ITSM.
- Request intake
- Change record binding
- Evidence write-back
Email and inbound webhook intake
Native connectorAccept requests from any system that can send an email or post a webhook.
- Generic intake
- Structured payload parsing
Virtualization and cloud platforms
The platforms that actually run the workloads.
Proxmox VE
Native connectorProvision, resize, snapshot and query guests through the Proxmox API.
- VM lifecycle
- Snapshots
- Host and guest state queries
VMware vSphere
Native connectorProvision from templates, manage lifecycle and read cluster capacity.
- VM lifecycle
- Template deployment
- Capacity queries
KVM / libvirt
Beta connectorDirect guest lifecycle management on libvirt hosts.
- VM lifecycle
- Host state queries
Microsoft Hyper-V
PlannedGuest lifecycle and host queries via WinRM and PowerShell.
- VM lifecycle
- Host state queries
OpenStack
Beta connectorCompute, network and volume operations through OpenStack APIs.
- Instance lifecycle
- Network and volume operations
- Quota checks
Public cloud compute APIs
Via API or webhookInstance lifecycle on major public clouds through their own REST APIs.
- Instance lifecycle
- Tagging and inventory sync
Monitoring and alerting
The signals that start an investigation.
Zabbix
Native connectorReceive triggers and query item history for investigation context.
- Alert intake
- Metric history
- Maintenance window awareness
Prometheus Alertmanager
Native connectorReceive alerts by webhook and query metrics for context.
- Alert intake
- PromQL context queries
- Silence coordination
Grafana Alerting
Beta connectorAlert intake from Grafana's unified alerting.
- Alert intake
- Dashboard links on incidents
Nagios-family checks
Via API or webhookNagios, Icinga and compatible systems via event handlers and webhooks.
- Alert intake
- Check result queries
Uptime and synthetic checks
Via API or webhookExternal availability checks that can post a webhook on state change.
- Independent symptom confirmation
- Alert intake
Backup and storage
Systems that hold recovery points and archive data.
Proxmox Backup Server
Native connectorTrigger jobs, read outcomes and run verification restores.
- Job scheduling
- Outcome collection
- Restore workflows
Veeam
Beta connectorJob orchestration and outcome reconciliation via the Veeam API.
- Job scheduling
- Outcome collection
- Restore point listing
Restic and Borg
Native connectorRepository operations executed through managed script actions.
- Job execution
- Integrity checks
- Restore workflows
S3-compatible object storage
Native connectorVerify object presence, lifecycle state and retention on backup targets.
- Target verification
- Retention auditing
Database-native dumps
Via API or webhookPostgreSQL, MySQL and MongoDB dump and restore through managed script actions.
- Logical backup
- Restore verification
Automation and scripting
How workflow steps are executed on target systems.
Ansible
Native connectorRun your existing playbooks and roles as workflow steps, with output captured.
- Configuration tasks
- Remediation playbooks
- Post-build roles
Shell and PowerShell
Native connectorRegistered scripts executed over a managed transport, never ad-hoc shell access.
- Diagnostics
- Remediation
- Checks and assertions
Terraform
PlannedPlan and apply managed configurations as part of a provisioning workflow.
- Infrastructure as code execution
- Plan review as an approval step
Redfish and IPMI
Beta connectorOut-of-band hardware operations for server and facility work.
- Power operations
- Firmware campaigns
- Hardware health
APIs and webhooks
The generic path for anything without a dedicated connector.
StackHeal REST API
Native connectorTrigger workflows, read run history and manage definitions programmatically.
- Workflow triggering
- Run status polling
- Definition management
Outbound webhooks
Native connectorNotify your systems on run events — started, approved, failed, verified.
- Event notification
- Chaining external systems
Generic HTTP action
Native connectorCall any authenticated HTTP endpoint as a workflow step, with typed inputs and response mapping.
- Integrating systems without a connector
- Internal service calls
Chat notifications
Native connectorPost run updates and approval requests into Slack or Microsoft Teams channels.
- Approval requests
- Run notifications
No connector needed
Anything with an API can participate.
The generic HTTP action is a first-class path, not a fallback. You register a specific operation — method, URL template, headers, body shape, input schema and response mapping — and workflows call it like any other action.
Registered, not arbitrary
You register the operation, not a general-purpose HTTP client. The workflow supplies only the declared inputs.
Validated inputs
Input types and patterns are checked before the request is made — which matters most when a value came from untrusted text.
Mapped responses
Only mapped response fields become workflow data, so an upstream API change cannot silently alter behaviour.
Outbound webhooks
Your systems can subscribe to run events — started, approved, failed, verified — and react to them.
Implementation status
Integration questions
Something not covered here? Ask our team.
Need a system we have not listed?
Tell us what it is and how you would want it used in a workflow. We will tell you whether it needs a connector or whether its API is enough — and roughly what that takes.