

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 Webflow. Navigate to the Webflow dashboard, select the project containing the data, and look for the CMS Collections tab. Export the desired collections as CSV files. Webflow provides a built-in option to export collection data, which can be downloaded directly to your local system.
Set up your local environment to work with Apache Iceberg. Ensure you have Apache Spark or Flink installed, as Iceberg is commonly used with these engines. You will also need Java and a compatible build tool like Maven or Gradle to compile and run your Iceberg setup.
Download and install Apache Iceberg. You can do this by cloning the Iceberg repository from GitHub or downloading a pre-built package. Follow the installation instructions specific to your processing engine (e.g., Spark or Flink) as outlined in the Iceberg documentation. This will typically involve adding Iceberg to your classpath and configuring it within your data processing engine.
Define the schema for your Iceberg table based on the structure of the CSV data exported from Webflow. This involves specifying the columns and data types that match the exported CSV files. You can do this by writing a DDL (Data Definition Language) script or using a Spark/Flink job to define the schema programmatically.
Write a script to load the CSV data into your chosen processing engine. Use Spark's `spark.read.csv()` or Flink's `CsvInputFormat` to read the CSV files. Ensure that the data is loaded into a DataFrame or DataSet, conforming to the schema defined in the previous step.
Use your data processing engine to write the data into the Iceberg table. In Spark, this can be done using the `write` method on the DataFrame, like `dataframe.write.format("iceberg").save("table_name")`. In Flink, configure a sink that writes to Iceberg. Ensure that the data types and structure match the Iceberg table schema to avoid errors.
After the data transfer, verify that the data in the Iceberg table matches the original CSV data. You can run queries to check for consistency and completeness. Perform any necessary maintenance tasks, such as optimizing the data layout within Iceberg using compaction or cleaning up temporary files, to ensure efficient storage and query performance.
By completing these steps, you will have successfully moved data from Webflow to Apache Iceberg without relying on third-party connectors. This manual process leverages the built-in capabilities of Webflow, Apache Iceberg, and your chosen data processing engine.
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.
Webflow is basically a great platform for web designs that can build production-ready experiences without code. Webflow is the leading platform to design, and launch powerful websites visually that enables you to rapidly design and build production-scale responsive websites and it is also an popular platform of CMS, and hosting provider perfect for building production websites and prototypes without coding. Webflow is an overall innovative tool to simplify the lives of designers and teams all around and helping them work faster and deliver high quality websites.
Webflow's API provides access to a wide range of data related to websites built on the Webflow platform. The following are the categories of data that can be accessed through the API:
1. Site data: This includes information about the website, such as its name, URL, and settings.
2. Collection data: This includes data related to collections, such as the name, description, and fields.
3. Item data: This includes data related to individual items within a collection, such as the item's ID, name, and field values.
4. Asset data: This includes data related to assets used on the website, such as images, videos, and files.
5. Form data: This includes data related to forms on the website, such as form submissions and form fields.
6. E-commerce data: This includes data related to e-commerce functionality on the website, such as products, orders, and customers.
7. CMS data: This includes data related to the content management system used on the website, such as templates, pages, and content.
Overall, the Webflow API provides access to a wide range of data that can be used to build custom integrations and applications that interact with Webflow websites.
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: