Loading docs
Operate
Workflow Library and Blueprints
Start from reusable workflow blueprints, starter circuits, and patterns before building a workflow from scratch.
Updated May 26, 2026QFlow StudioNormal userTeacher
Blueprints reduce setup time and improve consistency. Use them when a team repeats a known experiment, lesson, provider check, or demo path.
A good blueprint should be understandable before it is executed. Open it, inspect the blocks, review generated code, and then adapt it to your context.
Purpose
Start from reusable workflow blueprints, starter circuits, and patterns before building a workflow from scratch.
Where it fits
This page belongs to the Operate section and should be read with the related pages listed at the end.
Review boundary
Use screenshots and notes to explain product behavior without exposing private credentials, admin state, or customer data.
When to start from a blueprint
Use a blueprint when the workflow shape is known but details like provider, qubits, or owner need to change.
Avoid starting from blank canvas for routine onboarding, academy lessons, or provider readiness checks.
Known workflow shape
Repeatable lesson
Provider check
Demo-ready path
Next pages
Component library
Use QFlow Studio components, gates, and reusable workflow blueprints without leaving the build context.
Canvas
Use the QFlow Studio canvas to understand visual workflow blocks, connections, workflow switching, and responsive behavior.
Quickstart
Follow the first QFlow Studio workflow from canvas setup through provider selection, run feedback, and run history.