DatriseAI-first ETL

Dixa Snowflake

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

How Datrise loads Dixa into Snowflake

Datrise syncs Dixa's conversations, agents, customers, tags, and resolution metrics 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

Dixa: Customer service platform for conversations across channels.

Snowflake: Cloud data warehouse with separated compute and storage.

How Dixa entities map to Snowflake

Dixa entitySnowflake objectNotes
conversationsdixa_conversationsid PK · custom fields → VARIANT columns
agentsdixa_agentsid PK · linked to dixa_conversations
customersdixa_customersid PK · linked to dixa_conversations
tagsdixa_tagsid PK · linked to dixa_conversations

FAQ

How does Datrise handle Dixa'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 Dixa 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 Dixa 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.