Integrations
GreenSlope is designed to live alongside your existing stack, not replace it. The integrations below are the ones supported in V1; each page covers install, configuration, and the failure modes worth knowing about.
VercelOTel sink, deploy webhooks, and the deploy REST API for change-event ingestion.GitHubInstall the GreenSlope app to link commits to releases and surface PR context in alerts.SlackAlert delivery, acknowledgements, snooze, and slash commands — the full incident loop in Slack.EmailAlert delivery over email for backups and out-of-band recipients.TwilioSMS and voice escalation for sev-1 alerts when Slack isn't enough.Outbound webhooksGeneric webhook delivery for alerts and change events — wire up anything custom.
How integrations are scoped
We pick integrations based on the jobs-to-be-done the on-call engineer actually has, not on a checkbox-completeness goal. That means:
- Source-of-truth integrations (Vercel, GitHub) ingest data GreenSlope needs to do its job — release attribution would not work without them.
- Alert-routing integrations (Slack, Email, Twilio, Webhooks) deliver the loop. Slack is the primary surface; the others are escalation and fallback.
- What's deliberately not here: ticketing systems, chat-ops bots beyond Slack, and synthetic monitors. We add new categories on customer demand, not on competitive comparison.
If your stack needs something we don't have, email support@greenslope.io — we prioritise by real customer asks, not by what looks good on a feature matrix.