> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/custom-intents.md). # Custom Intents Custom Intents enable administrators to automate application activities and trigger specific actions based on predictable device states. It eases the efforts of both administrators and users by executing tasks automatically during lifecycle events such as login, logout, boot, or cradle. ### Device Events Custom Intents can be invoked on these [device events/state changes](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/custom-intents/technical-guide#device-events): * Pre Login * Login * Logout * Post Logout * Boot * Device Uncradled * Device Cradled * Device Screen On * Device Screen Off * Motion Lock Enter * Motion Lock Exit * Site Changed ### Intent Capabilities **Platform Actions:** Intents that are customized by BlueFletch to trigger operational tasks like clearing cache, deleting files, or adjusting settings. **Standard Android Intents:** Intents that are utilized to start apps, open activities, or send broadcasts using native Android capabilities. **Filtering:** Intents that are filtered to execute on targeted devices by matching session, device, or configuration attributes. For configuration details and examples, consult the [Technical Guide](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/custom-intents/technical-guide) for this feature. --- # 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.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/custom-intents.md?ask=&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.