Skip to main content
Trailspark Logo
Data Enrichment Integration

AI Lead Scoring with Your Clay Enrichment

Your Clay account, your tables, your waterfalls. Trailspark sends the accounts you choose to a webhook source in your own Clay table, and the company details you send back sharpen every ICP match and score.

Sign up freeSetup guide (opens in a new tab)About Clay (opens in a new tab)

What syncs between Trailspark and Clay

Clay is a two-sided round trip. Trailspark pushes an account's domain into your Clay table, you decide what to run on it there, and one HTTP API column sends the answer back. Clay credits are spent by the columns you build, not by Trailspark.

Clay
Trailspark

Clay sends to Trailspark

  • From Clay

    Company details

    Industry, employee count, region, and market segment, returned by an HTTP API column in your Clay table. Leave a field out and nothing is written; an empty value never overwrites one you already have.

  • From Clay

    Anything else your waterfall returns

    Funding stage, headcount growth, or whatever else your columns produce. Turn a field on under Enriched fields and it becomes selectable in ICP and scoring rules, and joins the account context the AI reads.

Trailspark writes to Clay

  • To Clay

    Account domain

    Each account's website domain, with an ID that matches the answer back to the right account. Only accounts that pass your enrichment rules are sent, and an account with no business domain is never sent at all.

Use cases

Spend credits only where they earn their keep

Rules decide which accounts are worth enriching, and you choose whether that happens as soon as an account appears or only once it is engaged enough to be scored. Monthly and daily caps are a hard pause, and accounts that queue up while paused are picked back up rather than lost.

Let your own waterfall shape the ICP

Whatever your Clay columns produce can become part of how accounts are judged: activate an extra field and it shows up in ICP eligibility and scoring rules, marked so it reads apart from your own account fields, and the AI sees it when it scores the account.

Fill the gaps your CRM never had

Enrichment is additive by design. Your CRM's value wins on every field it holds, Clay only fills what is missing, and a company you do not already track is ignored rather than added, so nothing new lands in your pipeline uninvited.

Setup

Two sides to wire up: a webhook source in Clay, and one HTTP API column that sends the answer back.

  1. 1

    Create a webhook source in Clay

    In the Clay table you want to enrich, add a webhook source and copy its URL. This is the table whose columns do the work.

  2. 2

    Connect it in Trailspark

    Paste that URL under Settings, Integrations, Data enrichment. Trailspark hands back a callback URL and an ingest token, shown once.

  3. 3

    Send the answer back

    Add an HTTP API column in Clay that posts the company details to your callback URL, then turn on auto-run so new accounts enrich as they arrive.

Connect Clay with Trailspark step by step

Our docs walk through both sides of the handshake: the webhook source in Clay, the one-time callback URL and ingest token, the sample row, the HTTP API column that sends results back, and budget caps.

Read the Clay setup guide (opens in a new tab)

Common questions

You bring your own Clay account, and the credits are yours. Trailspark never resells or shares access to Clay. What each account costs depends on the columns you built, because it is your table doing the work; Trailspark's caps control how many accounts get sent, not what each one costs in Clay.

The ones you choose. A rule builder decides which accounts are worth enriching, and leaving it empty enriches every account with a business domain. Two things hold regardless of your rules: an account with no usable company domain is never sent, and an account enriched recently is not sent again until it is due for a refresh.

No. Your CRM's value wins on every field it holds, and enrichment only fills what is missing. If your Clay column returns nothing for a field, nothing is written, and an empty value never blanks a field you already have filled in.

No. Trailspark only adds detail to accounts you already track. If a row comes back for a company that is not already one of your accounts, it is ignored rather than saved, and no account or lead is created from it.

Because the connection runs both ways. Trailspark pushes accounts to your Clay webhook, and your Clay table posts the answers back to a callback URL; the ingest token proves the answer really came from your table. Both are shown once for security, so if you lose the token, disconnect and reconnect to be issued a new pair.

A Clay webhook source accepts a fixed number of submissions over its life, so Trailspark warns you as yours gets close. Create a fresh webhook source in Clay, then disconnect and reconnect with the new URL to reset it. Testing the connection never sends a real row, so it costs you nothing against that limit.

Trailspark is billed on the unique accounts it evaluates each month, not seats or CRM contacts. Every plan is the full platform, Free included; see pricing for the tiers, or talk to us about custom volume. Clay credits are billed to you by Clay, separately.

Other integrations and pages

Integration

Salesforce

CRM

Integration

HubSpot

CRM

Integration

Airtable

CRM

Product

How scoring works

The full product page.

See Trailspark and Clay on your own data

Start free. Connect Clay with OAuth. Watch scores land in custom fields you create on the records your reps already use.

Sign up free
Trailspark Logo

Account evaluation for B2B PLG. Define what good looks like. Trailspark brings the account story together, applies the right lens, explains why, and sends the result back to your stack.

© 2026 Trailspark. All rights reserved.

Built for revenue teams who demand better.