Importing from Insomnia
Vegha imports Insomnia exports in both the v4 and v5 export formats. The import converts the source into native .bru collection files in your workspace.
Exporting from Insomnia
Section titled “Exporting from Insomnia”In Insomnia, export from the workspace menu and choose the Insomnia v4 or v5 export format. This produces a JSON (or YAML, for v5) file containing requests, folders, and environments.
Running the import
Section titled “Running the import”Open the Import dialog with Ctrl+I, select the export file, and choose a destination folder. Vegha reads the export, recreates the folder tree, and writes a .bru file per request.
How Insomnia concepts map
Section titled “How Insomnia concepts map”| Insomnia | Vegha |
|---|---|
| Workspace / Collection | A .bru collection folder |
| Request group (folder) | A subfolder |
| Request | A .bru request file |
| Base environment | Collection-level variables |
| Sub-environment | An environment in the workspace |
| Auth settings | Native request or collection auth |
Headers, query parameters, path parameters, and request bodies are carried across directly. Nested request groups are preserved as nested folders.
Caveats
Section titled “Caveats”- Environment inheritance — Insomnia layers a base environment under each sub-environment. After import, confirm that variables resolve as expected, especially where a sub-environment overrode a base value.
- Template tags — Insomnia template tags (e.g. response chaining, prompts) do not have a one-to-one equivalent and may need to be rewritten as variables or scripts.
- Secrets — environment values are imported as plain text. Move sensitive values to secret variables after import.
- Plugins — behavior provided by Insomnia plugins is not imported.