Intruder to Yellowfin Integration
AI-first ETL from Intruder into Yellowfin. Governed entities, incremental sync, typed landing tables.
How Datrise loads Intruder into Yellowfin
Datrise syncs Intruder's scans, issues, targets, severities, occurrences, and remediation statuses into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.
Ideal for dashboards with automated data storytelling.
Endpoints
Intruder: Continuous vulnerability scanning for internet assets.
Yellowfin: BI suite with dashboards, automated insights, and data storytelling.
How Intruder entities map to Yellowfin
| Intruder entity | Yellowfin object | Notes |
|---|---|---|
| scans | intruder_scans | id PK · custom fields → flattened columns |
| issues | intruder_issues | id PK · linked to intruder_scans |
| targets | intruder_targets | id PK · linked to intruder_scans |
| severities | intruder_severities | id PK · linked to intruder_scans |
FAQ
How does Datrise handle Intruder's custom fields in Yellowfin?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Yellowfin types.
How does the Intruder to Yellowfin sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Intruder
Early access
Connect Intruder to Yellowfin 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.