> For the complete documentation index, see [llms.txt](https://docs.finch3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finch3d.com/courses/finch-101-1/upload-objects-from-revit-to-finch.md).

# Upload objects from Revit to Finch

{% embed url="<https://youtu.be/MluH-A7XxfA>" %}

> **💡 Inner and Outer Bounds families can be saved from the link below and nested into your own Revit families.**

{% file src="/files/0Iit0cAQmbCI2i7qwAlX" %}

### 1: Open the Revit Project

1. Open the Revit project containing the families you want to upload.
2. Locate the families in the project (for example: beds, sofas, or plumbing fixtures).
3. Open one of the families to review its contents.

***

### 2: Verify Family Structure

1. Confirm the family includes:
   1. The main object geometry.
   2. A nested **Outer Bounds** family.
   3. A nested **Inner Bounds** family.
2. Open the **Outer Bounds** family and verify:
   * It is a **Generic Model**.
   * It is assigned to the **Outer Bounds** subcategory.
3. Open the **Inner Bounds** family and verify:
   * It is a **Generic Model**.
   * It is assigned to the **Inner Bounds** subcategory.

***

### 3: Prepare Revit for Upload

1. Open an **active Plan View**.
2. Ensure the **Finch Revit Plugin** is installed and up to date.
3. Open the Finch plugin and navigate to the **Objects** tab.

***

### 4: Find Families in the Active View

1. Click **Find Families**.
2. Enable **Show only visible in current view**.
3. Review the list of families grouped by category.

***

### 5: Upload Objects to Finch

1. Select the families you want to upload.
2. Click **Upload**.
3. Wait for the upload process to complete.

***

### 6: Confirm Objects in the Finch Object Library

1. Open Finch.
2. Navigate to your **Object Library**.
3. Locate the uploaded objects.
4. Open an object to confirm:
   1. Object geometry is visible.
   2. Inner Bounds are present.
   3. Outer Bounds are present.

***

### 7: Use Objects in a Finch Project

1. Open a Finch project.
2. Generate a layout using the uploaded objects.
3. Confirm the objects appear correctly in the generated plan.

***

### 8: Import Finch Geometry into Revit

1. Return to Revit.
2. Open the Finch plugin and navigate to the **Project** tab.
3. Select the project and variant.
4. Click **Import BIM**.

***

### 9: Map Objects During Import

1. In the **BIM Import** window, open **Import Settings**.
2. Under **Furniture**, review the object mappings.
3. Confirm that objects with matching names are mapped automatically.
4. Click **Save**.
5. Click **Import BIM**.

***

### 10: Review the Imported Geometry

1. Open the imported view in Revit.
2. Switch to a **3D view**.
3. Verify that all objects are correctly mapped and placed.


---

# 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.finch3d.com/courses/finch-101-1/upload-objects-from-revit-to-finch.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.