LivePerson to Neon Integration

How Datrise loads LivePerson into Neon

Datrise syncs LivePerson's conversations, agents, skills, messages, surveys, and engagement metrics into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

LivePerson: Messaging-first customer conversations and bots.

Neon: Serverless Postgres destination with branching and autoscaling.

How LivePerson entities map to Neon

LivePerson entity	Neon object	Notes
conversations	`liveperson_conversations`	id PK · custom fields → jsonb columns
agents	`liveperson_agents`	id PK · linked to liveperson_conversations
skills	`liveperson_skills`	id PK · linked to liveperson_conversations
messages	`liveperson_messages`	id PK · linked to liveperson_conversations

FAQ

How does Datrise handle LivePerson's custom fields in Neon?

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

How does the LivePerson to Neon sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

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