
This integration requires a Pro plan.
Start Here
Orbit AI 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 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).
- 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: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: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 What to do:
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).
Step 5: Test the Connection
Do a real test so you know Orbit is sending data and Clay is receiving it. Test checklist: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.
Step A: Enable Wait Mode in Orbit
First, tell Orbit to wait for Clay’s response instead of continuing immediately. What to do:Step B: Send a Test from Orbit
Send test data so Clay creates the necessary columns, including the correlation ID. What to do: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:
Required settings:
Endpoint URL:
POST
Headers:
| Key | Value |
|---|---|
X-Orbit-API-Key | your_api_key_from_orbit |
Step D: Map Enriched Fields in Orbit
Once Clay sends data back, map the fields to your contact records. What to do:Common Issues and Fixes
Can't find _correlation_id column
Can't find _correlation_id column
- Send a test from Orbit first - Clay auto-creates columns from incoming data.
- Look for a column named “Correlation Id” or “_correlation_id”.
Invalid or missing correlation ID error
Invalid or missing correlation ID error
- Reference the correct Clay column using
/Column Nameformat. - Check the exact column name in your Clay table - it might be “Correlation Id” not “_correlation_id”.
Missing X-Orbit-API-Key error
Missing X-Orbit-API-Key error
- Add a header in Clay’s HTTP API settings.
- Key:
X-Orbit-API-Key - Value: Your API key from Orbit’s Clay integration settings.
Workflow times out
Workflow times out
- Default timeout is 5 minutes.
- Make sure your Clay HTTP API column is configured to run automatically when rows are added, not manually.
Monitor Webhook errors
Monitor Webhook errors
- The inbound webhook (Monitor Webhook) must NOT require auth.
- Only the return HTTP API needs the X-Orbit-API-Key header.
Data not appearing in Clay
Data not appearing in Clay
- 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
Creating Workflows
Learn how to build workflows
HubSpot Integration
Connect to HubSpot CRM
Salesforce Integration
Connect to Salesforce
Workflow Features
Explore workflow capabilities
Visit Clay · All Integrations · Documentation



