> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/api/client-libraries/redivis-r/reference/workflow/workflowusdquery.md).

# Workflow$query

### Workflow$<mark style="color:purple;">query</mark>(*query\_string*) → [Query](/api/client-libraries/redivis-r/reference/query.md)

Execute a SQL query scoped to a workflow. Table names do not need to be fully qualified, since all tables are assumed to be within the workflow.

### **Parameters:**

**`query_string` :&#x20;*****str*** \
The SQL query to execute. Must follow the [Redivis SQL query syntax](https://docs.redivis.com/reference/projects/transform-nodes/raw-sql).

### **Returns:**

[**Query**](/api/client-libraries/redivis-r/reference/query.md)

### Examples

<pre class="language-r"><code class="lang-r">workflow &#x3C;- redivis$user("imathews")$workflow("example_workflow_climate_analysis")

# The query can reference any table in the workflow
query &#x3C;- workflow$query("
    SELECT
        id,
<strong>        EXTRACT(YEAR FROM date) AS year,
</strong>        SUM(value) AS annual_precip
    FROM daily_observations
    WHERE (element = 'PRCP')
    GROUP BY id, year
")
query$to_tibble()
# 	id	        year	    annual_precip
# 0	CA0023026HN	2003	    2925.0
# ...
</code></pre>


---

# 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.redivis.com/api/client-libraries/redivis-r/reference/workflow/workflowusdquery.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.