Foldr Flows - packaging

Go with the (work)flow. Plan it, then apply it.

A Foldr Flow is one file that carries your configuration: shares, custom fields, forms, Sign templates, Captur templates, saved searches, approval rules and the scripts that tie them together, with their schedules and triggers. Import it on another Foldr and you’ll see exactly what will be created, renamed or skipped before anything is written. It carries your setup, not your secrets or your files, so you’ll reconnect each share’s account on the other side.

invoice-intake.foldr-flow Ready to import
In this bundle
  • Storage connectors 3 shares
  • Custom fields 8
  • Captur templates 2
  • Scheduled mashlets 4
1 conflict surfaced before import
Distribution scenario 1

Across your own estate

Build the workflow once on a staging Foldr. Export. Import on every site, school, region, or office. The import shows you its plan first, and conflicts are surfaced before anything is overwritten.

Distribution scenario 2

Out to MSP clients

Service providers build the managed offering once, export it, and import it into each client’s Foldr, previewing the plan each time. Import is one tenant at a time, so each client is a deliberate step.

Moving house

From an appliance to Foldr Cloud, or the other way round.

A Flow is how your setup moves when you do. Export from the appliance, import into Foldr Cloud, and read the plan before you apply it. A few honest limits: accounts for your storage aren’t in the file, so you point each share at its own credentials; webhooks and user scripts don’t travel; users, groups and branding are set up again on the other side; and anything the new Foldr isn’t licensed for (Captur, Sign, Forms, Reviews) is left out and listed rather than run. Your files stay where they are, so there’s nothing to copy unless you kept them in Foldr Storage.

The engine inside a Flow

Build it as blocks, as code, or just by asking.

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

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

Or write it as plain-text script

Plain-text scripts with a version history and a diff built in, and a Flow bundle you can keep in git if you like. Engineers and IT admins read and edit the same file.

Grace

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 same scripts run on Foldr Cloud and on an appliance. Cloud keeps sensible limits on run time, mail volume and which hosts a script can call; on an appliance you set those yourself.

Travel

One file, plan first

Export the Flow on one Foldr, import on another, and the plan tells you what will be created, renamed or skipped before anything is written. Conflicts are surfaced before anything is overwritten.

Curious whether Foldr would fit?

Try it free for 30 days, no credit card. Or get in touch about self-hosting.