DatriseAI-first ETL

Revinate to Metabase Integration

AI-first ETL from Revinate into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Revinate into Metabase

Datrise syncs Revinate's guests, reservations, reviews, campaigns, hotels, and guest profiles into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Revinate: Hospitality guest data and reputation management.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Revinate entities map to Metabase

Revinate entityMetabase objectNotes
guestsrevinate_guestsid PK · custom fields → flattened columns for the question builder
reservationsrevinate_reservationsid PK · linked to revinate_guests
reviewsrevinate_reviewsid PK · linked to revinate_guests
campaignsrevinate_campaignsid PK · linked to revinate_guests

FAQ

How does Datrise handle Revinate's custom fields in Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the Revinate to Metabase sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Revinate to Metabase 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.