# Connector configuration

## Configuration

| UI label                | API field name          | Type     | Required | Allows notification source type overrides | Description                                                                                                                                                                                                                   |
| ----------------------- | ----------------------- | -------- | -------- | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Service key**         | `integrationKey`        | `String` | true     | true                                      | Also known as an [Integration Key](https://support.pagerduty.com/main/docs/services-and-integrations#generate-a-new-integration-key), this unique identifier allows notifications to be sent to a specific PagerDuty service. |
| **Dynamic service key** | `dynamicintegrationKey` | `String` | false    | true                                      | Specify a dynamic, data-driven value for the service key using alert metadata. Useful if you need to route alerts to different PagerDuty services based on different conditions.                                              |

## Templating for dynamic routing

The **Service key** field supports [dynamic templating](https://coralogix.com/docs/user-guides/notification-center/dynamic-templating/index.md), enabling dynamic routing by inserting variables into the notification configuration. This allows events to be sent to different services within PagerDuty based on their attributes.

Here is an example **Dynamic service key** configuration:

```js
{% if alert.groups['team_name'] == 'alpha'%}
  930aaaaaaaaaaaaaaaaaaaaaaaaaa0d1
{% elif alert.groups['team_name'] == 'beta' %}
  930bbbbbbbbbbbbbbbbbbbbbbbbbb0d1
{% else %}
  930xxxxxxxxxxxxxxxxxxxxxxxxxx0d1
{% endif %}
```

## Next steps

Define the payload structure for PagerDuty notifications in [Message configuration](https://coralogix.com/docs/user-guides/notification-center/destination-types/pagerduty/schema-structure/index.md).