Platform · Integrations
Fits the tools your team already runs.
SchemaPulse consolidates database operations. It does not ask you to abandon the incident tracker, paging tool and chat platform the rest of your engineering org already lives in.
What connects
Jira — a persistent two-way link
Not a message and forget. The incident holds the issue key, and on every view SchemaPulse reads back the issue's status, assignee and full comment thread from Jira. Comments and status changes made in SchemaPulse are pushed the other way, attributed. A recurrence can reopen the original issue rather than starting an unrelated one.
PagerDuty
Incidents raise and resolve PagerDuty alerts. Acknowledgement flows back, so an incident acknowledged on a phone is acknowledged in SchemaPulse.
Slack and Microsoft Teams
Incidents and alerts posted to the channel that owns the service, with the acknowledge and resolve actions available from the message.
Webhooks
A signed HTTP callback for anything not covered above — your own runbook automation, a status page, an internal on-call system.
Notification channels with test-send, and tokenised acknowledge and resolve links that work without a login.
Scoped per project
Routing follows the organisation and project scoping, so a shared platform does not page the wrong team.
Detail
Channels
- Jira
- Create from an incident; status, assignee and comments read back on view; comments and status pushed the other way with attribution; reopen on recurrence; deep link both ways
- Paging
- PagerDuty — raise, resolve, and acknowledgement flowing back
- Chat
- Slack · Microsoft Teams — channel routing with actions on the message
- Generic
- Webhook — signed HTTP callback for your own automation
- Notification channels with test-send and tokenised action links
Related