Skip to content
TeamLoop

PagerDuty Integration

Connect PagerDuty to search incidents, track response timelines, and capture on-call activity across your services.

What You Can Query

Section titled “What You Can Query”
Content TypeDescription
IncidentsAlerts with status, urgency, service context
Log EntriesFull incident timeline (trigger, ack, resolve)
AssignmentsOn-call responder history
EscalationsEscalation level changes
NotesIncident annotations and updates

Connecting PagerDuty

Section titled “Connecting PagerDuty”
  1. Log into TeamLoop at app.teamloop.io
  2. Navigate to Settings > Integrations
  3. Click Connect next to PagerDuty
  4. Enter your PagerDuty API v2 key
  5. TeamLoop validates the key and saves it encrypted

Creating a PagerDuty API Key

Section titled “Creating a PagerDuty API Key”
  1. Log into PagerDuty
  2. Go to Integrations > API Access Keys
  3. Click Create New API Key
  4. Give it a description (e.g., “TeamLoop”)
  5. Choose Read-only API Key for security
  6. Copy the key and paste it into TeamLoop

Your API key provides read access to incidents and services your PagerDuty account can access. We never write to your PagerDuty account.

Example Queries

Section titled “Example Queries”

Search Incidents

Section titled “Search Incidents”
teamloop_query:
  query: "database outage"
  sources: "pagerduty"

Find Service Incidents

Section titled “Find Service Incidents”
teamloop_query:
  query: "payment service critical"
  sources: "pagerduty"

Track On-Call Activity

Section titled “Track On-Call Activity”
teamloop_query:
  query: "after-hours incidents"
  sources: "pagerduty"

Automatic Change Tracking

Section titled “Automatic Change Tracking”

TeamLoop automatically tracks changes from PagerDuty via the log entries API.

Incident Timeline

Section titled “Incident Timeline”

When you query an incident, TeamLoop fetches its full log entry history:

  • Trigger events (with channel details)
  • Acknowledgment events
  • Resolution events
  • Escalation level changes
  • Reassignment events
  • Annotation/note additions

This timeline makes PagerDuty especially powerful for post-incident reviews and temporal queries.

Entity Extraction

Section titled “Entity Extraction”

PagerDuty content maps to TeamLoop entity types:

PagerDuty ContentTeamLoop Entity
IncidentDOCUMENT
Log entryCHANGE
AssigneePERSON
ServiceCOMPONENT
Status changeCHANGE
EscalationCHANGE

Temporal Queries with PagerDuty

Section titled “Temporal Queries with PagerDuty”

Point-in-Time

Section titled “Point-in-Time”

See the state of incidents on a specific date:

teamloop_query:
  query: "production incidents"
  sources: "pagerduty"
  mode: "as_of"
  as_of: "2024-06-01"

Evolution

Section titled “Evolution”

Track how incident patterns evolved over a quarter:

teamloop_evolution:
  query: "API service incidents"
  from_date: "2024-01-01"
  to_date: "2024-03-31"

Troubleshooting

Section titled “Troubleshooting”

No Results

Section titled “No Results”
  • Verify the PagerDuty integration is connected
  • Check that your API key is valid
  • Try broader search terms
  • PagerDuty search matches on incident titles

Missing Incidents

Section titled “Missing Incidents”
  • Check that your PagerDuty account has access to the relevant services
  • Ensure your API key has not been revoked
  • Incidents from restricted teams may not be accessible

Security

Section titled “Security”
  • API keys are encrypted at rest using pgcrypto
  • Keys can be revoked from PagerDuty API Access Keys settings
  • TeamLoop only reads, never writes
  • You can disconnect at any time from TeamLoop settings
  • Connected keys show a hint so you can identify which key is in use

Next Steps

Section titled “Next Steps”