How does authentication work in a Clay column?

One header on the HTTP API column: Authorization: Bearer . Keys are minted at app.argorant.com/profile and can be revoked any time.

Argorant + Clay

Verified contact data, as a Clay column.

Clay tables orchestrate enrichment — Argorant supplies the verified data. Add an HTTP API column with your Argorant key and every row can find a verified work email, verify an address you already have, or pull the full contact record from 626.5M B2B profiles.

Setup guide Get started free

626.5M contacts · 202 countries · verified at lookup time

Setup

Connect Clay to Argorant

No marketplace install needed: Clay's native HTTP API column speaks Argorant's REST API directly. Copy a template, paste your key, map your table columns.

Create a free Argorant account and mint an API key under app.argorant.com/profile → API keys.

In your Clay table, add an enrichment column → HTTP API, and set the Authorization header to Bearer <your key>.

Paste one of the ready-made templates from the Clay guide below — find email, verify email, or reveal contact — and map row columns into the request fields.

Run the column. Each row returns clean JSON (email, status, phone, title, company) that downstream Clay columns can use.

Full Clay guide

Waterfalls

A verified source in your enrichment waterfall.

Clay users chain providers and keep the first good answer. Argorant slots into that waterfall as a source that verifies at lookup time — the email you get back was just checked for deliverability, not pulled from a stale dump. Use the verification status field to decide whether the waterfall continues.

Live SMTP check · founder@nordwind-sys.com

Syntax & domainpass

MX records foundpass

SMTP handshakepass

Mailbox accepts RCPTpass

Catch-all probenot catch-all

Resultvalid · deliverable

Find & reveal

Name + company in, verified contact out.

Map your table's name and company (or domain) columns into the find-email template and each row comes back with a verified work email. Need more? The reveal template returns the full record — phone, title, location, LinkedIn — for one credit per row, only on the rows you run.

POST /v1/search · 200 OK

curl https://api.argorant.com/v1/search \

-H "Authorization: Bearer ak_live_…" \

-d '{"industry":"saas",

"title":"vp sales",

"country":"DE"}'

{

"total": 8412,

"verified": 6930,

"export_url": "…/e/9f2c"

}

List building

Or skip the row-by-row and import a finished list.

When you want a whole segment rather than per-row enrichment, build a verified export in Argorant — fintech CFOs in Germany, Series-B heads of sales — download the CSV, and import it as a new Clay table. Counts and previews are free, so you can size the segment before spending a credit.

app.argorant.com/exports

DACH - Manufacturing CFOs

Leads · verified at export · skips prior exports

done

5,234 / 5,420 checked live96.6% deliverable

valid · 4,981catch-all · 253invalid removed, not billed

Download CSVPush to sequencer

Operating guide

The complete, testable workflow

Published by Argorant

Use Clay's generic HTTP API integration to call Argorant. Store the bearer key as a protected credential, map a single request, test one row, parse the response, branch on valid or no-result status, and only then scale the table. This is an HTTP integration pattern, not a native Clay catalog integration, and it can consume both Clay and Argorant units.

Support boundary

Clay HTTP request

http

Call Argorant REST endpoints using protected bearer authentication and mapped row inputs.

Argorant enrichment

rest

Use known company, domain, or person inputs for one-row enrichment where the API endpoint supports them.

Argorant source import

rest

Create and poll a bounded export outside or inside a controlled Clay workflow, then import results.

Native catalog integration

requires verification

No proven native Clay catalog integration exists; block that wording.

Roadmap boundary

requires verification

The first-party push-endpoint roadmap concerns sequencers with public APIs and does not make Clay or its generic HTTP pattern a shipped direct provider.

Run it in this order

1
Choose source or enrichment
Decide whether Clay starts with rows to enrich or needs Argorant to create the company and contact universe.
Expected: The request maps to the correct Argorant endpoint and output shape.
2
Secure and test one row
Store the key as a credential, map inputs, and run success, miss, 401, and 429 cases on one row.
Expected: Known response and error branches without table-wide cost.
3
Add run conditions
Require complete inputs, empty target fields, eligible status, and bounded row scope before calling.
Expected: No duplicate or pointless calls.
4
Scale and reconcile
Run a limited batch, compare Clay Actions/Data Credits to Argorant successful output, and inspect every reject.
Expected: Predictable cost and complete row accounting.

