Does Superkabe charge for leads Clay already validated?

Superkabe runs its own validation pipeline (syntax, MX, disposable, catch-all, optional MillionVerifier) because Clay's enrichment does not include deliverability-grade validation. Validation consumes credits from your Superkabe plan (Starter: 10K/mo, Growth: 60K/mo, Scale: 100K/mo).

Can a single Clay webhook route to multiple campaigns?

Yes. Superkabe's routing rules match each incoming lead against priority-ordered (persona + min_score) rules, with a wildcard catch-all. One Clay table can feed many campaigns simultaneously.

What happens to leads Clay sends that Superkabe marks invalid?

They are held with a rejection reason code (no MX, disposable, catch-all, syntax error, SMTP unreachable). You can view them in the Lead Control Plane and optionally re-process once the domain recovers or the pattern changes.

Complete Guide: Clay to Sender Platform via Superkabe

End-to-end walkthrough from lead enrichment to campaign delivery

What This Guide Covers

This guide covers the complete journey of a lead from Clay enrichment through Superkabe's email validation, health gate classification, rule-based routing, and native send via your connected Google Workspace, Microsoft 365, or SMTP mailboxes. By the end, you will have a fully automated pipeline where enriched leads flow from Clay into your Superkabe campaigns with quality controls at every stage.

The Complete Flow

Every lead passes through these stages before being dispatched. Here is the full pipeline:

Clay — Lead Enrichment

Enriched lead data sent via HTTP webhook to Superkabe

Superkabe Webhook — Ingestion

Lead received, parsed, and deduplicated against existing records

Email Validation

Syntax check, MX record lookup, disposable domain detection, catch-all detection, MillionVerifier API

Health Gate — Classification

Lead scored and classified as GREEN, YELLOW, or RED

RED — Blocked

Invalid, disposable, or high-risk emails stopped here. Never reaches a sender platform.

GREEN / YELLOW — Proceed

Validated leads continue to the routing engine.

Routing Engine

Match lead to a campaign based on persona, min score, and rule priority

Capacity Check

Verify target campaign has available capacity and active mailboxes

Send via your connected Superkabe mailbox (Google / Microsoft / SMTP) — passes through SMTP transcript capture, DSN parsing, DNSBL + Postmaster reputation checks before leaving

Lead marked ACTIVE — in campaign and ready to send

Prerequisites

Before you begin, make sure every item below is in place:

1Active Superkabe account (Sign up here)
2Clay account with enriched lead data (email, name, company, job title)
3At least one sending mailbox connected to Superkabe — Google Workspace, Microsoft 365, or SMTP (Dashboard → Sequencer → Accounts)
4At least one campaign created in Superkabe with a sequence + the connected mailboxes attached
5At least one routing rule configured in Superkabe (Configuration guide)

Step 1 — Connect Your Mailboxes

Superkabe sends from your own infrastructure. Connect at least one mailbox before creating a campaign.

1. Open Dashboard → Sequencer → Accounts
2. Click Connect and pick a provider:
- – Google Workspace — OAuth flow, no credentials stored
- – Microsoft 365 — OAuth flow, no credentials stored
- – SMTP — paste host, port, username, password (encrypted at rest)
3. Repeat for as many mailboxes as you want — there's no per-tier mailbox limit

View the full getting-started guide →

Step 2 — Create a Campaign in Superkabe

1. Open Dashboard → Campaigns → New campaign
2. Configure the sequence (steps + variants), schedule windows, and stop rules
3. Attach the mailboxes you connected in Step 1
4. Save the campaign — it will appear in the routing-rule target dropdown for Step 3

Step 3 — Set Up Routing Rules

Routing rules tell Superkabe which campaign to assign each lead to. Rules are matched by persona and minimum lead score, and checked in priority order (lowest number first).

1. Go to Dashboard → Configuration
2. Click Create Rule
3. Fill in the rule fields:
- - Persona — exact match against the lead's persona field, or * for a catch-all rule
- - Min Score — minimum lead_score required (0-100)
- - Priority — lower number = checked first
- - Target Campaign — dropdown grouped by platform (Smartlead / Instantly / EmailBison)
4. Save the rule and repeat for each ICP segment

Example Routing Rules

Priority	Persona	Min Score	Target Campaign
1	VP Engineering	70	Enterprise Outreach
2	CTO	60	Technical Leaders
3	*	50	General Outbound

