> For the complete documentation index, see [llms.txt](https://docs.valorx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valorx.com/valorx-fusion/design-studio/workflow-and-ux/query.md).

# Query

Query Task is one of the properties where Designers will make the steps. Whenever we drag and drop any task from Toolbox to designer canvas it becomes a step of the workflow. So for every step in workflow there is a common property called Step Name which is a Task name by default but user can overwrite it anytime. Lets have a quick look at the task properties of different tasks.

Every Query task returns data and every step created from Query task needs an Output Name to uniquely identify the data retrieved in that specific step. Query task can also contain Filters of different types. Whenever filter of type Data Intake is there in Query it requires that Data Intake to execute the Query task. For such Data Intake filtered tasks Query properties will have Data Intakes section to select required Object data which is nothing but an output of other task. Edit button to edit actual Query Task associated with the step.

Expand the Query Task and you will find all the Maps. Drag and drop it in the workflow below the **Start** button.

![](/files/nvh0763gsxffxad5h4i0)

On the right hand side we can find Workflow Settings where Designers will add the Data Intake and select the Ribbon Icons which will be displayed under **Workflow Trigger**.

![](/files/eyG7vEqkeSB4q4VYuj0n)


---

# 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://docs.valorx.com/valorx-fusion/design-studio/workflow-and-ux/query.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.