The Integrations area covers how eltPulse connects to external systems on your behalf. For how Connections relate to pipelines, monitors, and gateways, see Concepts.
In the standard product, customers do not sign in to GitHub. eltPulse provisions repositories under your GitHub organization using a GitHub App or machine user. Service credentials live only on the server.
For enterprise or testing, operators can enable CUSTOMER_GITHUB_OAUTH_ENABLED=true so users may connect their own GitHub account. Tokens are encrypted at rest. This path is off by default.
You use ServicePulse by opening that site directly; eltPulse does not host or proxy it. The in-app Integrations page includes a shortcut to the same URL. An optional “with context” link passes your deployment’s public base as eltpulse_origin for future cross-product setup (no credentials). Pipeline run webhooks may include source: "eltpulse" so a receiver like ServicePulse can identify the emitter. Set NEXT_PUBLIC_SERVICEPULSE_URL if ServicePulse is not at the default host.
Slack, warehouse SSO, and notification channels will appear here as the product matures — similar to how ServicePulse documents integrations by surface area.