Clay

The Clay integration works in two directions. Logspot sends account signals into a Clay table, so Clay can enrich the company, find the right people, and start your outreach. Clay can also call Logspot for each row in a table to pull in a company's activity on your site: events, users, when it was last seen, and revenue.

You can use either direction on its own.

Before You Start

• Plan: on the Logspot side, both directions need the Pro plan or higher. On the Clay side, the Monitor webhook and the HTTP API enrichment are included in Clay's Growth and Enterprise plans.
• Role: connecting Clay and creating API keys are for owners and admins.
• Signals: Clay rows come from account signals. Set up your Target Accounts first, since signals such as High-Intent Page Visit fire for them.

Send Signals to Clay

Create a Clay Table

1. In Clay, open a workbook, click + Add, search for Webhooks, and select Monitor webhook.
2. Copy the webhook URL.

Leave Clay's optional authentication token off. Logspot sends to the webhook URL alone.

Connect Clay

1. In Logspot, go to Integrations → Browse Catalog and open Clay.
2. Click Connect and paste the URL into Clay Monitor Webhook URL.
3. Save. Clay now shows as Connected in Your Integrations.

The URL must start with https://. Logspot stores it encrypted and never shows it again.

Add Clay to an Action

Clay is a destination on a Send Notification action.

1. Go to Actions → Browse Catalog, choose Send Notification, and click Add & Configure.
2. On the Basics tab, add a trigger. Set it to Signal, pick a Signal Type such as Internal: High-Intent Page Visit, and set Which Accounts to Target Accounts Only. Add more signals with Add Trigger.
3. Pick a Cooldown to limit how often the same company sends a row. Every Occurrence sends one row for each signal.
4. On the Destinations tab, set Destination to Clay and choose your Clay Connection.
5. Click Save Changes.

Each time a matching signal fires, Logspot sends one row to your Clay table.

What Each Row Contains

A row has three parts: the signal, the account it fired for, and the evidence behind it.

{
  "signal": {
    "id": "9bdac695-f6a5-4525-9fb7-b9a1e9e8c817",
    "type": "account.high_intent_page",
    "source": "internal",
    "strength": 2,
    "occurred_at": "2026-09-29T11:50:04.013Z"
  },
  "account": {
    "profile_id": "5ad86173-42f8-47d6-8d36-1f3c9b2a7e10",
    "company_id": "24c16bf3-cb10-4b26-9f08-f37d76c6e368",
    "name": "Acme",
    "domain": "acme.com",
    "insights_path": "/actions/profiles/5ad86173-42f8-47d6-8d36-1f3c9b2a7e10"
  },
  "evidence": {
    "path": "/pricing",
    "matched_pattern": "/pricing",
    "event_name": "Pageview",
    "acquisition_channel": "organic_search",
    "source_host": "google.com"
  }
}

Send one real signal before you build on the table, and check how the fields appear in Clay. Then add Clay enrichments off the account.domain column to find the people and contact details you want.

Use signal triggers for Clay. An action triggered by an event, and Send Test, send a shorter row with the event name, slug, project_id, occurred_at, and message. It has no company, so there is nothing for Clay to enrich.

On Clay's Free or Launch Plan

Clay's Monitor webhook comes with its Growth plan. On Free or Launch, bring signals into Clay as a CSV instead:

1. In Logspot, go to Actions → Signals, filter the feed (for example to one signal type or account), and click Export CSV. The export includes every signal that matches the filters.
2. In Clay, create a table from Import from CSV and upload the file.

Each row has the same parts as a webhook row: signal_type, signal_label, signal_strength, occurred_at, account_name, account_domain, evidence, acquisition_channel, and a logspot_url back to the account. Clay's Free plan runs up to 200 rows per table.

Limits to Know

• Clay caps each webhook. In Clay's words, "Webhook sources are limited to 50,000 submissions, and this limit persists even after deleting rows." Keep Clay actions on Target Accounts Only with a cooldown.
• Consent applies. Sending to Clay shares data with another company, so Logspot sends a row only when the visitor's consent allows analytics and marketing. A do-not-sell or do-not-share signal holds the row back, unless your consent platform has recorded marketing consent for that visitor. A held-back row is skipped and recorded, and the action's other destinations still send. See Consent.
• Failed sends retry. If Clay doesn't accept a row, Logspot tries again after 1, 5, 30, 120, and 480 minutes, and delivers it once. A row isn't retried if Clay is disconnected or your plan no longer includes Clay.

Look Up a Company From Clay

Add an HTTP API enrichment to any Clay table with a domain column to see whether each company has been on your site.

Create an API Key

1. Go to Integrations → AI & API Access → API Keys & OAuth and click Create API Key.
2. Set Access to Whole organization, and make sure the analytics:read scope is selected.
3. Copy the key. It starts with sk_ and is shown only once.

See API Authentication for more on keys and scopes.

Add the HTTP API Enrichment

1. In your Clay table, click Add enrichment, then search for and select HTTP API.
2. Set the method to GET.
3. Set the URL to https://api.logspot.io/v1/companies/lookup?domain=, then type / and pick your domain column, so it reads https://api.logspot.io/v1/companies/lookup?domain=/Domain.
4. Add a header with the key Authorization and the value Bearer sk_... (your key).
5. In Field paths to return, list the fields you want as columns, such as data.events, data.users, data.last_seen, and data.revenue.

Optionally, add a run condition so the enrichment only runs when the row has a domain.

The domain can be a bare domain (acme.com), a full URL (https://www.acme.com/pricing), or mixed case.

What Comes Back

{
  "status": "OK",
  "data": {
    "company_id": "24c16bf3-cb10-4b26-9f08-f37d76c6e368",
    "name": "Acme",
    "domain": "acme.com",
    "events": 128,
    "users": 6,
    "last_seen": "2026-09-29T11:50:04.068Z",
    "revenue": 0,
    "currency": "USD"
  }
}

To use a different window, add &range_days= with a number from 1 to 365. If your plan keeps less history than you asked for, the response also includes range_clamped: true and the date the data starts from.

Errors

Disconnecting

In Your Integrations, open the Clay card's ⋮ menu and choose Disconnect. Actions that send to Clay stop delivering until you connect it again. To stop lookups, delete the API key under Integrations → AI & API Access → API Keys & OAuth.

Related

• Integrations
• Signals & Target Accounts
• Actions
• API Authentication
• Consent