DatriseAI-first ETL

LivePerson to Metabase Integration

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

How Datrise loads LivePerson into Metabase

Datrise syncs LivePerson's conversations, agents, skills, messages, surveys, and engagement metrics 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

LivePerson: Messaging-first customer conversations and bots.

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

How LivePerson entities map to Metabase

LivePerson entityMetabase objectNotes
conversationsliveperson_conversationsid PK · custom fields → flattened columns for the question builder
agentsliveperson_agentsid PK · linked to liveperson_conversations
skillsliveperson_skillsid PK · linked to liveperson_conversations
messagesliveperson_messagesid PK · linked to liveperson_conversations

FAQ

How does Datrise handle LivePerson'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 LivePerson to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect LivePerson 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.