SFTP Bulk to Redash Integration
AI-first ETL from SFTP Bulk into Redash. Governed entities, incremental sync, typed landing tables.
How Datrise loads SFTP Bulk into Redash
Datrise syncs SFTP Bulk's files, directories, rows, file batches, modification timestamps, and file formats into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.
Ideal for lightweight, query-driven dashboards.
Endpoints
SFTP Bulk: Bulk file drops delivered over SFTP.
Redash: Open-source SQL client for queries, visualizations, and dashboards.
How SFTP Bulk entities map to Redash
| SFTP Bulk entity | Redash object | Notes |
|---|---|---|
| files | sftp_bulk_files | id PK · custom fields → flattened columns for query results |
| directories | sftp_bulk_directories | id PK · linked to sftp_bulk_files |
| rows | sftp_bulk_rows | id PK · linked to sftp_bulk_files |
| file batches | sftp_bulk_file_batches | id PK · linked to sftp_bulk_files |
FAQ
How does Datrise handle SFTP Bulk's custom fields in Redash?
Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.
How does the SFTP Bulk to Redash sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for SFTP Bulk
Early access
Connect SFTP Bulk to Redash 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.