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

# Platform Integrations

Provides a list of all the integrations available natively through the Pushly platform

The Pushly Platform integrates with a wide range of external systems to enhance your campaigns, allowing you to leverage data from various sources to create highly personalized and automated notifications.  Some of our integrations are listed below:

#### Communication & Messengers

* Slack: The Pushly platform integrates with Slack to enable a seamless flow of information and updates. You can set up new connections to send notifications directly to specific teams and channels, such as a "Pushly" team channel or a private channel for a specific user. This is a one-time setup that allows you to configure which channel receives which notifications or alerts from the Pushly platform.

#### Content Management Systems

* WordPress: The Pushly WordPress plugin allows you to manage push notifications directly from your WordPress dashboard. This integration streamlines content workflows, enabling publishers to send notifications for new posts without leaving their CMS. The screenshot shows the integration is "Enabled," indicating an active connection for easy content distribution.

#### Data Platforms

* BlueConic: As a Customer Data Platform (CDP), BlueConic integrates with Pushly to provide a robust data source for creating personalized notifications. The integration allows you to leverage unified user profiles and segments from BlueConic to power highly targeted Recommended Notifications within the Pushly platform. The screenshot indicates a connected instance of "BlueConic Recommendations" which can be edited or removed.


---

# 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://documentation.pushly.com/platform/platform-integrations.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.
