clay

n8n node for Clay

Package Information

Downloads: 216 weekly / 469 monthly
Latest Version: 3.1.0
Author: Max Chuchmai

Documentation

n8n-nodes-clay

Community n8n node package that adds the Clay node.

What this node does

The Clay node fans out one request per incoming item to a selected Clay URL and waits for all callbacks before resuming workflow execution.

At execution time it:

  1. Reads all input items.
  2. Sends a POST request for each item to the selected request URL.
  • Requests are dispatched with bounded concurrency.
  1. Injects a callback URL into each outbound payload.
  2. Waits until all callback parts are received.
  3. Returns callback payloads in part order.

Node behavior

  • Node name in n8n UI: Clay
  • Operation model: send-and-wait-many (fan-out + webhook resume)
  • Input: any number of items
  • Output: one item per callback payload

Parameters

  • Request URL Name or ID: Selects a URL from the Clay Tables data table.
  • Field Values: Auto-generated inputs from the selected row's fields column.
  • Options:
    • Callback Field Name: Field name used to pass resume URL (default: resume_url).
    • Max Concurrency: Maximum number of outbound requests running at the same time (default: 5).
    • Max Wait Minutes: Max wait before timeout (default: 30).

Clay Tables schema

The Clay Tables n8n data table now uses these columns:

  • name: Friendly name shown in the node selector.
  • url: Target enrichment webhook URL.
  • fields: Comma-separated list of input fields to send to Clay (for example company_domain, company_name).

At runtime, the node reads the selected table row and builds a strict outbound payload shape:

  • data: Object containing configured fields from Clay Tables.
  • resume_url (or your configured callback field name): callback URL for Clay.

If fields is empty, null, or undefined, no field inputs are generated and the node falls back to sending the full input item JSON in data.

Important limitation

Execution state is currently stored in process memory. This is reliable for single-process deployments. For clustered or multi-instance setups, use an external state store (for example Redis).

Development

Prerequisites

  • Node.js 22+
  • npm

Install

npm install

Build

npm run build

Build in watch mode

npm run build:watch

Lint

npm run lint

Package metadata

  • npm package: @maxim_chu/n8n-nodes-clay
  • license: MIT

Discussion