DatriseAI-first ETL

Clay Snowflake

AI-first ETL from Clay into Snowflake. Governed entities, incremental sync, typed landing tables.

How Datrise loads Clay into Snowflake

Datrise syncs Clay's contacts, accounts, deals, activities, and lifecycle events into Snowflake as a typed table per source entity. Flexible or custom fields land in VARIANT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP_TZ.

Sync is incremental: Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size, so re-runs update only what changed. Automatic micro-partitioning, with optional clustering keys on high-cardinality ids. Snowflake upper-cases unquoted identifiers, so Datrise standardizes on lower-case quoted names to keep column references stable.

Ideal for central analytics warehouses feeding BI and AI workloads.

Endpoints

Clay: AI-native CRM for relationship data, enrichment, and workflow automation.

Snowflake: Cloud data warehouse with separated compute and storage.

How Clay entities map to Snowflake

Clay entitySnowflake objectNotes
contactsclay_contactsid PK · custom fields → VARIANT columns
accountsclay_accountsid PK · linked to clay_contacts
dealsclay_dealsid PK · linked to clay_contacts
activitiesclay_activitiesTIMESTAMP_TZ events

FAQ

How does Datrise handle Clay's custom fields in Snowflake?

Flexible values are stored as VARIANT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Snowflake types.

How does the Clay to Snowflake sync stay up to date?

It runs incrementally — Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size.

Related pipelines

Early access

Connect Clay to Snowflake the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.