> For the complete documentation index, see [llms.txt](https://docs.valorx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valorx.com/valorx-fusion/design-studio/workflow-and-ux/launch-crm.md).
# Launch CRM
Designers have an option to launch the app rom **CRM** or **Salesforce** when, they want. This is made simple with one of our workflow properties **Launch CRM**. Designers will have to create a Launch CRM task query which will be displayed under workflow.
Open an app and select Workflow and UX from Valorx Fusion Ribbon.
Designers will find Workflow Settings on the right hand side. Click on the drop-down and the Workflow properties gets expanded. Designers can find two options like Launch from CRM and Run at App Launch.
Select "Launch from CRM " this will provide the Launch from CRM instructions button click on it and a popup window opens which will guide the user on how to configure a workflow to launch it from CRM.
Refer [**Launch from CRM**](/valorx-fusion/runtime/runtime-ux/launch-from-salesforce-lfs.md) to know more information on the instructions button.
Designers can easily find when an app is selected to Launch from CRM as the app will be marked with the symbol shown below.
---
# 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://docs.valorx.com/valorx-fusion/design-studio/workflow-and-ux/launch-crm.md?ask=&goal=
```
`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.