> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/custom-tasks/see-and-browse-your-custom-tasks-the-custom-tasks-page.md).

# See and browse your custom tasks (the Custom Tasks page)

The Custom Tasks page lists your recurring custom tasks: work that an asset group's automation creates as a manual task for your team each cycle, instead of sending outreach to the customer. Filter by status (Scheduled or Complete).

Each row shows when the next task is created (Task Creation), the Task Description, the Property, **Asset Group Type**, and the Status. This column shows the equipment type the task covers. Click a row to open that specific custom task and its schedule.

A custom task exists because an asset group's Automation Setup is set to Custom Task, so the recurring service creates the task on its cadence rather than emailing or texting the customer.

You can also ask Essential to find custom tasks by description, property, or account, or about the one you're viewing.

![Custom tasks page](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-7a6facdc3b2028dcf1f6f83e113f4bc6a10a5f63%2Fcustom-tasks-list.png?alt=media)

> **Where to find it:** Automations, then the Custom Tasks page (route /automations/custom-tasks)


---

# 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://learn.withessential.com/field-operations/custom-tasks/see-and-browse-your-custom-tasks-the-custom-tasks-page.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.