DatriseAI-first ETL

SFTP Bulk to Domo Integration

AI-first ETL from SFTP Bulk into Domo. Governed entities, incremental sync, typed landing tables.

How Datrise loads SFTP Bulk into Domo

Datrise syncs SFTP Bulk's files, directories, rows, file batches, modification timestamps, and file formats into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

SFTP Bulk: Bulk file drops delivered over SFTP.

Domo: Cloud BI platform combining data integration and executive dashboards.

How SFTP Bulk entities map to Domo

SFTP Bulk entityDomo objectNotes
filessftp_bulk_filesid PK · custom fields → flattened columns for Magic ETL
directoriessftp_bulk_directoriesid PK · linked to sftp_bulk_files
rowssftp_bulk_rowsid PK · linked to sftp_bulk_files
file batchessftp_bulk_file_batchesid PK · linked to sftp_bulk_files

FAQ

How does Datrise handle SFTP Bulk's custom fields in Domo?

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

How does the SFTP Bulk to Domo sync stay up to date?

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

Connect SFTP Bulk to Domo 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.