Loading docs
Use QFlow Studio components, gates, and reusable workflow blueprints without leaving the build context.
The component library is where users add gates, reusable workflow pieces, and task-specific components to the current record.
Use components when a workflow should remain visual and explainable rather than hidden inside custom source files.
Use QFlow Studio components, gates, and reusable workflow blueprints without leaving the build context.
This page belongs to the Build Workflows section and should be read with the related pages listed at the end.
Use screenshots and notes to explain product behavior without exposing private credentials, admin state, or customer data.

A new user may not remember every gate label. Teach them to search for the operation they want and inspect the component before adding it.
After adding a component, return to the canvas and confirm that the block sits in the expected place in the workflow.
For repeatable work, start from library blueprints rather than rebuilding a workflow from memory.
Blueprints are especially useful for lessons, demos, provider readiness tests, and onboarding new team members.

Start from reusable workflow blueprints, starter circuits, and patterns before building a workflow from scratch.
Use the QFlow Studio canvas to understand visual workflow blocks, connections, workflow switching, and responsive behavior.
Follow the first QFlow Studio workflow from canvas setup through provider selection, run feedback, and run history.