QA Check
Score a text from 0 to 1 with an AI model for content, quality, consistency or safety, and get an approved or rejected decision with a short reason.
The QA Check node asks an AI model to score a text from 0.0 to 1.0 against one check type, such as quality or safety. The text is approved when the score reaches your threshold, and the model explains its decision in one short reason. Use QA Check as an automatic quality gate, for example to catch a weak script or caption before anyone publishes it.
When to use it
- Check that a generated script is complete and well structured before you turn it into audio or video.
- Check captions for clarity and grammar before they are posted.
- Screen a text for harmful or offensive content before it goes public.
- Compare the scores of several drafts to see which prompt writes better text.
Quick start
Add the node
Press Tab on the canvas and choose Automate › Logic & Data › QA Check.
Connect the text
Wire the text to check into the Input input, for example from a Prompt node, a Generate Script node or a Text node.
Choose the check
Open the settings panel. Choose a Check Type and a Threshold, and a different AI Model if you want one.
Run it
The node shows the score, the decision and the model's reason. The reason also leaves through the Approved or the Rejected output, whichever matches the decision.
Inputs and outputs
| Input or output | Accepts or sends | What it does |
|---|---|---|
| Input | Text | The text to evaluate. Required. |
| Approved | Text | The model's reason, when the score is at or above the threshold. |
| Rejected | Text | The model's reason, when the score is below the threshold. |
On each run, only one of the two outputs carries a value. Both carry the reason, not the checked text. To use the checked text in later steps, connect those steps to the node that wrote it.
Check types
| Check Type | What the model evaluates |
|---|---|
| Content (default) | Completeness, coherence and structure. |
| Quality | Clarity, grammar and professionalism. |
| Consistency | Internal consistency: no contradictions and no logical errors. |
| Safety | Whether the text is safe and appropriate, with no harmful or offensive material. |
Settings
| Setting | What it does |
|---|---|
| AI Model | The model that scores the text. The default is Gemini 3.6 Flash. |
| Reasoning Effort | How much the model reasons before it answers, on models that support it. Very high and Max may bill one tier up. |
| Advanced mode | Available on Gemini models only. It unlocks Temperature, Max Tokens and the full reasoning range, which appear once it is on. It costs one credit tier more, and the price on the node updates at once. On other models the switch is disabled and says why. |
| Check Type | What to evaluate: Content, Quality, Consistency or Safety. |
| Threshold | The lowest score that counts as approved, from 0 to 1. The default is 0.7. |
Credits
QA Check is billed like the other AI text nodes: the price follows the tier of the model you choose. A Reasoning Effort of Very high or Max, or Advanced mode, can move the check one tier higher. The node shows the price for your current settings before you run it. See Credits.
Tips
- Match the check to the risk. Use Safety for anything that is published automatically, and Content or Quality for drafts.
- Tune the threshold on real examples. Run the check on a few texts you already judged yourself, then raise or lower Threshold until the decisions match yours.
- Pick between drafts instead. To keep the best of several texts rather than score one, use Choose Best with AI picks the best.
- Check images with Image Critic. QA Check reads text only. For pictures, use Image Critic.
Frequently asked questions
Related
Prompt
Image Critic
Choose Best
Router
Credits
Last updated on
Extract Field
Pull one field or a nested path, such as title or authorMeta.name, out of JSON data, and send it on as text, as a list to run once per item, or as JSON.
JSON Process
JSON Process is a legacy node that filters and reshapes JSON. It is no longer in the node picker, but saved workflows keep running. Use Extract Field instead.