DatriseAI-first ETL

Intruder to Metabase Integration

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

How Datrise loads Intruder into Metabase

Datrise syncs Intruder's scans, issues, targets, severities, occurrences, and remediation statuses 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

Intruder: Continuous vulnerability scanning for internet assets.

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

How Intruder entities map to Metabase

Intruder entityMetabase objectNotes
scansintruder_scansid PK · custom fields → flattened columns for the question builder
issuesintruder_issuesid PK · linked to intruder_scans
targetsintruder_targetsid PK · linked to intruder_scans
severitiesintruder_severitiesid PK · linked to intruder_scans

FAQ

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

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

Related pipelines

Early access

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