A Workflow is a sequence of Jobs executed within sessions to achieve a desired outcome — like reading a balance, submitting a payment account, or confirming a payment. Although a Workflow can be as simple as a single Job, this section is especially useful for building more complex, multi-Job sequences. You can imagine a workflow like a conveyor belt:
  • The Connection puts the box on the conveyor
  • The Session is the moving belt
  • Each Job is a workstation along the belt, usually automated by a robot
  • Interactions are checkpoints requiring specific inputs to continue (e.g., amount to pay)
  • The Store is where the box is placed for safekeeping after all Jobs are complete

​
More on Interactions

An Interaction is a necessary input required before a Job can run successfully. These are not Jobs themselves but are tied to Jobs and essential to their execution. They can be:
  • System-triggered – e.g., two-factor authentication, session timeout
  • User-driven – e.g., selecting an account, approving an amount

​
How It Works

At the start, the user puts raw materials into a box — most commonly, credentials for connecting to a data source. The box travels along the conveyor belt (Session), stopping at each checkpoint or workstation:
  • At a workstation, a robot (API) may modify the contents — for example, adding an access token
  • At a checkpoint, a person (user) may be required to provide input — such as selecting an account or entering a payment amount (interaction)
  • Once that step is complete, the box continues along the belt
The conveyor is linear — the box moves step by step and cannot be at two workstations at once. That’s why the order of Jobs matters. Fortunately, the belt is flexible: it can be as long as needed, with any number of supported workstations arranged in any sequence, including repeats. This model supports powerful and adaptable workflows while keeping the structure simple and predictable.