Clay integration

Sales · 1 action · API key auth

Push records into a Clay table via its inbound webhook so Clay can run its data-enrichment waterfall on prospects and accounts.

Put Clay to work View Clay integration docs

Overview

The ModuleX Clay integration lets a ModuleX agent operate Clay on your behalf — working across populates — directly from a plain-English request, using your organization's own Clay credentials. No pre-built workflow is required: the agent picks the right Clay action for the task.

Clay is a sales platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Clay action — or, when you want a repeatable process, the composer assembles a Clay workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Clay in plain English

Type what you want. A ModuleX agent picks the right Clay action — or chains several — and runs it. No workflow to build.

Populate a Clay table with a record by sending it to the table's webhook URL
resolves topopulate

Use cases

What you can automate with Clay

Populate a Clay table with a record by sending it to the table's webhook URLpopulate

At a glance

Clay integration at a glance

VendorClay

CategorySales

Actions available1

AuthenticationAPI key

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

The 1 Clay action

Populates1

populate

Populate a Clay table with a record by sending it to the table's webhook URL. Clay enriches the record asynchronously; the response is an acknowledgment plus transport metadata.

See full parameters and response schemas in the Clay integration docs

Two ways

Two ways to use Clay in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Clay action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Clay into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Clay

API keyClay uses API-key authentication. You provide your own Clay secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use Clay without re-authenticating.

Step-by-step setup in the Clay docs

Pairs well with Clay

Agents often chain Clay with these — connect them once and the agent can use all of them in a single task.

Sixtyfour AI4 actions

Wiza4 actions

FAQ

Clay + ModuleX FAQ

A ModuleX agent can run any of Clay's 1 action — across populates — from a plain-English request, using your organization's own Clay credentials.

No. The agent selects the right Clay action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Via your own Clay API key, stored encrypted and scoped to your organization.

1, spanning populates.

Clay runs on your own credentials, so any Clay usage is billed by Clay directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Clay to work in ModuleX.

Connect Clay once with your own credentials and let your agent run its 1 action on demand.

Put Clay to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →