> 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/tasks/respond-to-a-workflow-task.md).

# Respond to a workflow task

A workflow task records a decision or follow-up that a customer workflow needs from your team. It can include a set of response buttons chosen by the workflow.

Some workflow tasks are **approval tasks**: a workflow that wants to email or text a customer, or make another higher-risk change, pauses and asks first. The task lists exactly the actions the run wants to take, with **Approve** and **Decline** buttons. Approving executes exactly those listed actions within a few minutes; declining stops the run and nothing is sent or changed.

> **Where to find it:** Open **Tasks**, then select the **Workflows** folder. The folder appears once Workflows is enabled for your business and a workflow has created its first task.

## Respond to the task

1. Select the task from the list.
2. Review its customer, details, and available responses.
3. Select the response that matches the decision. A workflow response is final once selected and may start the workflow's next step — or, for an approval task, run or stop the paused actions.
4. Use the status and Notes fields for your team's internal tracking, then select **Save**.

Changing the status or Notes field does not save automatically. **Cancel** restores the last saved values.

## Related guides

* [Run a workflow for a customer](/field-operations/workflows/run-a-workflow-for-a-customer.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 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/tasks/respond-to-a-workflow-task.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.