Sharing Flows
A flow is only worth building once if you can hand it to someone else — a teammate, your future self, or a CI job. Probe's .proflow format makes an export self-contained: the requests it references, any sub-flows it calls, and a manifest of whatever inputs the recipient needs to fill in.
Exporting
Section titled “Exporting”Right-click a flow in the FLOWS sidebar section and choose Share…. Probe builds the export and opens a review dialog showing:
- A summary of what's included (nodes, requests, sub-flows).
- A secrets-stripped banner — see below.
- An editable list of required inputs the recipient will need to supply.
From there, Copy JSON puts the export on the clipboard, or Save .proflow… writes it to a file you pick.
Secret stripping
Section titled “Secret stripping”Resolved secret values — anything currently filled in from auth config, environments, or scripts — never leave the machine. The exported requests keep their {{variable}} placeholders exactly as written; nothing gets baked in as a literal value. Instead, every variable the flow actually needs (name, a description if one's set, and whether it's flagged secret) is listed in a requiredInputs manifest bundled with the export. Importing prompts for those values — see below.
Embedded sub-flows
Section titled “Embedded sub-flows”If the flow calls any Sub-flow nodes, every referenced child flow is embedded in the export too, transitively (a child that calls another child comes along as well), deduplicated, with its own secrets stripped the same way. The required-inputs manifest is the union of everything the whole call tree needs, minus anything a parent already supplies to a child via an input mapping — so importing one export is enough to get the entire journey working, not just the top-level flow.
Importing
Section titled “Importing”Click the import icon at the top of the FLOWS sidebar section (or Import Flow…), pick a .proflow file, and Probe validates it — a malformed file, one that isn't a .proflow, or one written by a newer schema version than this build supports shows a clear error instead of a partial import.
On a valid file, you get a review dialog listing the required inputs with a field for each. Fill them in (or map them to an existing environment), confirm, and Probe:
- Creates a new "(imported)" collection holding the embedded requests.
- Materializes any embedded sub-flows as new flows.
- Re-points every node reference — the flow's request nodes and sub-flow nodes — to the newly created ids.
- Opens the imported flow's tab.
The imported flow runs identically to the original, provided you filled in the required inputs correctly.
Create Flow from Folder or Collection
Section titled “Create Flow from Folder or Collection”If you already have a Composer folder — or a whole collection — with a logical sequence of requests in it, you don't have to rebuild it node by node. Right-click the folder (or the collection) in the sidebar and choose Create Flow from Folder / Create Flow from Collection. Probe previews the generated flow — a linear chain in the existing request order — and creates + opens it on confirm.
Each request that has a Tests script becomes a node with that script attached verbatim as a script assertion, so every pm.test(...) runs at flow time through the same Postman-compatible engine as the Composer runner — full fidelity, no lossy conversion. The generated flow also runs with a shared cookie jar, so a login node's session carries into later nodes exactly as it does in a collection run.
The same generator also appears during collection import (Postman or .pro): when Probe detects folders in the file you're importing, it offers to also create a flow from each one.