# PagerDuty

This guide outlines the PagerDuty connector type.

## Connector paths

The PagerDuty connector has two paths:

- **Service key**: sends alerts and Cases one way to a single PagerDuty service, using a service integration key. This is the original PagerDuty connector and does not change.
- **Bi-directional**: keeps Cases and PagerDuty incidents in sync in both directions, using an account-level PagerDuty integration. It applies to Cases only and is opt-in. See the [PagerDuty Bi-directional integration](https://coralogix.com/docs/integrations/pull/pagerduty/).

## Connector configuration

A connector is a specific integration instance within a destination type that links Coralogix to a third-party vendor. The connector configuration defines how the connector communicates with its destination type and varies by destination type. See the [PagerDuty connector configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/pagerduty/connector-config/index.md) for details.

## Message configuration

Each destination type has a notification schema structure per output type. Schemas define the structure of the message sent to the destination type. Presets expose this message configuration in a reusable format. See the [PagerDuty message configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/pagerduty/schema-structure/index.md) for details.

## Next steps

[PagerDuty connector config](https://coralogix.com/docs/user-guides/notification-center/destination-types/pagerduty/connector-config/) [PagerDuty message config](https://coralogix.com/docs/user-guides/notification-center/destination-types/pagerduty/schema-structure/) [Route alerts to PagerDuty](https://coralogix.com/docs/user-guides/notification-center/user-scenarios/alerts-to-pagerduty/)