Skip to main content

Flows: values, automation and versions

5 minute read

How a flow holds the values to read, the file and the destination, and how to change it safely.

What a flow holds

A flow is one setup for one kind of document. Its page has four steps, with Documents and History beside them:

  • Arrives. How documents reach the flow: upload, the flow's email address, pickups from a mailbox or server, and the API. See Ways to send documents in. A document you add without choosing a flow is put with the flow whose documents it is like. If none fits, or we are not sure, it waits for you in Documents.
  • We read. The values and tables to read from every document, each with a name and an example. More on a value holds its Required tick, its type and its meaning.
  • You check. Whether documents wait for you or are sent on their own.
  • We send. The files we make, each sent to a destination. A file can have a Send when condition, so one flow can send different documents to different places. See Files we make.

Documents lists the newest documents in this flow. History lists its versions.

What we read

The first time, drop one document like the ones you will receive on We read, or press Choose a file there. We read it, and We read lists the values we found. Untick what you do not need and rename values. Under More, tick Required for values that must always be there: we mark the value when it is missing from a document. Then press Looks right, next while you set up a new flow, or Keep these values on the flow's We read step.

Every later document is read into these values. Once the setup is saved, changes to these values wait until you use them. If the latest document has something extra, it appears under New values we noticed, with Add beside it.

Automation

Each flow is set to one of two modes, on its You check step. A change applies to new documents straight away:

  • Review before delivery. Every document waits for you. This is the default.
  • Automatic delivery. A document is sent as soon as it has been read. Failed checks do not stop it, with two exceptions that always wait: a repeated document number, and the first document from a new email address. See Checks.

The flow shows how many recent documents were sent without a correction. Use it to decide when to switch to automatic. Only a workspace admin can change the mode.

Versions

Each time you use your changes, the flow keeps its values and files as a numbered version. New documents are read and sent with the setup in use, so you can change a flow without breaking what is running.

Changes to the values and the files save as you make them. While a change is not in use yet, a bar under each step says so. Before the first save of the setup, changes are in use straight away and the bar offers only Save this setup. After that, you can Use these changes or Undo my changes. The flow's name, its mode and how documents arrive do not wait: they change at once.

History lists every version with the date and who put it in use. You can restore an earlier one. Restoring puts it back into your changes. It is in use only after you press Use these changes. Putting changes in use and restoring are for workspace admins. See Use changes and restore earlier versions.

The Advanced view

Each file you built yourself has an Open in Advanced link. It opens a wider workbench for finer control, and it needs a larger screen. Most flows never need it.

How many flows

The number of flows depends on your plan. See Pricing.