# Connectors explained

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Fnotification-center%2Fintroduction%2Fconnectors-explained.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Fnotification-center%2Fintroduction%2Fconnectors-explained.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

Notification Center creates outbound push notifications based on a connector configuration that connects to a particular third-party vendor or destination type. Examples include `slack-workspace-1`, `jane@company.com`, or `My_PagerDuty`.

[![Available connector destination types in Notification Center](/docs/assets/images/connectors-type-fbbfc8e376a36ffccf3c15cf260d3588.webp)](https://coralogix.com/docs/docs/assets/images/connectors-type-fbbfc8e376a36ffccf3c15cf260d3588.webp)

As part of the connector configuration, notifications can be sent to multiple connectors within the same destination type or across different destination types.

A connector configuration is a set of fields specifying a third-party vendor’s connection details, including authentication. Each destination type has different fields that need to be configured.

[![Configuration page for a connector destination type](/docs/assets/images/connector-config-new-ade77b80fa6615c26bafadd89538c1fe.webp)](https://coralogix.com/docs/docs/assets/images/connector-config-new-ade77b80fa6615c26bafadd89538c1fe.webp)

## Next steps[​](#next-steps "Direct link to Next steps")

[Connectors overview](https://coralogix.com/docs/docs/user-guides/notification-center/connectors/.md)[Destination types](https://coralogix.com/docs/docs/user-guides/notification-center/destination-types/introduction/.md)[Quick start](https://coralogix.com/docs/docs/user-guides/notification-center/quick-start/.md)