QA Checklist Node

The QA Checklist node runs a set of quality checks against the incoming data and routes records to one of two outputs — Passed or Failed — based on the resulting health score. It integrates with the platform's QA Checklist feature and computes a health score the same way the governance layer does.

When to Use

Use QA Checklist when your automation involves campaign setup or content production steps that need systematic quality checks — naming-convention validation, UTM-parameter review, creative asset checks, and similar. Branch downstream nodes off the Passed and Failed handles to handle each outcome.

Configuration

One check source is required: checkItems, templateId, or systemTemplateName. They are resolved in that priority order.

Example

Require a campaign-compliance check before export:

systemTemplateName: Meta Campaign Compliance
minHealthScore: 100
blockOnFailure: true

When the checklist passes (health score ≥ 100), records exit through Passed. When blockOnFailure is false, failing records exit through Failed instead of stopping the run.

Notes

• The health score is computed over automated checks only — items awaiting manual review (pending_manual) are excluded from the score.
• With blockOnFailure: true, a failing checklist stops the automation run with an error (health score X% < required Y%); with blockOnFailure: false, the run continues down the Failed branch.
• Checklist templates are created and managed in the QA Checklists feature; reference them by templateId. Use systemTemplateName for the built-in quick-start templates.
• fieldMappings lets a checklist that expects, say, a campaign_name field read it from a differently named input column.