> For the complete documentation index, see [llms.txt](https://help.watcherlink.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.watcherlink.online/task-managers.md).

# TASK MANAGERS

- [Basic tasks](https://help.watcherlink.online/task-managers/basic-tasks.md): The Basic Task Manager allows you to create and track tasks that don’t require specific forms or workflows.
- [Maintenance tasks](https://help.watcherlink.online/task-managers/maintenance-tasks.md): The Maintenance tasks manager is designed to track and manage tasks related to servicing malfunctioning equipment.
- [Diagnostics](https://help.watcherlink.online/task-managers/diagnostics.md): This feature allows you to run diagnostics on devices, detect faulty components, and assign service repairs and statuses in the Maintenance Tasks manager.
- [Workflows & task types](https://help.watcherlink.online/task-managers/workflows-and-task-types.md): This guide will help you configure workflows and task types so you can flexibly manage the logic of custom tasks.
- [Custom tasks](https://help.watcherlink.online/task-managers/custom-tasks.md): Custom task managers provide a flexible way to organize work with tasks. They are built on top of pre-configured workflows and task types.


---

# 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://help.watcherlink.online/task-managers.md?ask=<question>&goal=<user_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.