How Priority Works

Priority 1 is checked first. If a lead with persona "VP Engineering" and score 85 arrives, it matches rule 1 and is enrolled in the Enterprise Outreach campaign. The * wildcard at priority 3 catches all remaining leads that did not match a more specific rule above it.

Advanced routing configuration →

Step 4 — Configure Clay Webhook

This is where you connect Clay to Superkabe so enriched leads flow in automatically.

4a. Get Your Credentials

1. Log in to your Superkabe dashboard
2. Navigate to Settings → Clay Integration
3. Copy your Organization ID (UUID format) and the Webhook URL

4b. Add HTTP API Enrichment in Clay

1. Open your Clay table
Navigate to the table containing your enriched leads
2. Add an Enrichment Column
Click + Add Enrichment → search for "HTTP API" or "Webhook"
3. Configure the HTTP API Integration
Method:
POST
URL:
https://api.superkabe.com/api/ingest/clay
Headers:
```
Content-Type: application/json
X-Organization-ID: YOUR_ORG_ID
X-Clay-Secret: YOUR_WEBHOOK_SECRET
```
Copy the webhook secret from Dashboard → Integrations → Clay. It's a per-org token (rotated on demand) that Superkabe verifies against the request — same security model as a bearer token. Advanced: if you can compute HMAC-SHA256 in a separate Clay column, send X-Clay-Signature: <hex> instead. Either header works.
4. Map Your Fields to JSON Body
Use Clay's column references to map fields:
```
{
 "Work_Email": "{{Work Email}}",
 "First_Name": "{{First Name}}",
 "Last_Name": "{{Last Name}}",
 "Company": "{{Company}}",
 "Job_Title": "{{Job Title}}",
 "Lead_Score": {{Lead Score}}
}
```
The pattern: JSON keys use underscores (Work_Email), Clay column references inside {{ ... }} use the literal column name with spaces ({{Work Email}}). Clay's editor recommends this convention. The Superkabe Clay endpoint matches keys case-insensitively and accepts both underscored and spaced variants, so Work_Email, work email, email, and e-mail all map to the same field. See the field reference below for the full list of accepted variants. String values stay quoted; Lead_Score stays unquoted. Don't wrap the whole body in outer quotes or escape the inner quotes — Clay expects raw JSON. You do not need to specify a campaign ID; routing is handled automatically by your routing rules.
5. Test on a few rows first
Run the enrichment on 2-3 test rows before enabling "Run on all rows"

4c. Field Mapping Reference

Field	Type	Example	Required
email	String	john@company.com	Yes
persona	String	VP Engineering	Recommended
lead_score	Number	85	Recommended
firstName	String	John	Optional
lastName	String	Doe	Optional
company	String	Acme Corp	Optional

Field Flexibility

Superkabe's Clay webhook supports case-insensitive field matching. All of these work interchangeably:

- email = Email = work email
- persona = job title = title
- lead_score = score = Lead Score

HMAC Security (Optional but Recommended)

For additional security, you can enable HMAC signature verification. When enabled, Superkabe generates a signing secret that you include in your Clay webhook headers. Superkabe then validates every incoming request to confirm it came from your Clay table and was not tampered with. Configure this in Settings → Clay Integration → HMAC Signing.

What Happens When a Lead Arrives

Once Clay sends a lead to Superkabe, it passes through four stages before reaching your sender platform. Understanding each stage helps you diagnose issues and know exactly where any lead is in the pipeline.

Stage 1: Email Validation

Before anything else, Superkabe checks whether the email address is real and safe to send to. This prevents bounces from ever reaching your sender infrastructure.

Internal checks (all plans):

- Syntax validation — rejects malformed addresses (missing @, invalid characters)
- MX record lookup — confirms the recipient domain has mail servers
- Disposable domain detection — blocks throwaway email providers (mailinator.com, guerrillamail.com, etc.)
- Catch-all domain detection — flags domains that accept all addresses (higher bounce risk)

API verification (Growth/Scale plans):

- MillionVerifier — verifies risky emails against a real-time verification API for definitive deliverability status

Result: A validation score from 0-100 is assigned to the lead.

Where to see it: Leads page → click any lead → Email Validation card

Invalid and disposable emails are BLOCKED immediately. They never reach your sender platform, protecting your domain reputation.

