> For the complete documentation index, see [llms.txt](https://docs.halosecurity.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.halosecurity.com/docs/integrations/workflow-integrations/pagerduty.md).

# PagerDuty

Receive events in PagerDuty

### Generate PagerDuty Integration Key

Start by generating an integration key from PagerDuty.

1. Log into you PagerDuty account
2. Select **Services → Service Directory** from the top navigation
3. Click **New Service** and add the service details
   1. Service Name: **Halo Security**
   2. Integration Type: **Events API v2**
4. Click **Create Service**
5. Copy the **Integration Key**

Learn more about [Services and Integration in PagerDuty](https://support.pagerduty.com/main/docs/services-and-integrations#generate-a-new-integration-key).

### Connect PagerDuty in Halo Security

* Log into Halo Security
* Visit your *Settings → Integrations →* [Add](https://app.halosecurity.com/user/settings/integrations/add)
* Add the PageDuty integration
* Name for your integration and enter the API key you generated from PagerDuty

### Create Profiles

After connecting PagerDuty, you can create profiles to control how alerts are created. To create a profile:

1. Navigate to the **Profiles** tab
2. Click the **+** icon
3. Enter a name for the profile
4. Configure your settings
5. Click **Save**

### Create Event Rules

To receive PagerDuty events, create Event Rules and add your PagerDuty profile as an action. Visit *Events →* [Event Rules](https://app.halosecurity.com/user/settings/event-rules/) to set up rules that determine which Halo Security events create events in PagerDuty.

Learn more about configuring Event Rules at:

{% content-ref url="/pages/QVrCXwRcuy8YWA5L25VR" %}
[Event Rules](/docs/platform/events/alerts.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.halosecurity.com/docs/integrations/workflow-integrations/pagerduty.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.