CLAY FALLBACK RECIPE

Add Potarix as the
last step in your Clay waterfall

Keep your current Clay providers. When they leave email blank or unverified, run one HTTP API action against Potarix and write the fallback result into clean output columns.

Send 25 failed rows copy recipe

FAILED ROW FLOW

Existing provider missesEmail is empty

Potarix HTTP action runsOnly on failed rows

Final Email fillsOriginal or Potarix

/ 01 - HTTP ACTION

Copy this into Clay's HTTP API action.

Use this version when the row has a known person and domain. Add the condition in Clay so it runs only when your current Email column is blank, invalid, or unverified.

Person email fallback

Method
POST

URL
https://api.potarix.com/enricher/find-email/person

Headers
Authorization: Bearer YOUR_POTARIX_API_KEY
Content-Type: application/json

Body
{
  "first_name": "{{ /First Name }}",
  "last_name": "{{ /Last Name }}",
  "domain": "{{ /Domain }}"
}

RUN CONDITION

Gate the call to failed rows.

In Clay, set the action to run only when the existing enrichment result failed. The exact column name depends on your table, but the rule should read like this:

Current Email is empty OR Email Status is not verified

Keep the Potarix result in separate columns first. Then create a final email column that prefers the original provider and falls back to Potarix only when needed.

/ 02 - EXPECTED COLUMNS

The minimum table shape agencies can reuse.

Most client waterfalls already have these fields. If a table only has company names, run Potarix website lookup first or use Clay's domain step before the email fallback.

First NameRequired for person email fallbackUse with Last Name and Domain when the row already has a person.

Last Name or Full NameRequired for person email fallbackPass first_name + last_name, or swap to full_name if that is the column you keep.

DomainRequiredUse the client table's website/domain column. Run website lookup first if you only have Company Name.

Target RoleRequired for role fallbackUse ceo, founder, sales, marketing, operations, finance, or the role your client wants.

Current EmailRecommendedGate Potarix to rows where this is empty, invalid, or not verified.

OUTPUT MAPPING

Create these Potarix columns.

Potarix Emailemail

Potarix Email Statusemail_status

Potarix Sourcesource

Potarix Cachedcached

Potarix Credits Remainingcredits_remaining

Response shape

{
  "email": "sam@acme.com",
  "email_status": "verified",
  "source": "anymailfinder",
  "cached": false,
  "credits_remaining": 4082
}

/ 03 - NO PERSON NAME

Use role fallback when the row only has a domain.

If your client table is account-first, swap the endpoint and body. Potarix returns the person name, title, LinkedIn URL, and verified email when the waterfall finds a match.

Decision-maker fallback

Method
POST

URL
https://api.potarix.com/enricher/find-email/decision-maker

Headers
Authorization: Bearer YOUR_POTARIX_API_KEY
Content-Type: application/json

Body
{
  "decision_maker_category": "{{ /Target Role }}",
  "domain": "{{ /Domain }}"
}

WHEN TO USE IT

Good fallback rows look like this.

Domain is present and normalized.
Target Role says the buyer you want, for example ceo, founder, sales, or ops.
Previous provider did not return a verified email.
Final Email uses Potarix only when the original Email is still empty.

/ 25 FAILED-ROW OFFER

Send 25 rows your current Clay waterfall missed.

We will run the fallback recipe, return the hit rate, and send back the exact column mapping to clone across client tables.

Email the 25 rows Start free

Add Potarix as thelast step in your Clay waterfall