> For the complete documentation index, see [llms.txt](https://docs.verbdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verbdata.com/data-transformations/building-transformations/transformation-steps/join-data.md).

# Join Data

Enables joining data between tables in a variety of join types. Join data requires any combination of two tables, Child datasets or data views to be placed and connected on the Transformation Canvas. Join Types include:&#x20;

#### Inner Join&#x20;

Returns values that have matching values in both tables&#x20;

#### Left Outer Join&#x20;

Returns values from the left table and the matched records from the right table.&#x20;

#### Right Outer Join&#x20;

Returns values from the right table and the matched records from the left table.&#x20;

#### Full Outer Join&#x20;

Returns values when there is a match in either the left or right table.&#x20;

#### Cross Join&#x20;

Creates a row to connect every left table row to every right table row.

Output will be all columns from the left table followed by all columns from the right table.


---

# 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.verbdata.com/data-transformations/building-transformations/transformation-steps/join-data.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.
