The Integrations area and related app pages cover how eltPulse connects to external systems. For how Connections relate to pipelines, monitors, and gateways, see Concepts.
Managed GitHub (default) — in the standard product, customers do not sign in to GitHub directly. eltPulse provisions repositories under your organization using a GitHub App or machine user.
Bring your own GitHub — operators can enable CUSTOMER_GITHUB_OAUTH_ENABLED=true so users connect personal or org accounts. Tokens are encrypted at rest. Off by default.
Pipeline YAML auto-pushes on save when connected — see Repositories.
Webhooks support outgoing run notifications (global or per-pipeline) and incoming triggers via a workspace token. Full contract: Webhooks (docs).
Register MCP servers to extend Pulse AI with custom tools — HTTP or stdio transports, encrypted secrets, and a template catalog for common providers. Pulse AI invokes registered tools during AI-assisted pipeline editing.
Create Bearer tokens under Account → Developers for automation — same REST endpoints as the browser session (pipelines, runs, connections, webhooks). Audit log entries record key usage where enabled.
ServicePulse is a separate product for service health and incident response. eltPulse includes a shortcut on Integrations; optional eltpulse_origin query param passes your deployment base URL for cross-product setup. Run webhooks may include source: "eltpulse" for receiver filtering. Set NEXT_PUBLIC_SERVICEPULSE_URL if ServicePulse is not at the default host.
Billing uses Stripe (Team/Pro plans); authentication uses Clerk. Webhook endpoints for those providers are server-side only — not user-configurable.