Validate first
Run standard Email Validation and identify risky catch-all outcomes before considering recovery.
GTM workflow guide
Workflow guide for routing risky catch-all validation results into opt-in Premium Catch-All Recovery logic without changing the canonical validation status.
Auth
X-API-Key header
Setup
moderate · Depends on n8n workflow design
Workflow type
workflow
Run standard Email Validation and identify risky catch-all outcomes before considering recovery.
Send only opt-in recovery candidates to the recovery workflow and keep recovery fields separate from canonical status.
Store recovery confidence and recommended action without changing the validation result status.
Separate risky catch-all records from high-value validation results before campaign decisions.
Use recovery recommendation fields to decide which catch-all records deserve review or cautious routing.
No. Recovery fields do not change the canonical validation status.
No. This page describes an HTTP/API workflow pattern, not an official n8n listing.