Commands › Drainage › M E P System Auto Fillet
M E P System Auto Fillet
Coming soon
Before you run this
Active document must be open. At least two pipes must exist.
After it runs
Appropriate fitting created based on selection proximity. Pipes are connected.
When to use this
- Smart pipe connections without manual fitting selection.
- Creating either endpoint or mid-pipe connections.
- General-purpose pipe connection tool.
Don't use this when
Not for autonomous AI execution. This command requires interactive Revit UI input (dialogs, picks, or manual confirmation).
Side effects
May move target pipe. May break reference pipe (for tee). Creates fitting element.
Inputs
| Name | Kind | Type | Required | Default | Description |
|---|---|---|---|---|---|
ReferencePipe |
selection | Pipe |
yes | — | Reference pipe (endpoint or mid-pipe) "Select REFERENCE pipe (click near endpoint for elbow, mid-pipe for tee)" |
TargetPipe |
selection | Pipe |
yes | — | Target pipe to connect "Select TARGET pipe to connect" |
EndpointThreshold |
config | double |
no | 25.0 | Distance threshold for endpoint detection |
Returns
| Name | Type | Description |
|---|---|---|
CreatedFitting | FamilyInstance | The fitting created (elbow or tee) |
FittingType | string | Type of fitting used |
Decision flow
check: document.isOpen → continue action: promptUserToSelectReferencePipe → getReferencePipe action: promptUserToSelectTargetPipe → getTargetPipe check: bothPipesValid → continue, else → error decision: distanceToEndpoint ≤ 25mm → useElbow, else → useTee action: createFitting → connect resolve: success → complete, else → showError
What you'll see in the chat
on start
Auto-detecting fitting type...
Choosing elbow or tee based on selection...
Choosing elbow or tee based on selection...
thinking
Checking distance to nearest unconnected endpoint...
Determining elbow vs tee (threshold: 25 mm)...
Creating fitting and connecting pipes...
Determining elbow vs tee (threshold: 25 mm)...
Creating fitting and connecting pipes...
on success
{FittingType} fitting placed successfully.
on failure
Auto-fillet failed: {error}
REST API
Not yet exposed
This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:
POST /api/v1/commands/mepsystem_auto_fillet- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
auto fillet · smart connect · auto fitting · connect pipes auto · smart fillet
Patterns: auto * connect · smart * fillet · connect * auto
Related
| Related commands | MEPSystemFilletCommand · MEPSystemTeeCommand |
|---|---|
| Pillar | Drainage |