

Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say

Andre Exner

"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."

Chase Zieman

“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
Begin by exporting your data from Coda. Coda allows you to export documents in various formats such as CSV or JSON. Navigate to the document you wish to export, click on the 'Share' or 'Export' option, and select the desired format. For this guide, exporting as CSV is recommended for simplicity.
Prepare your Apache Iceberg environment. Ensure you have a compatible compute engine like Apache Spark, Flink, or a compatible SQL engine with Apache Iceberg support. Install the necessary Iceberg libraries and dependencies for your chosen engine to enable you to create and manage Iceberg tables.
Define the schema for your Iceberg table. This schema should correspond to the structure of your data exported from Coda. Use your compute engine to execute a SQL statement that creates a new Iceberg table. For example, using Spark SQL:
```sql
CREATE TABLE iceberg_db.my_table (
id INT,
name STRING,
value DOUBLE
)
USING iceberg;
```
Convert your exported CSV data into a format that can be ingested by your compute engine. If necessary, clean or transform the data to match the schema defined in your Iceberg table. This might involve using simple scripting in Python or a similar language to ensure data types and formats align.
Load the prepared data into the Iceberg table. Use your compute engine's native capabilities to read the CSV file and write the data to the Iceberg table. For example, using Spark:
```python
from pyspark.sql import SparkSession
spark = SparkSession.builder \
.appName("Coda to Iceberg") \
.getOrCreate()
# Read CSV data
df = spark.read.csv("path/to/exported_data.csv", header=True, inferSchema=True)
# Write to Iceberg table
df.write \
.format("iceberg") \
.mode("append") \
.save("iceberg_db.my_table")
```
After loading, verify that the data has been correctly ingested into the Iceberg table. Run queries to check the data integrity, ensuring that the number of records and the data values are correct. Use simple SQL queries through your compute engine to perform these checks:
```sql
SELECT COUNT(*) FROM iceberg_db.my_table;
```
Finally, optimize and manage your Iceberg table for performance and storage efficiency. Execute maintenance operations like compaction and partitioning if necessary. Use Iceberg's built-in commands to optimize the table:
```sql
CALL iceberg.system.rewrite_data_files('iceberg_db.my_table');
```
By following these steps, you can successfully move data from Coda to Apache Iceberg without relying on third-party connectors or integrations, using the built-in capabilities of your chosen compute engine and Apache Iceberg.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
Coda is a comprehensive solution that combines documents, spreadsheets, and building tools into a single platform. With this tool, project managers can track OKRs while also brainstorming with their teams.
Coda's API provides access to a wide range of data types, including:
1. Documents: Access to all the documents in a user's Coda account, including their metadata and content.
2. Tables: Access to the tables within a document, including their columns, rows, and cell values.
3. Rows: Access to individual rows within a table, including their cell values and metadata.
4. Columns: Access to individual columns within a table, including their cell values and metadata.
5. Formulas: Access to the formulas within a table, including their syntax and results.
6. Views: Access to the views within a table, including their filters, sorts, and groupings.
7. Users: Access to the users within a Coda account, including their metadata and permissions.
8. Groups: Access to the groups within a Coda account, including their metadata and membership.
9. Integrations: Access to the integrations within a Coda account, including their metadata and configuration.
10. Webhooks: Access to the webhooks within a Coda account, including their metadata and configuration.
Overall, Coda's API provides a comprehensive set of data types that developers can use to build powerful integrations and applications.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: