DatriseAI-first ETL

Freshcaller to Neon Integration

AI-first ETL from Freshcaller into Neon. Governed entities, incremental sync, typed landing tables.

How Datrise loads Freshcaller into Neon

Datrise syncs Freshcaller's calls, agents, queues, phone numbers, call metrics, and recordings 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

Freshcaller: Cloud call center for support and sales.

Neon: Serverless Postgres destination with branching and autoscaling.

How Freshcaller entities map to Neon

Freshcaller entityNeon objectNotes
callsfreshcaller_callsid PK · custom fields → jsonb columns
agentsfreshcaller_agentsid PK · linked to freshcaller_calls
queuesfreshcaller_queuesid PK · linked to freshcaller_calls
phone numbersfreshcaller_phone_numbersid PK · linked to freshcaller_calls

FAQ

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