Build and run workflows at scale
  • *Pricing TBA
  • πŸ‘©β€πŸ’» 1 Administrator License (+$ per additional licence)
  • πŸ§‘ 10 Authenticated User Licenses (+$ per additional license)
  • πŸš€ 1000 workflow sessions per month (+$ per additional sessions)
  • πŸ”€ Unlimited published workflows
  • πŸ“‘ Unlimited draft workflows
  • πŸ’Ύ 10GB file storage and upload
  • πŸ’ͺ Premium components including workflow data, API request and response and more

Pricing Terminology


Administrator/Editor License πŸ‘©β€πŸ’»

An Administrator or Editor license allows you to create a user that can build, edit and run workflows.

Whats the difference between an Editor and an Administrator? Both can build and edit workflows, but Administrator users also have access to additional account and user management features such as the ability to invite users, change user permissions and change organisation settings.

Authenticated User License πŸ§‘

An Authenticated User license allows you to create a user who can run, start or use workflows. They cannot build or edit workflows. Think of them as end-users of a workflow.

Authenticated User licenses are required if you have a workflow that can only be run by certain users within your organisation. So if you have a workflow which you only want employees in your company to be able to access and run, all of your employees will need to be Authenticated Users.Β 

If your workflow is open to the public (i.e. it can be run and started by anyone) then you don’t need to be an Authenticated User to run or start it.

Draft and Published Workflows 🚦

A draft workflow is a workflow that is not active. It is essentially non-functional as it cannot be run or started.

A published workflow is a workflow which is live and functional. It can be run and started.

Workflow sessions πŸ”„

Every time a workflow is run, it counts as one session. So if you run your workflow from start to finish 10 times, that is 10 sessions. A subscription comes with a number of workflow sessions per month. This number resets at the start of the monthly billing cycle.

File Uploads and Storage πŸ’Ύ

When a workflow is run, it may store files uploaded during its course (e.g. a file uploaded to a form) or it may generate files such as documents. These are stored inside the platform where you can access them via link or download them. Each plan comes with a limit to how many files can be stored in Workflow86.