Confirm the audience before handoff

The matching count is visible before contact output. Check it and a masked sample before a paid export or destination push is allowed.

What this screenshot shows: The market count is visible before reveal, export, or destination handoff, which gives the operator a concrete approval boundary. Open the product guide · captured August 20, 2026

Before calling this complete

Build and capture one enrichment column and one source import in the current Clay product.
Test success, miss, 401, 429, row limit, schema change, and replay behavior.
Reconcile Clay Actions/Data Credits and Argorant credits for the same batch.

Hard boundaries

Do not say native Clay integration or catalog provider.
Do not apply the sequencer direct-push roadmap to Clay or describe a future integration as shipped.
Do not put bearer keys in visible headers, screenshots, or exported templates.
Do not run a full table before success, miss, authentication, and rate-limit branches pass.

Current source pages

Argorant Clay integration page

Reviewed 2026-08-20

Argorant Clay documentation

Reviewed 2026-08-20

Argorant API reference

Reviewed 2026-08-20

Clay HTTP API integration guide

Reviewed 2026-08-20

Clay pricing

Reviewed 2026-08-20

Coverage

626.5M

Contacts covered, and available to your Clay workflows the moment you connect.

More ways to connect

Argorant plugs into the stack you already run.

Zapier

No-code Zaps into 8,000+ apps

Claude

Native MCP connector for Claude

ChatGPT

Argorant inside ChatGPT & GPTs

Grok

Connect Grok to your lead data

Grok Build

xAI's coding CLI, wired to Argorant

Grok Bot

Always-on AI teammates, fed with data

Salesforce

Verified contacts into Salesforce

lemlist

Clean lists for lemlist sequences

PlusVibe

Verified lists for PlusVibe campaigns

Make

Visual scenarios with HTTP modules

n8n

Self-hosted workflows & AI agents

HubSpot

One-click push into your CRM

Pipedrive

Verified persons & organizations

Smartlead

Verified leads into campaigns

Instantly

Verified lists for your campaigns

Google Sheets

Any export, one click to a Sheet

CLI

npx argorant — terminal & agents

AI agents & MCP

Claude, ChatGPT & any MCP client

Customer stories

From the right contacts
to real customers.

What happened when these teams put the right contacts into their outreach.

Read the customer stories

Meetings booked in week one

“The appointments you're booking are crazy: Hugo Boss, AboutYou, Drykorn, Jack Wolfskin, all within a week.”

Christian Schmidt & Mike Klaßen

Co-Founders & Owners

Read their story

16.81%

Reply rate across the campaign

“We've gotten 16.81% in replies after working with you guys. Can only recommend you.”

Jannik Linke

Founder & CEO

Read their story

Blunaranja

€759K

Pipeline generated

“Yesterday I got confirmation for a pilot - and it was the very first appointment.”

Armin L. Rau

Founder & Managing Director

Read their story

Frequently asked
questions

Clay + Argorant

Everything about connecting Clay to verified, deliverable B2B contact data.

Still have questions? Talk to us

Not yet — there's no branded Argorant integration in Clay's catalog today. You connect using Clay's built-in HTTP API enrichment column with our copy-paste templates: same API key and endpoints, documented at argorant.com/docs/integrations/clay. If a native integration ships later, your existing key and tables keep working — nothing to redo.

One header on the HTTP API column: Authorization: Bearer <your API key>. Keys are minted at app.argorant.com/profile and can be revoked any time.

Counts and redacted previews are free. Finding or verifying an email and revealing a full contact consume workspace credits — the same metering as the web app, REST API, CLI, and MCP server. Clay only runs the rows you tell it to, so you control spend per table.

Yes — that's the recommended pattern. Put the Argorant find-email template in your waterfall and branch on the returned verification status: keep verified addresses, let the waterfall continue otherwise.

