Drop a portal export.
Get the documentation back.
Export your workflows with any of the browser tools that do it, drop the zip here, and get one written spec per workflow in the library's own format. It runs in this page: the zip is never uploaded, and nothing about your portal reaches us.
Nothing is uploaded. The work happens in this tab, and you can watch the network panel to check.
The first one, as it comes out
Five sections written for you. Four left deliberately empty.
Written from the export
The trigger and its criteria in plain English, re-enrolment, every action in run order with its real values, the branches and their conditions, every property touched, and a diagram.
Marked TO WRITE
When to use it and when not to, the known pitfalls, the test plan, the variants. No export contains them. We leave them blank rather than invent them.
Measured on 2,060 real client workflows across nine portals: a fiche with both criteria and steps comes out for 76% of them, and 92% of all actions can be named. The four empty sections are 44% of a hand-written fiche by word count, which is the honest size of the gap between a copy and a spec.
A client's automation is not ours to hold.
An agency dropping an export is handing over a client's business logic. Uploading that to get a document back is a trade nobody should accept, so we did not build it that way. There is no upload endpoint to trust, because there is no upload.
This page is also the honest version of the bigger product. The Vault keeps those copies dated, puts one back after someone breaks it, and moves them between portals. The founding list