Get model data into the format your team uses.
Build one repeatable export from Revit to CSV or a spreadsheet-friendly format. Define the fields, order, and scope so downstream reports start with consistent data each time.
Use this template to build your own app with Conduit. Describe your requirements in plain English and review the plan. Conduit writes the code; you test the result and ask for refinements.
When to use this starter
Teams preparing model data for spreadsheets, reporting, or another system’s input format.
Bring these details
- The model elements or categories to include in the export.
- The exact fields, column names, and column order the receiving team needs.
- The output format and how blank values or units should be represented.
Shape the first version
- Export the fields you need from the selected model elements.
- Produce the same column structure on each run.
- Keep the first version focused on a single export your team can check and reuse.
A brief you can adapt
Start with this example, then add your project’s requirements and rules.
Build a Revit tool that exports the selected elements to CSV. Ask me for the fields, column names, and order. Keep empty values blank and leave the model unchanged. Use the same column structure every time so our reporting spreadsheet can read the file.
Check the result before sharing it
- Compare a few exported rows with the values visible in Revit.
- Check column order, blank values, and any unit formatting you requested.
- Run the export again on the same selection and confirm the structure stays consistent.
From your first build to your team
Test your generated app in Revit, refine it in the Builder, and choose the version to deploy. One Desktop Runner install delivers assigned Conduit-built apps to each teammate and keeps them updated.
Your versions stay in Conduit. Every app reports how it’s running for your team, helping Conduit diagnose problems and make improvements.
Ready to make it yours?
Build your team’s version of Data Exporter.