All workflows

GTM workflow guide

n8n catch-all recovery workflow

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

Workflow steps

  • Validate emails through the public Email Validation workflow
  • Detect risky catch-all outcomes
  • Send opt-in records to recovery scoring
  • Store recovery confidence and recommended action
  • Keep canonical status unchanged

Why this workflow fits

  • Keeps catch-all detection separate from recovery-specific fields
  • Avoids implying mailbox existence certainty
  • Supports automation without sending verification emails

Setup sequence

Validate first

Run standard Email Validation and identify risky catch-all outcomes before considering recovery.

Branch risky catch-all records

Send only opt-in recovery candidates to the recovery workflow and keep recovery fields separate from canonical status.

Persist recovery-specific fields

Store recovery confidence and recommended action without changing the validation result status.

Catch-all routing

Separate risky catch-all records from high-value validation results before campaign decisions.

Manual review queue

Use recovery recommendation fields to decide which catch-all records deserve review or cautious routing.

Common questions

Does recovery change risky to valid?

No. Recovery fields do not change the canonical validation status.

Does this require an official n8n node?

No. This page describes an HTTP/API workflow pattern, not an official n8n listing.