Available Destinations
URL Webhook
Send data to any HTTP endpoint
Snowflake
Insert data into Snowflake tables
Google Sheets
Append data to Google Sheets
Clay
Send data to Clay tables
URL Destination
Send data to any HTTP endpoint via POST request. Perfect for webhooks, custom integrations, or serverless functions.Configuration
Parameters
The HTTP endpoint URL where data will be sent via POST request
Optional custom headers to include in the POST request
Payload Format
The data sent to your endpoint will follow this structure:Use Cases
Webhook Integration
Webhook Integration
Send data to platforms like Zapier, Make, or n8n for workflow automation
Custom API
Custom API
POST data directly to your application’s API endpoint
Serverless Functions
Serverless Functions
Trigger AWS Lambda, Vercel Functions, or Cloudflare Workers
Snowflake Destination
Insert enriched data directly into Snowflake data warehouse tables.Configuration
Parameters
Your Snowflake account identifier
Target database name
Target schema name
Target table name
Snowflake warehouse to use for the operation
Snowflake username with write permissions
Snowflake password
Ensure your table schema matches the JSON schema defined in your query for seamless data insertion.
Google Sheets Destination
Append data to Google Sheets for easy collaboration and visualization.Configuration
Parameters
The Google Sheets spreadsheet ID (found in the sheet URL)
The name of the specific sheet/tab within the spreadsheet
Google OAuth access token with Google Sheets API permissions
How to Get Access Token
1
Enable Google Sheets API
Go to Google Cloud Console and enable the Google Sheets API
2
Create OAuth Credentials
Create OAuth 2.0 credentials for your application
3
Obtain Access Token
Use the OAuth flow to obtain an access token with
https://www.googleapis.com/auth/spreadsheets scopeClay Destination
Send data to Clay tables via webhook for sales and marketing workflows.Configuration
Parameters
Your Clay webhook URL (obtained from Clay table settings)
Data Flattening
Clay webhooks expect flat data structures. The API automatically handles:
- Nested objects: Flattened with underscore-separated keys (e.g.,
address.citybecomesaddress_city) - Primitive arrays: Joined as comma-separated strings
- Object arrays: Stringified as JSON
Example
Before flattening:Comparison
| Feature | URL | Snowflake | Sheets | Clay |
|---|---|---|---|---|
| Setup Complexity | Low | Medium | Medium | Low |
| Best For | Custom integrations | Data warehousing | Collaboration | Sales/Marketing |
| Authentication | Optional | Required | OAuth | Webhook URL |
| Data Volume | Any | Large | Small-Medium | Small-Medium |
| Real-time | ✅ | ✅ | ✅ | ✅ |
