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

# Destinations catalog

Find here the list of all plug\&play [destinations](/getting-started/concepts.md#destination).

Destinations are sorted per categories (Advertising, Emailing, Analytics, Push notifications...).

The destination's catalog homepage show an overview of 3 destinations per categories, click on the categories menu or on 'View all' to display the full destinations list.\
\
You didn't find the destination you were looking for? Do not hesitate to fill the **request form** to ask our team to add a new destination on the list, or use the [Destination Builder](/features/destinations/destination-builder.md)

Newly added destinations are summarized on the ***New*** tab.

**Flags meanings**:

* "New": the destination was just released
* "Closed alpha": the destination is not open publicly, the backend is still in QA on our side (Commanders Act tests) and/or the partner.
* "Beta" : the destination is usable by everybody, but it has to be validated with one ore more first (beta) customers

You need more information about a destination? Simply click on it, and you will have access to all details and requested settings for this destination.


---

# 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://doc.commandersact.com/features/destinations/destinations-catalog.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.