> For the complete documentation index, see [llms.txt](https://api-how-to.plannrcrm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-how-to.plannrcrm.com/addons/add-on-store.md).

# Add-On Store

There are two types of add-ons within Plannr's ecosystem; plannr-built add-ons and externally built. If you've built your own integration to Plannr, it's still possible to have an entry on our add-on store. 

### Key information required for a store entry

In order to shout about your integration within Plannr, we'll need the following information from you: 

* Name of your integration (max 255 chars)
* Headline banner image (1024 x 300 pixels)
* Description of what the add-on does (no limit on length, can include html)
* Instructions on how to set up the add-on (no limit on length, can include html)

### Listing your integration

To get your integration listed on our add-on store, please visit the following link. You are also welcome to send us any HTML you would like in the info/setup instructions by sending us an email to **<integrations@plannrcrm.com>**

{% embed url="<https://plannrcrm.com/add-on-form>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://api-how-to.plannrcrm.com/addons/add-on-store.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.