First name, last name, and a company domain give the best hit rate; name plus company name also works. The reveal template accepts the same inputs and returns the full contact record including phone and LinkedIn.

Connect Clay in about a minute.

Build a personalized 25-lead sample. Counts and searches are always free.

Get started Connect your AI agent

Argorant + Clay

Verified contact data, as a Clay column.

Setup guide Get started free

626.5M contacts · 202 countries · verified at lookup time

Setup

Connect Clay to Argorant

No marketplace install needed: Clay's native HTTP API column speaks Argorant's REST API directly. Copy a template, paste your key, map your table columns.

Create a free Argorant account and mint an API key under app.argorant.com/profile → API keys.

In your Clay table, add an enrichment column → HTTP API, and set the Authorization header to Bearer <your key>.

Paste one of the ready-made templates from the Clay guide below — find email, verify email, or reveal contact — and map row columns into the request fields.

Run the column. Each row returns clean JSON (email, status, phone, title, company) that downstream Clay columns can use.

Full Clay guide

Waterfalls

A verified source in your enrichment waterfall.

Live SMTP check · founder@nordwind-sys.com

Syntax & domainpass

MX records foundpass

SMTP handshakepass

Mailbox accepts RCPTpass

Catch-all probenot catch-all

Resultvalid · deliverable

Find & reveal

Name + company in, verified contact out.

POST /v1/search · 200 OK

curl https://api.argorant.com/v1/search \

-H "Authorization: Bearer ak_live_…" \

-d '{"industry":"saas",

"title":"vp sales",

"country":"DE"}'

{

"total": 8412,

"verified": 6930,

"export_url": "…/e/9f2c"

}

List building

Or skip the row-by-row and import a finished list.

app.argorant.com/exports

DACH - Manufacturing CFOs

Leads · verified at export · skips prior exports

done

5,234 / 5,420 checked live96.6% deliverable

valid · 4,981catch-all · 253invalid removed, not billed

Download CSVPush to sequencer

Operating guide

The complete, testable workflow

Published by Argorant

Support boundary

Clay HTTP request

http

Call Argorant REST endpoints using protected bearer authentication and mapped row inputs.

Argorant enrichment

rest

Use known company, domain, or person inputs for one-row enrichment where the API endpoint supports them.

Argorant source import

rest

Create and poll a bounded export outside or inside a controlled Clay workflow, then import results.

Native catalog integration

requires verification

No proven native Clay catalog integration exists; block that wording.

Roadmap boundary

requires verification

The first-party push-endpoint roadmap concerns sequencers with public APIs and does not make Clay or its generic HTTP pattern a shipped direct provider.

Run it in this order

1
Choose source or enrichment
Decide whether Clay starts with rows to enrich or needs Argorant to create the company and contact universe.
Expected: The request maps to the correct Argorant endpoint and output shape.
2
Secure and test one row
Store the key as a credential, map inputs, and run success, miss, 401, and 429 cases on one row.
Expected: Known response and error branches without table-wide cost.
3
Add run conditions
Require complete inputs, empty target fields, eligible status, and bounded row scope before calling.
Expected: No duplicate or pointless calls.
4
Scale and reconcile
Run a limited batch, compare Clay Actions/Data Credits to Argorant successful output, and inspect every reject.
Expected: Predictable cost and complete row accounting.

Confirm the audience before handoff

The matching count is visible before contact output. Check it and a masked sample before a paid export or destination push is allowed.

Before calling this complete

Build and capture one enrichment column and one source import in the current Clay product.
Test success, miss, 401, 429, row limit, schema change, and replay behavior.
Reconcile Clay Actions/Data Credits and Argorant credits for the same batch.

Hard boundaries

Do not say native Clay integration or catalog provider.
Do not apply the sequencer direct-push roadmap to Clay or describe a future integration as shipped.
Do not put bearer keys in visible headers, screenshots, or exported templates.
Do not run a full table before success, miss, authentication, and rate-limit branches pass.