Workflows: the stages and tasks work follows after it prints
Workflows in SimplyPrint lets you describe what happens after a print comes off the printer: the stages a print, an item or an order goes through, the tasks a person does at each stage, and the checks that decide when it may move on. This guide covers who Workflows is for, how its parts fit together, where you find it in the panel and which plans include it.
When a printer says a print is done, the work usually isn't. Supports come off, every piece gets checked, a student is told their print is ready to collect, an order is packed and shipped. Until now SimplyPrint stopped at "done". Workflows covers what comes after.
You find the board at Workflows in the sidebar (/panel/workflows), and you set workflows up in Settings > Workflows (/panel/settings/workflows).

Table of contents
- Who is this for?
- What can you do with it?
- How it all fits together
- The building blocks
- Where you see workflows in the panel
- Plans and availability
- What workflows do not do
Who is this for?
Workflows is built for places where more than one person touches a print after it comes off the bed:
- Print farms and shops that finish, inspect, pack and ship parts, and want every item and order to show where it is.
- Schools and makerspaces where a teacher or technician finishes prints and the student who asked for one should hear when it is ready to collect.
- Any team that has a checklist on paper next to the printers, such as "remove supports, inspect, bag, label".
If nobody does anything to a print after it finishes, you don't need a workflow. With no workflow attached, nothing changes: a print is done when it is printed, exactly as before.
What can you do with it?
- Describe what happens after printing, once. A workflow is a list of stages, such as Printing, Post-processing and Ready for collection, each with the tasks a person does there.
- Only ask for work that is needed. A task like "Remove supports" can be set to appear only when the slice used supports. When SimplyPrint can't tell, the task is still shown and marked as possibly not needed, with the reason one click away.
- Check every piece, not just the batch. A task can be done once per piece, so three pieces need three ticks.
- Let work move on by itself. Stages can be entered when the print starts, when it finishes or when the bed is cleared, and a stage can move on as soon as its checks pass.
- Hold work until it is really ready. An order doesn't reach Ready to pack until every item is accepted and every item's own workflow is finished.
- Tell the person who asked. The ready-made School pickup workflow emails whoever asked for the print when it is ready to collect.
- See everything in flight. The Workflows board shows every running workflow in columns, with blocked work at the top.
How it all fits together
- You add a ready-made workflow or build your own in Settings > Workflows.
- You publish it. Publishing makes a numbered revision. Work that is already running keeps the revision it started on.
- You add a rule that says when it is used: for everything in the account, for anything with a label, or for one product.
- When something it covers starts, such as a print job or a Shop item, a run of that workflow starts for it. A run is that one thing's copy of the workflow, with its own tasks and history.
- People work through the run on the board or on the run's own page, ticking tasks and moving it to the next stage.
- When the run reaches a stage marked as finishing the job, it is done and leaves the board.
The building blocks
Stages
A stage is somewhere work sits, such as "Post-processing". Each stage can say what moves work into it automatically, what it does on entry (for example, email the requester), and what must be true before work may enter or leave it.
See: How a workflow works: stages, tasks, conditions and checks
Tasks
A task is something a person does at a stage, such as "Inspect". Tasks can be required or optional, done once or once per piece, ask for a note, and be limited to one user group. Reusable tasks live in the task library, so you write the instructions once.
See: Building, editing and publishing a workflow
Rules
Rules decide which workflow a print, item or order follows. The most specific rule wins: a rule on a product beats the account default. Rules can also add extra tasks, such as "Hand-painted adds Prime, Paint and Dry".
See: Workflow rules: choosing which workflow applies, by account, label or product
Runs and the board
Every piece of work following a workflow is a run. The board shows them all; clicking a card opens its stages and tasks.
See: Working through a workflow: ticking tasks, notes, waiving, blocking and moving on
Where you see workflows in the panel
- Workflows in the sidebar: the board of everything running.
- Settings > Workflows: your workflows, their rules and the ready-made ones. You need the Manage workflows permission to see this page.
- A run's own page,
/panel/workflow/<run>: what a link in an email opens, and what the board opens on a phone. - In the Shop: an order's Production tab, the Work list and each item's page in the Shop show the workflow the order or item follows.
See: Workflows in the Shop: order and item workflows, accepted pieces and moving on by itself
Plans and availability
What | Plans |
|---|---|
Workflows (board, settings, runs) | Print Farm, School, Enterprise |
Shop order and item workflows | Print Farm, Enterprise (the Shop is not part of School) |
While Workflows is in its pilot, a plan alone doesn't turn it on. Accounts in the pilot see it; other accounts see nothing of it yet.
What workflows do not do
- The board is read-only. You can't drag a card to another column. A card opens its run, where moving on asks for confirmation when the next stage does something outside the workflow, such as adding work to the print queue.
- Photo evidence isn't available yet. A task can ask for a note; a task can't yet ask for a photo.
- Scanning a tray to open its work isn't built yet. Open the work from the board, the Shop or the link in an email.
- Workflow emails go to SimplyPrint users only, such as the person who asked for the print. They are not sent to Shop buyers.
- Automatic stage actions can't be added in the editor. Emails and adding to the print queue come with the ready-made workflows. The editor shows them and keeps them when you edit.
Related articles
Setting up workflows
- How a workflow works: stages, tasks, conditions and checks
- Ready-made workflows: Basic post-processing, School pickup, Item finishing and the order workflows
- Building, editing and publishing a workflow
- Workflow rules: choosing which workflow applies, by account, label or product
Day to day
- The Workflows board: see every print, item and order in its stage
- Working through a workflow: ticking tasks, notes, waiving, blocking and moving on
- Workflow permissions, group-only steps and the activity history
Workflows and the Shop
- Workflows in the Shop: order and item workflows, accepted pieces and moving on by itself
- The Shop: run your 3D printing orders from store to shipped
- Shop production work: the Work page, clearing plates, trays and finishing steps
Printing and teams
- The print queue: manage, schedule and automate your prints
- Print farm workflows: running a farm with the print queue, AutoPrint and automation
- School and makerspace workflows: from teacher-led to student-led printing
- User groups and permissions: what each one controls
Updated on: 06/11/2026
Thank you!