Skip to main content
Hypermodel API supports multiple destination types for delivering enriched data from async queries.

Available Destinations


URL Destination

Send data to any HTTP endpoint via POST request. Perfect for webhooks, custom integrations, or serverless functions.

Configuration

{
  "type": "URL",
  "config": {
    "endpoint": "https://webhook.site/unique-id",
    "headers": {
      "X-API-Key": "your-api-key",
      "X-Custom-Header": "custom-value"
    }
  }
}

Parameters

endpoint
string
required
The HTTP endpoint URL where data will be sent via POST request
headers
object
Optional custom headers to include in the POST request

Payload Format

The data sent to your endpoint will follow this structure:
{
  "id": "query_1234567890_abc123",
  "raw": "Raw unformatted response from Claude...",
  "data": [
    /* Formatted data matching your schema */
  ]
}

Use Cases

Send data to platforms like Zapier, Make, or n8n for workflow automation
POST data directly to your application’s API endpoint
Trigger AWS Lambda, Vercel Functions, or Cloudflare Workers

Snowflake Destination

Insert enriched data directly into Snowflake data warehouse tables.

Configuration

{
  "type": "Snowflake",
  "config": {
    "account": "your-account",
    "database": "your-database",
    "schema": "your-schema",
    "table": "your-table",
    "warehouse": "your-warehouse",
    "username": "your-username",
    "password": "your-password"
  }
}

Parameters

account
string
required
Your Snowflake account identifier
database
string
required
Target database name
schema
string
required
Target schema name
table
string
required
Target table name
warehouse
string
required
Snowflake warehouse to use for the operation
username
string
required
Snowflake username with write permissions
password
string
required
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

{
  "type": "Sheets",
  "config": {
    "spreadsheetId": "your-spreadsheet-id",
    "sheetName": "Sheet1",
    "accessToken": "google-oauth-access-token"
  }
}

Parameters

spreadsheetId
string
required
The Google Sheets spreadsheet ID (found in the sheet URL)
sheetName
string
required
The name of the specific sheet/tab within the spreadsheet
accessToken
string
required
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 scope
Access tokens expire. Consider implementing token refresh logic for production use.

Clay Destination

Send data to Clay tables via webhook for sales and marketing workflows.

Configuration

{
  "type": "Clay",
  "config": {
    "webhookUrl": "https://clay.com/webhook/your-webhook-url"
  }
}

Parameters

webhookUrl
string
required
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.city becomes address_city)
  • Primitive arrays: Joined as comma-separated strings
  • Object arrays: Stringified as JSON

Example

Before flattening:
{
  "company": {
    "name": "Example Corp",
    "address": {
      "city": "San Francisco"
    }
  },
  "tags": ["tech", "saas"]
}
After flattening (sent to Clay):
{
  "company_name": "Example Corp",
  "company_address_city": "San Francisco",
  "tags": "tech,saas"
}

Comparison

FeatureURLSnowflakeSheetsClay
Setup ComplexityLowMediumMediumLow
Best ForCustom integrationsData warehousingCollaborationSales/Marketing
AuthenticationOptionalRequiredOAuthWebhook URL
Data VolumeAnyLargeSmall-MediumSmall-Medium
Real-time

Next Steps