> 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/administration/settings/automate-task-statuses-with-task-automations.md).

# Automate task statuses with Task Automations

Task Automations, sometimes called task status automations, control how a task's status updates automatically when something happens in Essential. Use them to keep task folders clean after your team takes the expected next action.

For example, you can set a Recurring Services Approved task to move to a done status when someone uses Quick Action: Create Job / Visit, set a bounced quote task to move to done after Edit Contact and Resend, or set an overdue invoice task to move to done when the invoice is marked paid, void, or uncollectible.

The left side groups the triggers by source: Recurring Services (Approved, Declined, Ask Someone Else, Email Bounced, Unanswered, Custom), Quotes (Signed, Email Bounced, Unanswered), Jobs (various completion outcomes), Invoices (Email Bounced, Overdue, Payment Failed), and Deficiencies. Pick a source to see the triggers available for that folder.

For each trigger you choose, under "What should the status be set to?", the task status to apply when that event occurs. To clear a task from the active folder count, choose one of your business's done statuses, such as Completed. Choosing "Do not change status (automation off)" turns that trigger off. Each trigger maps to at most one rule, and your edits aren't saved until you use Save.

> **Where to find it:** Settings -> Work Management -> Tasks -> Task Status Automations tab

## Related guides

* [Add, rename, reorder, or remove task statuses](/administration/settings/add-rename-reorder-or-remove-task-statuses.md)
* [Task folder and subfolder meanings](/field-operations/tasks/task-folder-and-subfolder-meanings.md)
* [Quick Actions on a task: create a visit, invoice, or quote without leaving the task](/field-operations/tasks/quick-actions-on-a-task-create-a-visit-invoice-or-quote-without-leaving-the-task.md)
* [Working a task: changing its status and saving notes](/field-operations/tasks/working-a-task-changing-its-status-and-saving-notes.md)
* [The Tasks inbox: folders, status filters, and search](/field-operations/tasks/the-tasks-inbox-folders-status-filters-and-search.md)


---

# 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/administration/settings/automate-task-statuses-with-task-automations.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.
