DatriseAI-first ETL

Retently to Snowflake Integration

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

How Datrise loads Retently into Snowflake

Datrise syncs Retently's surveys, responses, customers, NPS scores, campaigns, and feedback comments 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

Retently: NPS and customer satisfaction survey tracking.

Snowflake: Cloud data warehouse with separated compute and storage.

How Retently entities map to Snowflake

Retently entitySnowflake objectNotes
surveysretently_surveysid PK · custom fields → VARIANT columns
responsesretently_responsesid PK · linked to retently_surveys
customersretently_customersid PK · linked to retently_surveys
NPS scoresretently_nps_scoresid PK · linked to retently_surveys

FAQ

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