Stage 2: Health Gate Classification

After validation, the lead receives a health classification that determines whether it proceeds to routing:

GREEN (score 80+)

Safe to send. The email passed all validation checks with high confidence. Routed normally to the matching campaign.

YELLOW (score 50-79)

Proceed with caution. The email is likely valid but has some risk factors (catch-all domain, limited verification data). Routed to campaigns with risk-aware distribution.

RED (score below 50)

Blocked. The email is invalid, disposable, or too risky. The lead is marked BLOCKED and never reaches a sender platform. This is your deliverability protection working as intended.

Where to see it: Leads page → lead detail → Health Classification badge

Stage 3: Routing

GREEN and YELLOW leads enter the routing engine. Superkabe evaluates your routing rules in priority order (lowest number first) to find the right campaign.

- Rules are checked in priority order (priority 1 before priority 2, etc.)
- The first rule where the lead's persona matches AND lead_score >= min_score wins
- The lead is assigned to that rule's target campaign
- If no rule matches, the lead stays HELD — check your Configuration page to add a matching rule

Where to see it: Leads page → lead detail → Execution Context shows the assigned campaign

Stage 4: Native Send

After routing, the lead is enrolled in the target Superkabe campaign as a CampaignLead row. The send-queue dispatcher picks it up on the next cycle and sends step 1 through one of the campaign's connected mailboxes. Every send passes through:

– Execution gate — verifies mailbox is healthy + below daily/warmup cap
– SMTP transcript capture — records the SMTP exchange for diagnostics
– DSN parsing — async bounces routed back to the bounce monitor
– State machine — pauses the mailbox immediately on bounce-rate breach

Once enrolled: lead is marked ACTIVE — it is in the campaign queue.

If enrollment fails: the lead stays HELD for automatic retry.

Where to see it: Leads page → lead status changes from HELD → ACTIVE upon successful enrollment

Monitoring After Push

Once leads are ACTIVE in campaigns, Superkabe continues to protect your sending infrastructure:

- Bounce rate tracking — monitored per mailbox and per domain in real time
- Auto-pause — mailboxes are automatically paused if bounce thresholds are breached
- 5-phase healing pipeline — paused mailboxes enter an automated recovery process to restore them safely
- Campaign health — campaigns are paused only when ALL their mailboxes are paused or removed

Monitoring system →Auto-healing pipeline →

Understanding Lead Statuses

Every lead in Superkabe has a status that tells you exactly where it is in the pipeline:

Status	What It Means	What To Do
`BLOCKED`	Failed validation or health gate	Check lead detail for the reason. No action needed — this is protection working correctly.
`HELD`	Passed validation but not yet in a campaign	Check routing rules — no rule may match this lead's persona or score. Or a platform push failed and will retry.
`ACTIVE`	Successfully pushed to sender platform	Lead is in a campaign and will be emailed. No action needed.
`PAUSED`	Campaign or mailbox was paused	Check campaign and mailbox health in the dashboard.
`BOUNCED`	Email bounced after sending	Check bounce analytics. The lead will not be sent to again.

Troubleshooting

Issue	Solution
Webhook returns 401	Check that the `x-organization-id` header matches your org ID in Settings.
Leads not appearing in Superkabe	Verify the webhook URL ends with `/api/ingest/clay`. Check that Clay is sending a POST request.
All leads showing BLOCKED	Check if the emails are from disposable domains or have invalid syntax. Click a blocked lead to see the specific rejection reason.
Leads stuck in HELD status	No routing rule matches this lead's persona and score combination. Go to Configuration and add or adjust a rule.
Lead is HELD but has a campaign assigned	The platform push failed. Check your sender platform API key in Settings and verify the target campaign is still active.
Validation shows "internal only"	Upgrade to the Growth plan for MillionVerifier API verification. Internal checks (syntax, MX, disposable) are available on all plans.
Campaign not in routing dropdown	Run a platform sync first. Go to Settings → your platform → click Sync to pull in new campaigns.

Next Steps

Getting Started

Connect mailboxes, build a sequence, launch your first campaign

Import from Smartlead

One-time migration of campaigns, sequences, leads, and mailbox metadata

Infrastructure Monitoring

Bounce tracking and health dashboards

Email Validation Explained

Deep dive into validation stages

All Status Labels Explained

Leads, mailboxes, domains, campaigns