Foldr Flow · packaging

Bundle a workflow. Ship it anywhere.

A Foldr Flow is one file: shares, custom fields, Captur templates, scheduled mashlets. Hand it to another Foldr and it just runs.

Distribution scenario 1

Across your own estate

Build the workflow once on a staging Foldr. Export. Import on every site, school, region, or office. Conflicts are surfaced before anything is overwritten.

Distribution scenario 2

Out to MSP clients

Service providers package up a managed offering, the connectors, the captures, the automations, and roll it out to every client in one go.

The engine inside a Flow

A Flow packages a workflow. Build it whichever way fits.

MaSH, Make Stuff Happen, is the engine underneath Foldr automations. Schedule jobs, classify documents, route data, run reconciliations. Flows bundle the result with the shares, custom fields and Captur templates it depends on, so the whole thing travels together.

Mashup · Visual

Build it as visual blocks

Drag blocks together to construct the workflow. Every block is a real MaSH instruction; switch to the script view at any time and the code is right there.

MaSH · Code

Or write it as plain-text script

Plain-text scripts checked into source control. Reviewed in pull requests, diffed in git. Engineers and IT admins read and edit the same file.

Grace · Verbal

Or just ask Grace

Describe what you want in plain English and the AI assistant writes the workflow for you. Inspect the result in Mashup or as MaSH before anything runs in earnest.

Schedule

Run on a timer or a trigger

Cron, file-arrived, share-changed, Captur-completed. The engine runs the same on Foldr SaaS or a self-hosted appliance; the workers come with the platform.

Travel

One file, any Foldr

Export the Flow on one Foldr, import on another, and the whole thing runs. Conflicts are surfaced before anything is overwritten.

Bring it together. On your terms.

Start a 30-day trial, no credit card. Or talk to us about self-hosting the appliance.