> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbitforms.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Clay Integration
> Enrich form data with company and contact info
This integration requires a **Pro** plan.
## Start Here
OrbitForms can send form submissions to Clay for enrichment, so you can automatically look up company data, verify contacts, and score leads. This guide shows you how to create a Clay table, connect it to Orbit, and use enriched data in your workflows.
### Overview
Here's the idea in plain terms:
* You create a **Clay table** with a webhook source, which generates a unique URL.
* When someone submits a form, Orbit sends the data to Clay via that webhook URL.
* Clay enriches the data (company info, LinkedIn profiles, etc.) using its 75+ data providers.
* Optionally, Clay can send the enriched data **back to Orbit** so you can use it in later workflow steps.
### Why This Matters
Clay enrichment transforms basic form submissions into complete lead profiles. Instead of just getting an email address, you get company size, funding status, industry, tech stack, and more—all automatically, without any manual research.
***
## Step 1: Create a Clay Table
First, set up a Clay table to receive form submissions from Orbit.
[Clay Getting Started Guide](https://www.clay.com)
**What to do:**
* Log in to Clay and click **New Table**.
* Add columns for the data you want to collect (e.g., Email, Company, First Name, Last Name).
**What this does:**
* Creates a destination for your form data.
* You can later add enrichment columns to look up company data, LinkedIn profiles, etc.
***
## Step 2: Add Monitor Webhook Source
Now you'll add a webhook source so Clay can receive data from Orbit.
**What to do in Clay:**
In your Clay table, click **Actions** in the top menu.
Select **Import** → **Monitor Webhook**.
Clay will generate a unique **Webhook URL**.
Make sure "Require Auth Token" is **OFF**.
Click **Copy** to copy the webhook URL.
The webhook must NOT require an auth token. Orbit sends data directly without authentication headers.
***
## Step 3: Connect Clay to Orbit
You are going to tell Orbit where to send form data when a submission happens.
**What to do in Orbit:**
In Orbit, navigate to **Integrations**.
Find **Clay** and click to open settings.
Paste your **Clay Webhook URL**.
Click **Save**.
***
## Step 4: Add Clay to a Workflow
Now add a Clay enrichment node to your workflow so form submissions flow to Clay.
[Workflow Creation Guide](/guides/workflows)
**What to do:**
Create a new workflow or open an existing one.
Add a **Form Trigger** as your starting node.
Click **+** to add a new node → choose **Enrichment** → **Clay**.
Save your workflow.
**What this does:**
* Every form submission triggers the workflow.
* The Clay node sends submission data to your Clay table.
* The workflow continues immediately (fire-and-forget mode).
By default, Orbit sends data and continues immediately. If you need enriched data in later steps, see the "Advanced: Two-Way Data Flow" section below.
***
## Step 5: Test the Connection
Do a real test so you know Orbit is sending data and Clay is receiving it.
**Test checklist:**
Open your form in a browser.
Submit a test entry with real-looking data.
In Clay, check your table for a new row with the submitted data.
In Orbit, check the workflow run history to confirm it executed.
**That's it!** Data will flow from Orbit to Clay on every form submission. Use Clay's native integrations (HubSpot, Salesforce, etc.) to push enriched data to your CRM, or continue reading to send enriched data back to Orbit.
***
## Advanced: Two-Way Data Flow
Need enriched data back in your Orbit workflow? Enable two-way mode and Clay will send enriched data back before the workflow continues.
### How It Works
Here's the idea in plain terms:
* Orbit sends form data to Clay and **waits** for a response.
* Clay enriches the data and uses an **HTTP API column** to send it back.
* Orbit receives the enriched data and **continues the workflow** with the new fields.
The flow looks like: Form Submission → Send to Clay → Clay Enriches → Return to Orbit → Continue Workflow
***
### Step A: Enable Wait Mode in Orbit
First, tell Orbit to wait for Clay's response instead of continuing immediately.
**What to do:**
Open your workflow and click on the **Clay node**.
Toggle on **"Wait for enriched data"**.
In the **Advanced** section of Clay integration settings, click **Generate API Key**.
Copy the API key - you'll need it in Clay.
***
### Step B: Send a Test from Orbit
Send test data so Clay creates the necessary columns, including the correlation ID.
**What to do:**
In the Clay node settings, click **Send Test**.
Check your Clay table - you should see a new row with columns including `_correlation_id`.
Clay may name the column "Correlation Id" instead of "\_correlation\_id". Note the exact name - you'll need it in the next step.
***
### Step C: Configure Clay's HTTP API
Add an HTTP API column in Clay to send enriched data back to Orbit.
**What to do in Clay:**
Click **+** to add a new column.
Select **Enrich Data** → **HTTP API**.
Configure the HTTP API with the settings below.
**Required settings:**
**Endpoint URL:**
```
https://orbitforms.ai/api/webhooks/clay/return
```
**Method:** `POST`
**Headers:**
| Key | Value |
| ----------------- | ------------------------- |
| `X-Orbit-API-Key` | `your_api_key_from_orbit` |
**Body (JSON):**
```json theme={null}
{
"_correlation_id": "/Correlation Id",
"company_size": "/Company Size",
"industry": "/Industry",
"linkedin_url": "/LinkedIn URL",
"annual_revenue": "/Annual Revenue"
}
```
The `_correlation_id` field is REQUIRED. Without it, Orbit cannot match the enriched data back to your workflow.
***
### Step D: Map Enriched Fields in Orbit
Once Clay sends data back, map the fields to your contact records.
**What to do:**
Run your Clay HTTP API column to send data back.
In Orbit, the field mapper will display the fields Clay returned.
Map Clay fields to contact fields (name, email, company) or create custom fields.
Save your workflow.
Custom fields are stored in a flexible format, so you can map any data Clay returns - company size, funding, technologies, and more.
***
## Common Issues and Fixes
* Send a test from Orbit first - Clay auto-creates columns from incoming data.
* Look for a column named "Correlation Id" or "\_correlation\_id".
* Reference the correct Clay column using `/Column Name` format.
* Check the exact column name in your Clay table - it might be "Correlation Id" not "\_correlation\_id".
* Add a header in Clay's HTTP API settings.
* Key: `X-Orbit-API-Key`
* Value: Your API key from Orbit's Clay integration settings.
* Default timeout is 5 minutes.
* Make sure your Clay HTTP API column is configured to run automatically when rows are added, not manually.
* The inbound webhook (Monitor Webhook) must NOT require auth.
* Only the return HTTP API needs the X-Orbit-API-Key header.
* Check that the webhook URL in Orbit exactly matches Clay's webhook URL.
* Verify the workflow is active and the form trigger is correctly configured.
* Check the workflow run history in Orbit for any errors.
***
## Related Articles
Learn how to build workflows
Connect to HubSpot CRM
Connect to Salesforce
Explore workflow capabilities
***
[Visit Clay](https://www.clay.com) · [All Integrations](/integrations/overview) · [Documentation](/)