Onboard your PagerDuty account so AiStrike can manage incidents as cases and page your on-call responders.◼︎
1. Prerequisites
-
Administrator or Account Owner access to PagerDuty, with permission to manage API Access Keys.
-
The login email address of a PagerDuty user that AiStrike will act as.
-
Manager role or above, only if you choose to add an Events API integration manually (Step 4).
2. Create a REST API key
The REST API key lets AiStrike read and manage incidents, notes, alerts, services and users.
-
Log in to PagerDuty as an administrator.
-
Go to Integrations > Developer Tools > API Access Keys.
-
Click Create New API Key.
-
Enter a Description to identify the key later (e.g.
aistrike-connector). -
Leave Read-only unchecked. AiStrike needs write access to acknowledge, resolve and annotate incidents.
-
Click Create Key.
-
Copy the key shown and store it securely — it is displayed only once and cannot be retrieved again.
The key is a 20-character string. If the value you copied is 32 characters, it is an Events API integration key and will not work here.
3. Choose the From user
PagerDuty attributes every action taken through the API to a specific user. AiStrike sends this address on each request, and the user's name appears in the incident timeline against acknowledgements, resolutions and notes.
-
Go to People > Users and pick the user AiStrike should act as. A dedicated automation user is recommended.
-
Copy that user's login email address.
This field is required. Without it PagerDuty accepts read operations but rejects acknowledging, resolving and adding notes to incidents, so the connector will appear to connect successfully and then fail when a playbook runs.
4. Events API integration (optional)
To page an on-call responder, AiStrike sends an event to a PagerDuty service. The event then follows that service's own event rules, escalation policy and on-call schedule, so your existing routing decides who is notified.
No action is needed here in most cases. AiStrike discovers each service's Events API key automatically using the REST API key from Step 2, so services you add later work without any configuration change.
Complete this step only if your REST API key cannot read services, or if a service has no Events API V2 integration yet:
-
Go to Services > Service Directory and select your service.
-
Open the Integrations tab.
-
Click Add integration.
-
Select Events API V2, then click Add.
-
Copy the Integration Key shown (32 characters).
5. Connector configuration
|
Field |
Description |
|---|---|
|
REST API Key |
The 20-character key created in Step 2 |
|
From Email |
Login email of the PagerDuty user AiStrike acts as, from Step 3 |
|
Events API Routing Key |
Optional. Only required if AiStrike should not discover routing keys automatically |
|
Default Service ID |
Optional. Service used when a playbook does not specify one, e.g. P7GFCPL |
Use one connector configuration per PagerDuty account. Multiple services within the same account are selected inside each playbook action, so they do not need separate configurations.
6. Verify the connection
Use Test Connection in the AiStrike connector screen. This performs a read-only incident lookup and confirms the REST API key is valid.
Because the test is read-only, it does not validate the From Email. To confirm write access, run a playbook action such as Add Note against an existing incident and check that the note appears in the PagerDuty incident timeline attributed to your chosen user.
7. What AiStrike can do
Once connected, playbooks can:
-
Page an on-call responder for a detection, honouring your escalation policies and schedules.
-
Fetch and search incidents by status, urgency, service, assignee and time range.
-
Work incidents as cases — acknowledge, resolve, re-prioritise, reassign, snooze and merge duplicates.
-
Add investigation notes and enrichment findings to the incident timeline.
-
Read incident context including grouped alerts, notes and the full incident timeline.
-
Record remediation actions as change events on a service.
For help with setup, reach out to the AiStrike support team.