> 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](/files/YwChAr7kF8fUzX6AO7Vr)

> **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 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://learn.withessential.com/field-operations/custom-tasks/see-and-browse-your-custom-tasks-the-custom-tasks-page.md?ask=<question>&goal=<endgoal>
```

`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.