Getting Started
Which file does each tool need?
Not every tool needs the same file. This is the lookup table.
The table
| Tool | Needs | Paid Bubble plan? |
|---|---|---|
| Database Visualizer | user_types only | No |
| Workflow Tracer | any of pages, element_definitions, api | Yes |
| Reusables Tree | pages or element_definitions | Yes |
| Design System | pages or element_definitions | Yes |
| Audit | pages or element_definitions | Yes |
| JSON Sanitizer | any JSON object | Yes, in practice |
The Design System tool also reads styles and settings, but it does not require them. Without those keys the element tree still loads; it just has no named styles to list and no colour or font tokens from settings.client_safe to resolve against.
The "paid plan" column is about Bubble, not LumiDevKit. LumiDevKit is free. But the full application export that four of these tools need is only enabled on Bubble's Starter plan and above, so on a free Bubble app you cannot produce their input at all. See get your app export out of Bubble.
Two rules that cover most cases
A full application export works everywhere. Every tool on this page accepts it. The Database Visualizer simply picks out user_types and option_sets and ignores the rest.
A database-only file works only in the Database Visualizer. A file containing just user_types and option_sets — which is what LumiDevKit's own "Download JSON" produces, and what an AI produces from our prompt — has nothing for the other tools to read. Uploading it to the Workflow Tracer gives you "Invalid Bubble JSON format. Expected workflow data."
The Database Visualizer is the exception
It needs one key: user_types. That is why it accepts three quite different things:
- A full Bubble application export.
- A small schema file with just
user_typesandoption_sets, including one generated by an AI. - A Postgres schema as
.sql.
It also has a "Start from scratch" mode that needs no file at all — see build or edit a schema by hand.
One caveat about sanitized files
The JSON Sanitizer removes settings.client_safe.plugins, and that is exactly the key the Workflow Tracer reads to turn plugin action IDs into readable plugin names.
A sanitized export still traces workflows correctly. Plugin actions just show their raw identifiers instead of friendly names. Sanitize when you are sharing; use the original when you are working on your own machine.
If you uploaded the wrong file
Every error message and its cause is listed in upload errors, decoded.