> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/freelucy/work-in-the-app/data-hub.md).

# Find records with the Data Hub

Search, browse, and pull records in to relate to your primary element.

The Data Hub is the drawer you source records from. Open it to search the tables that make sense for your primary element, browse a record tree, and add one or many records as relationships.

<figure><img src="https://4267074599-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJwX0HDB6chAHkVR797eQ%2Fuploads%2F6yIBiwq97Iop3wBNUDvw%2Fimage.png?alt=media&amp;token=1bfd7e2d-f76a-4153-a17a-b0cf9c1147e5" alt="" width="375"><figcaption></figcaption></figure>

## Open the Data Hub

Open the Data Hub from the editor. It opens as a drawer alongside your current view and stays out of the way of the canvas.

## Find a record

1. The Data Hub suggests tables based on your primary element. Search to narrow them.
2. Expand a table to browse its records as a tree, or search within it.
3. Records that are valid to relate to your primary element are the ones YouDesign Freelucy lets you add.

## Add records

Once you have found the record or records you want:

* **Add to a side directly.** Use a record's **Add to Upstream** or **Add to Downstream** action. Freelucy resolves the relationship type, asking you only when more than one type applies.
* **Drag onto a drop target.** Drag a record out of the Data Hub. Valid drop targets light up in your current view. Where those targets are depends on the view, so see the [view guides](/freelucy/views-in-depth/classic.md) for specifics.

## Add many at once

You do not have to add records one by one.

1. Hold **Ctrl** or **Cmd** and click each record you want. Selected records highlight.
2. Add them all with the **Add to Upstream** or **Add to Downstream** action, or drag the whole selection onto a valid drop target.

<figure><img src="https://4267074599-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJwX0HDB6chAHkVR797eQ%2Fuploads%2F3Xip92tBbwSq7drtpr1D%2Fimage.png?alt=media&amp;token=06096bdb-d220-44f5-8dbe-56d4d79cf8e4" alt="" width="375"><figcaption></figcaption></figure>

See [Create multiple relationships at once](/freelucy/work-in-the-app/create-multiple.md) for the full walkthrough.

{% hint style="info" %}
**Valid sides light up as you drag.** While you drag from the Data Hub, every view highlights the sides and drop zones your metamodel allows. If a side does not light up, that relationship is not permitted for the records you picked.
{% endhint %}

***

## What's next

* [Filter and sort with View Controls](/freelucy/work-in-the-app/view-controls.md)
* [Create a relationship](/freelucy/work-in-the-app/create-relationship.md)
* [Create multiple relationships at once](/freelucy/work-in-the-app/create-multiple.md)
* [Choose a view](/freelucy/get-started/choose-a-view.md)


---

# 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.ins-pi.com/freelucy/work-in-the-app/data-hub.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.
