Docs/Integrations and provider selection
integrationPackage manifestv2.0.5

integration.provider-clay

Clay API, webhook, and hosted MCP integration for ContractSpec.

@lssm-tech/integration.provider-clay
Markdown ↓Structured data ↓
Source, release and verification context

Source snapshot bcc79fcc · Declared package version 2.0.5. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.

Package source ↗ Manifest ↗
servernode
EXPLORE THE PACKAGE

See where this package fits.

Follow a declared connection, inspect an import, then open the source guide when you need the detail.

THIS PACKAGEintegration.provider-clayintegrations

Arrows point from a package to its direct dependency. Each count is derived from the captured manifests.

2 declarationsSELECT TO INSPECT
PACKAGE GUIDERead at source ↗

@lssm-tech/integration.provider-clay

Injected, secret-reference-based access to Clay's public developer API, plus a safe Clay webhook-table sender, configurable HTTP-action callback authentication, and metadata for Clay's vendor-hosted MCP service.

The generic typed transport covers documented identity, Search, Routine, read-only Enterprise Table, and opted-in Workflow Alpha endpoints while stable ContractSpec operation keys remain defined in the contracts package. Hosted MCP OAuth remains client-held and is never proxied.

bindClayOperations(registry, client, options) binds every declared sales-intelligence.clay.* operation to the injected API client, hosted-MCP descriptor, or webhook-table trigger dependency. Cost-bearing Search, Routine, and Workflow commands require both scoped approval and matching runtime economic evidence before the bound provider handler runs.

Clay does not document a universal callback signature. Callers must configure a tenant-owned shared header/token; the package reports configured_shared_secret, never vendor_signature.

Declared capabilities.

Integration Provider Clay

Clay API, webhook, and hosted MCP integration for ContractSpec.

Use it to

  • Adopt clay api, webhook, and hosted mcp integration for contractspec

Requires

  • TypeScript

Choose another boundary when

  • The @lssm-tech/integration.provider-clay package constraints do not match the target runtime or platform.

@lssm-tech/integration.provider-clay

@lssm-tech/integration.provider-clay/client

@lssm-tech/integration.provider-clay/errors

@lssm-tech/integration.provider-clay/hosted-mcp

@lssm-tech/integration.provider-clay/operation-bindings

@lssm-tech/integration.provider-clay/receiver

@lssm-tech/integration.provider-clay/types

@lssm-tech/integration.provider-clay/webhooks

Imports and export paths.

8 entries

These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.

8 imports

Dependencies and related packages.

Runtime dependencies 2
Development dependencies 7
@types/bun
catalog:types
typescript
catalog:

Package scripts.

Commands declared by this package. Review its setup requirements before running them; no command here was executed by this review.

buildcontractspec-bun-build build
build:bundlecontractspec-bun-build transpile
build:typescontractspec-bun-build types
cleanrimraf dist .turbo
lint:checknode ../../../scripts/biome.cjs check .
lint:fixnode ../../../scripts/biome.cjs check --write .
testbun test
prebuildcontractspec-bun-build prebuild
typechecktsgo --noEmit
← Package directoryMore in Integrations and provider selection →
Your view

Make room for your context.

Shape the presentation around this moment. You can change it whenever you need.

Your context

The different parts of you

Choose a starting point

A useful mix of context, visuals and gentle guidance.

Tune each dimension
Each dimension can change independently. Product permissions and available actions stay unchanged.

Support the way you begin and return

Tune your support

Reading comfort

Choose your language

Interface language changes text only. Markets, prices and workflows keep their own settings.

Translation coverage

Original source

Navigation151
Graph616
Categories378
Portfolio833
Examples2,035
Source preview1,542

More translations will be added as content is reviewed.

This preference is saved on this browser.

Search the website

Useful starting points

No results. Try a shorter phrase, an operation name or another search area.

A LITTLE ROOM TO EXPLORE

Find something to explore.

Open a closer look on this page, try a different perspective, or follow the detail into its own page.

How previews and controls work
01

Look before you leave

Hover a link or focus it with Tab to see a preview. Clicking the original link or pressing Enter always opens its destination.

02

Stay with the context

Move into the preview to explore its sections. Use Alt + ↓ from a focused link to enter it with the keyboard. Escape closes it.

03

Open the possibilities

Disclosure rows, perspective choices and highlighted controls reveal more. Your view changes reading comfort and the context you explore.

A separate button for a closer look

Show small preview buttons beside links where there is room. Tap the eye to inspect, or tap the link to go straight there. This choice stays in this tab.

No browsing history is collected. Reduced motion follows your device and Your view.