Track the incident’s next steps
Create issues from selected service incidents with their original incident context.
PagerDuty + Velocity
Reliability
Connect incident response with the work that follows.
Route PagerDuty incidents into Velocity, keep service ownership clear and coordinate incident and issue status.
Illustrative workflow
- 1
Map your services
Connect PagerDuty and choose the team and status behavior for each service.
- 2
Receive an incident
A supported incident callback creates or updates the linked issue.
- 3
Coordinate the response
Review the incident link and on-call context while tracking follow-up work.
What your team gets
Keep status connected
Configure supported status mappings in both directions rather than updating each tool independently.
See response context
Use the configured on-call and service information to understand who is handling the incident.
Make it work for your workspace
A workspace admin connects PagerDuty credentials, configures a verified service webhook and chooses service/status mappings. Optional outbound incident actions require appropriate PagerDuty access.
Choose the workspace and follow its integration setup. Your existing issue ownership, priorities and workspace permissions stay part of the workflow.
Questions, answered
Does every PagerDuty incident have to use the same team?
No. Service mappings let you route configured incident work to the team responsible for that service.
Bring PagerDuty into your Velocity workflow.
Connect the tools your team uses to the work your team tracks.