A destination is where a pipeline writes the data it pulls from a source. Pick one when you create a pipeline, and reuse it across as many pipelines as you like.
Warehouses and databases
Files and object storage
| Destination | Use it for |
|---|
| Amazon S3 | Parquet or JSON files in your bucket, with an IAM role or an access key. |
| Azure Blob Storage | Parquet or JSON files in a blob container. |
| Azure Data Lake Gen2 | Files in an ADLS Gen2 filesystem. |
| DuckDB | A managed DuckDB file you download after a run. |
Spreadsheets
| Destination | Use it for |
|---|
| Google Sheets | Rows appended into a Google Spreadsheet. |
Before you start
Whichever destination you choose, make sure the identity KoraBridge uses can create tables or write files there. Every destination page lists what you need, where to find it, and the mistakes that come up most. Use Test connection after saving. For PostgreSQL, Lakebase, Databricks and Amazon S3 it performs a small real test write, so a green result means a pipeline can load. The other destinations check the configuration only, so the first pipeline run is the real proof.