> 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/reference/workflows/overview.md).

# Overview

Workflows are used to analyze data on Redivis at any scale. They allow you to organize your analysis into discrete steps, where you can easily validate your results and develop well-documented, reproducible analyses.

Workflows are owned by users or [organizations](/reference/organizations.md), and can be [shared](/reference/workflows/collaboration-and-sharing.md) with other users and organizations.

<div data-with-frame="true"><figure><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FNXJc1Okv8TTDJiUebDC1%2Fredivis.com_workflows_x7kh-5pvd4mbf1_tables_467g-0nqepj0am%20(2).png?alt=media&amp;token=4e26560b-c3ee-48d6-9d55-4948ed5de56f" alt=""><figcaption></figcaption></figure></div>

## The workflow page

The workflow page consists of a top title bar, a left pane, and a right pane.

The **left pane** displays the workflow tree, allowing you to visualize how data is moving through the workflow and its nodes. Switching between nodes is the main way of navigating around a workflow.

The **right pane** shows the contents of the currently selected node. If no node is selected, this panel will display the workflow's overview and metadata. You can select the workflow title or empty space in the workflow tree to return to the workflow overview at any time.

The **title bar** provides an entry point to common actions, broken into two sections. The left section contains actions that are global to the workflow while the right section contains actions relevant to the currently selected node, such as running a transform.

## The workflow tree

The workflow tree is represented visually in the left pane of the workflow. This tree is comprised of a collection of nodes, with each node having various inputs and outputs, such that the output, or result, of one node can serve as the input of another.

Data in the tree flows from the top to bottom. Circular relationships are not allowed. Formally, this is known as a "Directed Acyclic Graph" (DAG).

Selecting a node within the tree will display that node's contents within the right pane of the workflow, while highlighting the ancestors and descendants of that node on the tree.

You can right-click on any node for a list of other options. Similarly you may select the node then the three-dot "More" menu at the top-right.

## Workflow nodes

The workflow tree is made up of the following node types:

<div data-with-frame="true"><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FWgIptK1DwdBh7wGGXdj0%2FScreenshot%202024-12-03%20at%2012.09.20%E2%80%AFPM.png?alt=media&amp;token=7daf955f-b94d-4b15-a58a-95978bb4fe90" alt=""></div>

[**Data sources**](/reference/workflows/data-sources.md) represent datasets or workflows that have been added to a workflow, and are the mechanism for bringing data into a workflow.

[**Tables**](/reference/workflows/tables.md) are either tables associated with a data source, or the resulting output table of a transform or notebook.

[**Transforms**](/reference/workflows/transforms.md) are queries that are used to reshape and combine data, always creating a single table as an output.

[**Notebooks**](/reference/workflows/notebooks.md) are flexible, interactive programming environments, which can *optionally* produce a table as an output.


---

# 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.redivis.com/reference/workflows/overview.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.