Integrations
Connecting a system
Credentials, connectivity and the difference between a native connector and an API integration.
Systems reach StackHeal in one of two ways. A native connector is a maintained integration with configuration, authentication and action mapping built in. Everything else is integrated through the generic HTTP action, webhooks or registered scripts — which is a fully supported path, not a workaround.
Credentials
Credentials are stored in the secret store and referenced by name. They are resolved by the execution runner at the moment of use. They do not appear in workflow definitions, in run history, or in any context passed to the interpretation layer.
Grant the narrowest credential that lets the actions you registered work. A monitoring connector that only supplies context needs read-only access; there is no reason for it to hold more.
Connectivity
Platform APIs do not need to be internet-reachable. Execution runners deployed inside your network initiate outbound connections to the control plane and reach your systems locally. Network requirements for each deployment model are covered under Deployment models.
Checking current connector status
The integration directory lists every system with its current status: native connector, beta connector, API-based, or planned. Status labels describe availability honestly — confirm with our team before building a plan around a connector marked beta or planned.
Scope of this documentation