Loading docs
Start Here
Create and Run Your First Workflow
Follow the first QFlow Studio workflow from canvas setup through provider selection, run feedback, and run history.
Updated May 26, 2026QFlow StudioNormal userTeacher
Use this page when you want the shortest path through the product. You will create or open a workflow, inspect the canvas, review generated code, choose provider context, run the workflow, and return to history.
The goal is not to learn every feature. The goal is to understand the product loop well enough to make your first safe, reviewable run.
Purpose
Follow the first QFlow Studio workflow from canvas setup through provider selection, run feedback, and run history.
Where it fits
This page belongs to the Start Here 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.
Step-by-step path
01
Open the Studio canvas
Sign in and open the default workflow. Confirm that blocks are visible, the top tabs are available, and the run action remains near the workflow record.
Result: A workflow ready for inspection.
02
Inspect the generated source
Open the Code tab and review the source generated from the visual workflow. Use this as the bridge between visual design and SDK-level review.
Result: Qiskit, Cirq, or OpenQASM context that matches the canvas.
03
Select provider context
Open provider selection from the Studio surface. Pick the provider context without exposing credentials in a shared screenshot or reviewer artifact.
Result: A route decision with provider fit visible.
04
Run and return to history
Run the workflow, wait for feedback, then open run history to confirm the result is attached to the workflow record.
Result: A saved execution record.
Provider selection stays inside the workflow
Provider choice is part of the operating record. Treat it as a decision attached to a workflow, not as a separate setup task in another console.
Before a hardware run, confirm provider name, queue posture, and route fit. If credentials are missing, fix the private provider setup rather than sharing tokens in comments or screenshots.
Provider selected
Route fit checked
No token shown
Run action still visible
Run feedback should be boring and explicit
After you run, look for direct feedback in the Studio. A useful run state tells the user what happened and where the resulting evidence will live.
When documenting a workflow for a team, include what was run, which route was used, and where the result can be reviewed later.
Run history is the proof trail
Run history is where repeated work becomes operational. It gives teams a place to compare status, return to evidence, and avoid rerunning the same question blindly.
Use history when writing lab notes, preparing review, or proving that a workflow was executed under a specific provider context.
Next pages
Generated code
Review generated Qiskit, Cirq, and OpenQASM output beside the visual workflow before routing or exporting.
Providers
Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.
Results & evidence
Use run history, evidence packets, certificates, and approved shares without exposing private workspace data.