Dynamo for Civil 3D: 10 scripts that automate repetitive work, and when to move to a plugin

Dynamo has shipped with Civil 3D since 2020. It lives on the top toolbar, Manage tab, Visual Programming panel. Dynamo Player sits right next to it, included since the 2020.2 update.

Out-of-the-box nodes grew a lot in 2025. The 2025.1 update added 1,120 new nodes to the 226 that already existed: corridors, alignments and profiles, surfaces, pipe and pressure networks, feature lines, parcels, COGO points, property sets, layouts and viewports, among others. 2025.2 added 62 label nodes, and 2026 added catchments and feature lines created from a list of points.

The practical consequence: a script built with the new nodes won't run on earlier releases. If your office mixes versions, decide which one each script targets.

The packages that cover the rest:

• Camber: open source, with hundreds of nodes for labels, data shortcuts, xrefs, styles, sample lines and pipe networks.
• Civil 3D Toolkit: a large inventory of additional nodes for Civil 3D.
• The Civil Nodes: more than 850 nodes for Civil 3D 2025.1 and later. It continues the Arkance Systems library, which stopped working with Civil 3D 2025.

Script 1. Place blocks along an alignment.

• What it does: places a block — light pole, sign, station marker, proposed manhole — at a set interval and offset from the centerline, rotated to the alignment's direction and set at the surface elevation.
• What it saves: copying, rotating and adjusting by hand, and redoing it every time the alignment changes.
• What it needs: out-of-the-box alignment, surface and block nodes. If the alignment changes, you run it again and everything is re-placed.

Script 2. Stakeout points from an Excel table.

• What it does: reads a table with station, offset and description — for example, the edges of pavement every 50 ft — and creates the COGO points with their number, coordinates and elevation.
• What it saves: calculating coordinates by hand and the typos in the staking list.
• What it needs: Dynamo's Excel nodes plus the out-of-the-box alignment and COGO point nodes. The result is a point group ready for the total station or GNSS rover.

Script 3. Rename and number to the standard.

• What it does: renames alignments, profiles, surfaces or network structures following the office convention, such as CL-01, CL-02 or MH-001 in the direction of flow.
• What it saves: endless clicks, and inconsistent names that later break tables and data shortcuts.
• What it needs: reading the objects, sorting them by station, position or flow direction, and assigning the name by rule. For network structures, out-of-the-box nodes since 2025.1, or Camber before.

Script 4. Cut and fill table to Excel.

• What it does: walks the alignment at a set interval, or at the stations you list, and exports to Excel the station, existing ground elevation, finished grade elevation and cut or fill depth.
• What it saves: the table built by hand for the plans, which has to be redone every time the profile changes.
• What it needs: out-of-the-box profile nodes and the Excel nodes.

Script 5. Export COGO points by code or group.

• What it does: exports only the points with a given code, such as EP or CL, or from a group, in the order, columns and format the field crew or the client asks for. One file per code, one click.
• What it saves: filtering and reordering in Excel before every delivery. Civil 3D already exports points; the script adds what the command doesn't: the same format every time, for every group at once.
• What it needs: out-of-the-box COGO point and point group nodes, plus the Excel or text file nodes.

Script 6. Sample lines at the stations in a table.

• What it does: creates the sample lines for cross sections at the exact stations in a list (the ones in the plans, the control points, the section changes), with the swath width you set on each side.
• What it saves: creating sections one by one when they don't fall at regular intervals.
• What it needs: on Civil 3D 2025.1 or later, out-of-the-box sample line nodes; on earlier releases, Camber.

Script 7. Check pipe slopes.

• What it does: walks the sewer network, calculates the slope of every pipe and flags the ones below your standard's minimum or above the maximum, with a report in Excel.
• What it saves: checking pipe by pipe before every submittal, and the reviewer's comments.
• What it needs: out-of-the-box pipe network nodes since 2025.1, or Camber before. The minimum-slope criterion comes from your local standard — in much of the US, the Ten States Standards or your state's rules — and you set it in the script.

Script 8. Verify layer and style standards.

• What it does: checks that every object is on the layer and uses the style required by your office or client standard, and returns a list of what doesn't comply, or fixes it.
• What it saves: the visual check before every submittal and the rejections over formatting.
• What it needs: out-of-the-box object and layer nodes, plus an Excel table with the standard, so you can change it without touching the script.

Script 9. Automatic labels.

• What it does: labels stations, ground elevations, slopes or points with the right label style, on every object at once.
• What it saves: labeling one by one and missing some.
• What it needs: on Civil 3D 2025.2 or later, out-of-the-box label nodes; before that, Camber.

Script 10. Drape polylines onto the surface.

• What it does: turns the 2D polylines of a drawing — edges of pavement, ditches, fences — into 3D polylines or feature lines at the surface elevation, to use as breaklines or in the design.
• What it saves: Civil 3D does this object by object with its command; the script does it for every polyline on a layer at once, with the right name and style for each.
• What it needs: out-of-the-box surface and feature line nodes. Since the 2026 release, one node creates the feature line straight from a list of points.

The Dynamo editor intimidates anyone who didn't build the script. Dynamo Player solves that: it lists the scripts in a folder and runs them with one click, without opening the editor. It's on the top toolbar, Manage tab, Visual Programming panel.

• Inputs up front. The values that change on each run — the alignment, the interval, the Excel file — are marked as inputs in the script, and the Player shows them as a simple form.
• Pick in the drawing. Since 2025.2, a node lets the user pick a point in the drawing while the script runs from the Player.
• One shared folder. Approved scripts live in a network folder, so the whole team runs the same version.

• One task per script. It's easier to test, explain and maintain.
• Group and name the blocks — inputs, calculation, output — and write notes. Whoever opens it a year from now should understand it without calling you.
• No hidden values. Distances, layers and styles go in as inputs or in an Excel table with the standard.
• Use the OpenXML-based Excel nodes. They don't need Excel installed, and since Dynamo 3.5 they replace the legacy nodes.
• Write down the release of Civil 3D and of the packages it works with. An updated package can break a script.
• Test on a copy of the drawing, and check one stretch before running it on the whole project.
• Keep scripts under version control, not on the desktop of whoever wrote them.

Dynamo is ideal for proving an automation quickly. Its limits show up as usage grows: it slows down with thousands of objects, depends on third-party packages and on the release, anyone can open it and break it, and it has no interface with its own validation.

The rule of thumb: if the whole office uses a script every week, it's a plugin candidate. We explain it in Dynamo vs C#, which one fits each case, and the budget in how much a Revit or Civil 3D add-in costs.