Actions5
- Table Actions
- Workspace Actions
Overview
This node allows you to create a new record in a Clay table by sending data through a Clay webhook URL. It is useful for automating the insertion of enriched or collected data into Clay tables without manual entry. Typical scenarios include syncing contact information, company details, or any structured data from other systems directly into Clay for further enrichment or processing.
For example, you can use this node to:
- Add new leads captured from a form into a Clay table.
- Insert customer data enriched by another service into Clay for centralized management.
- Automate record creation based on events in your workflow, such as new user signups or purchases.
Properties
| Name | Meaning |
|---|---|
| Workspace | Select your Clay workspace or enter its ID manually. This determines which workspace the target table belongs to. |
| Workspace ID (manual) | Manually enter the Clay workspace ID if not selecting from the list. |
| Table | Select your Clay table within the chosen workspace or enter its ID manually. This is the destination table for the new record. |
| Table ID (manual) | Manually enter the Clay table ID if not selecting from the list. |
| Webhook URL | The Clay webhook URL associated with the target table. This URL is used to send the record data to Clay. |
| Field Mapping Mode | Choose how to specify the fields for the new record: - Manual Field Mapping: Specify each field name and value individually. - JSON Object: Provide all fields as a JSON object. |
| Fields | When using Manual Field Mapping, specify one or more fields with their exact names (case-sensitive) and values to set in the new record. |
| Fields (JSON) | When using JSON Object mode, provide the fields as a JSON object where keys are field names matching Clay table columns exactly, and values are the corresponding data to insert. |
Output
The node outputs a JSON object summarizing the result of the record creation operation. The output includes:
success: Boolean indicating if the operation was successful.message: A descriptive message about the operation outcome.operation: The operation performed (createRecord).data: The record data that was sent to Clay.timestamp: The ISO timestamp when the operation occurred.
If the operation is an update (upsert), the message notes that auto-deduplication may have prevented duplicate records.
No binary data is output by this node.
Example output JSON:
{
"success": true,
"message": "Record created successfully in Clay table",
"operation": "createRecord",
"data": {
"First Name": "John",
"Last Name": "Doe",
"Email": "john.doe@example.com",
"Company": "Example Corp"
},
"timestamp": "2024-06-01T12:00:00.000Z"
}
Dependencies
- Requires a valid Clay webhook URL configured for the target table. This URL must be obtained from the Clay table settings.
- Requires an API key credential for authenticating requests to Clay's API (configured in n8n credentials).
- The node depends on Clay's webhook mechanism to accept incoming record data.
- No additional external dependencies beyond Clay API access and webhook configuration.
Troubleshooting
- Invalid Clay webhook URL format: The webhook URL must match the expected pattern starting with
https://api.clay.com/v3/sources/webhook/pull-in-data-from-a-webhook-. Verify the URL copied from Clay table settings. - No fields specified: Ensure at least one field is provided either via manual mapping or JSON object. Empty payloads are rejected.
- Unique identifier missing (for update operations): When updating records, the unique identifier field (e.g., Email) must be included in the data to allow Clay's auto-dedupe feature to work.
- Failed to create record: Check network connectivity, webhook URL correctness, and that the target table exists and is accessible.
- Invalid JSON in Fields (JSON): If using JSON mode, ensure the JSON syntax is correct and keys match Clay table column names exactly.
- API unavailable for loading options: If workspace or table lists fail to load, fallback to manual ID entry.