Import

Start from what you already have: a curl command, a Postman, Bruno or Insomnia collection, an OpenAPI description, or a recording of what your browser sent.

Import on the left opens the menu. Every import shows a preview first: what comes in, and anything for you to check. Then it opens as a new flow, or is added to the end of the open one (one undo step).

The Import menu: cURL command, HAR recording, OpenAPI / Swagger, Postman collection, Postman collection folder (v3), Postman environment, Bruno collection, Insomnia collection
The Import menu.

cURL

Three ways in: Import → cURL command (added at the end of the flow), + between two steps → cURL (added there), or paste the command straight into a request's URL field. That fills in the method, URL, headers and body and keeps the request's checks, extract rules and loop.

curl 'https://api.example.com/orders' \
  -H 'Authorization: Bearer $token' \
  --json '{"item":42,"qty":2}'

Postman

Import → Postman collection: pick the exported file (Collection v2.0 or v2.1, or a v3 collection saved as one file). For Postman 12's Git format, see Postman v3 folders below.

In PostmanIn CLEM
FoldersName prefixes: Users / Create user
Collection variables {{name}}Flow variables $name (base-url becomes $base_url)
Auth (Bearer, Basic, API key, OAuth 2.0)CLEM auth: the collection's is the flow's; a folder's or a request's own goes to its requests' Auth tab
pm.environment / collectionVariables / variables .get / .set$variables. Reading one nothing has set yet gives undefined, as in Postman: if (!pm.environment.get("token")) becomes if (!globalThis.$token). A name worked out in code (pm.environment.unset(names[i])) becomes globalThis[clemVarKey(names[i])], with a small clemVarKey function at the top that names the variable as the import does
pm.response.json(), .code, .responseTime, .headersresponse
pm.test + pm.expect (a function or an arrow, () => pm.response.to.have.status(200))assertEqual(), assertContains()… or check(); tests on the status, time or a header go to the Checks tab. A chain with .and (.to.be.a("string").and.to.have.length.above(0)) checks each part; .length.above(n) and .lengthOf.at.least(n) check the length
pm.test.skipA comment: Postman only reports it as skipped
Folder and collection scriptsRun once where the folder starts (tests: commented)

A script that can't run in CLEM as it is comes in commented out, with the reason, in a step whose name ends in "(to convert)". Nothing that would fail is left running. That covers:

Requests with no URL come in with an empty one and a note, so you can fill them in. A Bruno request file that is empty or cut off (a block that is never closed) is skipped with a note naming the file, and isn't counted. An Insomnia request whose folder is missing from the file comes in at the top, with a note.

Imported flows keep running after a failed step, like Postman's runner (Flow Settings).

Import → Postman environment adds an environment (or a globals export) to the flow's project under a name you choose, and selects it. A v3 environment file (YAML) works too.

Postman v3 folders (Postman 12's Git format)

Postman 12 can keep a collection in a Git repository as a folder of YAML files: one .request.yaml file per request, and a .resources/definition.yaml for the collection and each folder. Newman can't run these; CLEM imports them directly.

  1. Import → Postman collection folder (v3).
  2. Pick the collection's folder, or the repository (or its postman folder). When it holds several collections, choose one (the biggest is proposed); import the folder again for another.
  3. The preview and the save work as for a Bruno collection: the flow is saved into a project, and the environments in postman/environments become that project's environments, the first one selected.

The requests and scripts come over as from a v2.1 collection (the table above), plus:

In the v3 filesIn CLEM
Folders and orderName prefixes, in Postman's order
A collection's or folder's auth, a list of several (chosen by rules)Inherited as in v2.1; of a list, the first is used (noted)
GraphQL requests (graphql-request)GraphQL requests, with the operation name
WebSocket requests (websocket-request)WebSocket requests that send the saved messages (binary ones as text, noted)
Request settings: follow redirects off, HTTP versionThe request's own settings; "don't verify certificates" is noted
Workspace globals (postman/globals)Flow variables the collection doesn't define itself
Secret variablesEmpty variables, noted: make them secrets
Saved examples, gRPC / Socket.IO / MQTT / Kafka / MCP / AI requestsNot imported; the notes count them

Bruno

Import → Bruno collection: pick the collection's folder, the one with bruno.json (the .bru format) or opencollection.yml (the YAML format of Bruno 3). A JSON file from Bruno's Export → Bruno Collection works through Postman collection or OpenAPI.

Insomnia

Import → Insomnia collection: pick an Insomnia export. In Insomnia, use Export on the collection (or design document) and choose Insomnia v5 (a YAML file) or Insomnia v4 (a JSON file); both work, and so do the files Insomnia keeps in a Git repository. An export of all your data can hold several workspaces: CLEM asks which one to import.

OpenAPI / Swagger

Import → OpenAPI / Swagger: an API description in OpenAPI 3.0 or 3.1, or Swagger 2.0, as JSON or YAML. Each operation becomes a request step, grouped by tag and named after its summary (pets / Add a pet). The preview lets you choose the tags to import.

HAR recordings

Record what a web app does in the browser, and replay it as a flow. Browsers save a .har from DevTools → Network → Save all as HAR (Chrome, Edge, Firefox, Safari); Charles, Fiddler and mitmproxy export them too. Import → HAR recording.

Going the other way, to hand a request to someone: Copy as cURL, HTTPie, fetch, Python or PowerShell.