All workflows

GTM workflow guide

Clay catch-all recovery workflow

Workflow guide for routing risky catch-all rows from a Clay table into opt-in Premium Catch-All Recovery on a completed CSV validation job, without changing canonical validation status.

Auth

X-API-Key header

Setup

moderate · Depends on Clay table and HTTP action setup

Workflow type

workflow

Create an API keyRead API docs

Workflow steps

  • Build or import the lead table in Clay
  • Run the list through a CSV validation job
  • Trigger opt-in recovery for risky catch-all rows on the completed job
  • Map recovery confidence and recommended action back to Clay columns
  • Route rows by recovery fields while canonical status stays unchanged

Why this workflow fits

  • Keeps recovery output separate from canonical validation status
  • Uses job-scoped public recovery endpoints with X-API-Key authentication
  • Non-intrusive scoring that does not send verification emails

Setup sequence

Validate the list first

Run the Clay-sourced list through the CSV validation job flow and wait for the job to complete. Recovery operates on a completed validation job, not on raw emails.

Request opt-in recovery for the job

Trigger recovery for the completed job's risky catch-all rows with X-API-Key authentication.

curl -X POST https://api.gtmapis.com/v1/csv/jobs/batch_123/recover-catchalls \
  -H 'X-API-Key: $GTMAPIS_API_KEY'

Fetch recovery results

Read recovery output from the job recovery endpoint and map recovery confidence and recommended action back onto the matching Clay rows as separate columns.

curl https://api.gtmapis.com/v1/csv/jobs/batch_123/recovery \
  -H 'X-API-Key: $GTMAPIS_API_KEY'

Route rows by recovery fields

Filter or branch the Clay table on recovery confidence and recommended action while keeping the canonical risky status column unchanged.

Rescue risky catch-all rows before send

Decide which catch-all rows deserve cautious sending or manual review instead of discarding the whole segment.

Recovery-aware list segmentation

Split a Clay table into send, review, and suppress segments using recovery confidence and recommended action fields.

Common questions

Does recovery change a risky row to valid?

No. Recovery adds confidence and recommended action fields; the canonical risky status is unchanged.

Is this an official Clay app listing?

No. This page describes an HTTP/API workflow pattern inside Clay, not an official marketplace integration.

Does recovery send verification emails?

No. Premium Catch-All Recovery is non-intrusive and must not send verification emails.