DatriseAI-first ETL

Manatal Metabase

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

How Datrise loads Manatal into Metabase

Datrise syncs Manatal's contacts, accounts, deals, activities, and lifecycle events 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

Manatal: Recruiting CRM/ATS for candidates, pipelines, and placements.

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

How Manatal entities map to Metabase

Manatal entityMetabase objectNotes
contactsmanatal_contactsid PK · custom fields → flattened columns for the question builder
accountsmanatal_accountsid PK · linked to manatal_contacts
dealsmanatal_dealsid PK · linked to manatal_contacts
activitiesmanatal_activitiestemporal columns for trends events

FAQ

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

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

Related pipelines

Early access

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