> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/odin-ai/scheduled-prompts.md).
# Scheduled prompts
Odin lets you schedule an automated cadence of emails with your most important metrics analyzed.
### How does it work?
1. Go to the Odin tab in the navigation bar
2. Open the "Prompts" section and click "+ Saved Prompt"
3. Give it a name and toggle "Schedule Sendout"
4. Now it’s time to define your prompt: type your business question and tell Odin what you want to analyze
5. Refine your prompt until the analysis matches your needs
6. Test it by sending the analysis to yourself via email using the button in the bottom-right corner
7. **Now it's time to do the scheduling!**
8. Pick the frequency: daily, weekly, or monthly
9. Choose the delivery time and day
10. Select the recipients
11. Click "Save"
**You're all set!**
### Managing saved prompts:
In the "Prompts**"** section, you can run, edit, or delete existing prompts.
You can also view a full list of all analyses Odin has performed in the "Past Analyses" section.
---
# 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.hockeystack.com/marketing-intelligence/odin-ai/scheduled-prompts.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.
