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

# Supported Platforms

- [Klaviyo](https://docs.heypoplar.com/integrations/supported-platforms/klaviyo.md): Add Direct Mail as a step in your marketing Flows or push your Lists & Segments for use in a One Time Send (see the Poplar App page).
- [Poplar App (Lists & Segments)](https://docs.heypoplar.com/integrations/supported-platforms/klaviyo/poplar-app-lists-and-segments.md): Our brand-new Klaviyo app will provide direct access to your Lists & Segments, allowing you to now  execute One Time Sends with external audiences.
- [Shopify](https://docs.heypoplar.com/integrations/supported-platforms/shopify.md): Install Poplar's Shopify App to configure Playbook triggers, push lists for One Time Sends, and share transactional data for real-time reporting.
- [Batch Mailings](https://docs.heypoplar.com/integrations/supported-platforms/shopify/batch-mailings.md): Send mailings to a list of recipients all at once, versus triggered via Playbooks.
- [Salesforce Marketing Cloud](https://docs.heypoplar.com/integrations/supported-platforms/salesforce-marketing-cloud.md)
- [Data Extension Setup](https://docs.heypoplar.com/integrations/supported-platforms/salesforce-marketing-cloud/data-extension-setup.md)
- [Iterable](https://docs.heypoplar.com/integrations/supported-platforms/iterable.md): Send personalized Direct Mail just like you would with emails or SMS - triggered by customer behavior and automated through journey logic.
- [Customer.io](https://docs.heypoplar.com/integrations/supported-platforms/customer.io.md): Configure a webhook trigger within a Customer.io campaign.
- [Emarsys](https://docs.heypoplar.com/integrations/supported-platforms/emarsys.md): Poplar's Emarsys integration allows you to create a webhook set up in your automations.
- [Simon Data](https://docs.heypoplar.com/integrations/supported-platforms/simon-data.md)
- [Segment](https://docs.heypoplar.com/integrations/supported-platforms/segment.md)
- [Optimizely](https://docs.heypoplar.com/integrations/supported-platforms/optimizely.md)
- [Cordial](https://docs.heypoplar.com/integrations/supported-platforms/cordial.md)
- [Sailthru](https://docs.heypoplar.com/integrations/supported-platforms/sailthru.md)
- [Braze](https://docs.heypoplar.com/integrations/supported-platforms/braze.md)
- [Blueshift](https://docs.heypoplar.com/integrations/supported-platforms/blueshift.md)
- [Marketo](https://docs.heypoplar.com/integrations/supported-platforms/marketo.md)
- [Hightouch](https://docs.heypoplar.com/integrations/supported-platforms/hightouch.md)
- [Zapier](https://docs.heypoplar.com/integrations/supported-platforms/zapier.md): Connect your Marketing Automation/CRM platform to Poplar via Zapie


---

# 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.heypoplar.com/integrations/supported-platforms.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.