Import
Coming soon
Active document must be open. A valid JSON export file must exist. Required pipe/duct/tray types must be loaded in the model. At least one level must exist in the document.
MEP curves, fittings, and family blocks are created in the document. A companion .import.log.txt file is written alongside the JSON file. Smart mapping and family export files are created for debugging.
When to use this
- User wants to import a full MEP layout from a JSON design tool export.
- User wants to recreate MEP routing from a 2D/3D design into Revit.
- User needs to import pipes, ducts, trays, and equipment from JSON.
Importing only radiators (use ImportRadCommand). Importing IFC, DWG, or native Revit formats. Exporting from Revit (use ExportJSON).
Inputs
| Name | Kind | Type | Required | Default | Description |
|---|---|---|---|---|---|
heightMode |
config | string |
no | — | Height mode: 'smart' (level-based) or 'json' (hardcoded Z) |
Returns
| Name | Type | Description |
|---|---|---|
CurvesCreated | int | Number of MEP curves created |
Elbows | int | Number of elbows placed |
FamiliesPlaced | int | Number of family blocks placed |
What you'll see in the chat
Starting MEP import workflow...
Resolving levels and MEP types...
Building node coordinates...
Creating MEP curves...
Placing elbows and fittings...
Importing family blocks...
Finalizing import...
REST API
This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:
POST /api/v1/commands/import- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
import json · import mep · json import · import pipes · import ducts · import layout
Patterns: import * json · import * mep · json * import · import * layout
Related
| Related commands | ExportJSON · ImportRadCommand |
|---|---|
| Pillar |