Coordinate responders on incidents
Connect
SPIRITT
PagerDutyPagerDuty
Run the response
SPIRITT builds and operates the work around PagerDuty incidents, from response plays and coverage changes to status updates and reliability fixes. Keep responders, stakeholders, and follow-up work connected.
What you can do with PagerDuty.
Response in motion
Launch incident workflows and response plays with the right incident context, then carry coordination into your team's connected tools.
Coverage that holds
Turn agreed rotations and absences into on-call schedules, temporary overrides, and handoff notifications with explicit boundaries.
Evidence into action
Use incident analytics, alerts, and related change events to prioritize reliability work and carry verified lessons into postmortems.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for incident response, on-call operations, or the reliability work you want owned end to end.
02
Connect PagerDuty
Connect PagerDuty with access to the incidents, services, schedules, and workflow actions your mission needs.
03
Delegate an outcome
Hand over a response procedure, coverage plan, or reliability goal. SPIRITT builds the system and runs the work across connected tools.
Hand over a mission.
Choose a mission. Make it yours.
Put PagerDuty to work.
Put your response plan to work
Questions
PagerDuty, with SPIRITT.
01What can SPIRITT do directly in PagerDuty?+
SPIRITT can create incidents, services, escalation policies, schedules, overrides, maintenance windows, and incident workflows. It can also execute response plays, retrieve alerts and incident analytics, and create or update status page posts and postmortems. The mission uses the actions available to your connected account.
02What access does the connection need?+
PagerDuty supports connecting through OAuth or an API key. Required access depends on the mission: incident analysis needs access to incident data, while schedule overrides, workflow creation, and public status posts need corresponding write access. Your account permissions and available PagerDuty features determine which operations can run.
03Can SPIRITT manage on-call coverage and planned maintenance?+
Yes. It can create layered on-call schedules, temporary schedule overrides, user handoff notification rules, and service-specific maintenance windows. Give it the agreed responders, schedule or service identifiers, timezones, and exact boundaries so coverage changes and maintenance periods match the intended scope.
04How can it connect incident response to Slack and Jira?+
PagerDuty webhook subscriptions can supply incident event notifications. SPIRITT can retrieve incident alerts and response context, coordinate in connected Slack channels, and create Jira follow-up work from confirmed findings. A linked record keeps response activity and engineering actions traceable to the originating incident.
05What custom systems can it build around PagerDuty?+
Useful builds include an incident intake app that creates assigned incidents, a reliability dashboard backed by aggregated incident metrics, and a maintenance coordination system that creates scoped windows. PagerDuty remains the incident management system while the custom app supplies the intake, views, and cross-tool coordination your team needs.
06How is this different from a PagerDuty Incident Workflow?+
An Incident Workflow defines response steps inside PagerDuty. SPIRITT can create workflows, configure their triggers, and start workflow instances, while also building software around them and carrying work into other tools. That extends the mission into coverage planning, stakeholder communications, investigation, and tracked reliability improvements.