> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/tasks/task-items.md).
# Task Items
Each task offers a unique functionality that runs after a respondent has submitted his answers. Task are run in the top to bottom order of your task pane.
{% hint style="info" %}
Task will only run once the respondent has submitted his answers. Task are not triggered for responses updates of existing answers.
{% endhint %}
## ➕ **Adding a task**
To add a new task to your survey you may either use the **Add task** button or choose from the available tasks list.
## 🔅 Task properties
* **`Enabled`** a task will only run if its enabled and if it matches its [trigger ](/form-management/tasks/triggers.md)conditions.
* **`Submit`**will only run the task when any new respondent has been saved.
* **`Update`**will only run if its any existing respondents has updated their answers.
---
# 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://docs.ngsurvey.com/form-management/tasks/task-items.md?ask=&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.
