Describe the result, with enough detail to test it
Explain the workflow to Conduit in plain English. Include the details someone new to your firm would need to get it right:
- Software and users: where the app runs and who will use it.
- Scope: selected elements, categories, sheets, documents, or project records.
- Rules: parameter names, naming conventions, required values, or ownership rules.
- Output: the columns in a report, the issues to show, or the changes to apply.
- Exceptions: missing values, items outside the scope, and changes that need confirmation.
“Build a Revit export tool for the doors in the active view. Export element ID, Mark, Type, and Level to CSV in that order. Keep blank values blank, and leave the model unchanged.”
Use this as a brief pattern. Ask for the fields and output format your team actually needs.
Review the plan before launching
Answer the Builder’s clarification questions, then review the plan summary. Check which items it will work on, what it will produce, and what it will change. Adjust the plan before building.
Use Launch current plan when the plan is ready. Conduit builds a version of your app. A first version uses 40 generation credits; subsequent versions use 20.
If you have several unbuilt plans, review what is pending before launching. Discard pending unbuilt plans removes plans you no longer intend to build; it does not remove already built versions.
Connect the app to another platform
Tell Conduit which platforms your app needs to connect to. It can build integrations with any platform that has an API, using the access you provide. Describe the information to read, send, or sync, what should trigger the action, and whether data should move one way or both.
Conduit builds the connection around your requirements. In one test, the Conduit team used a single prompt to build an app that brings ClickUp tasks into Revit. Your own integration can use different systems or directions, depending on what their APIs allow.
When a credential is needed, Conduit asks for it in a masked secure form. Enter it there. The value stays out of the chat transcript and generated source; the app retrieves it securely at runtime.
App creators and workspace admins can update or delete saved credentials from App Overview without rebuilding the app. After a change, test the connection again with the access the new credential provides.
Check the version against a known result
Open Versions to inspect the build and choose the version to test. Code snapshots are available there if you want to review the generated source.
- Run one small example whose expected result you already know.
- Compare the actual rows, issues, or changes with that expected result.
- Try an exception from your brief, such as a missing parameter or an item outside the selected scope.
- For an app that changes data, check both the intended changes and the items that should stay untouched.
Templates accelerate the brief; your testing establishes whether the generated app fits your firm’s workflow.
Improve the same app over time
Return to the Builder with the app version, the case you tested, and a specific change. “Leave blank Mark values blank instead of exporting ‘Unknown’” gives Conduit a clearer target than “fix the export.”
Conduit can see how every app type is running for your team. Explain the result you want, and it can use that activity to help diagnose problems and improve the next version.
Each build becomes a separate saved version. Conduit retains the version history without a cap on saved versions; creating new versions uses generation credits. Test the next version, then send it to your team using one-click deployment and updates.