> 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/launch-button.md).

# Launch Button

We also offer the ability to add a launch button to Plannr. This allows your integration to be launched fully from within the CRM. Your button would look like this:

<figure><img src="/files/zSoduPt8yTWzL6gfISFM" alt=""><figcaption></figcaption></figure>

We allow launch buttons on the following pages:

* Client Page
* Plan Page

The purpose of launch buttons is to seamlessly open your integration with just a click of a button. While this can be just a link to your application, you can also complete the full OAuth2 flow when this button is pressed.&#x20;

### Example OAuth2 Flow

1. User clicks on your launch button
2. The button will redirect to a URL of your choosing with the account (client) UUID / plan UUID in the URL
3. You store the UUID in the browser session and redirect to <https://api.plannrcrm.com/oauth/authorize>
4. The user is redirected back to Plannr where the OAuth2 flow happens, and then Plannr will redirect back to your application
5. You check your session if it has a launch UUID present, if so, take them to the resource directly on your system.

### Adding launch buttons to Plannr

If you would like to add a launch button to Plannr, please let us know the URL you would like us to point a button to, as well as the text you would like in the button. Note, you must also have an add-on for launch buttons to be visible.

To add a launch button, email us at **<integrations@plannrcrm.com>**&#x20;


---

# 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/launch-button.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.