Summarize


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."
First, configure a webhook in your GitLab repository to trigger data export actions. Navigate to your GitLab project's settings, select "Webhooks," and create a new webhook. Set the URL to point to your intermediate server or service that will handle the data processing before sending it to Google Pub/Sub. Choose the events you want to trigger the webhook, such as push events or merge requests.
Go to the Google Cloud Console and create a new project or use an existing one. This project will be used to manage your Google Pub/Sub resources. Ensure you have the necessary permissions to create and manage Pub/Sub topics and subscriptions.
In the Google Cloud Console, navigate to the "APIs & Services" section and enable the Google Pub/Sub API for your project. This step allows you to create topics and subscriptions programmatically using Google Cloud's services.
Still in the Google Cloud Console, go to the Pub/Sub section and create a new topic. A topic is a named resource to which messages are sent by publishers and from which messages are received by subscribers. Note the topic name, as you will need it to send data to this topic.
Set up a server or cloud function to listen for incoming HTTP POST requests from your GitLab webhook. This server will process the incoming data and prepare it for publication to Google Pub/Sub. You can use any programming language or framework that supports HTTP server functionalities (e.g., Flask for Python, Express for Node.js).
In your server code, handle incoming webhook data by parsing the JSON payload. Use Google Cloud's Pub/Sub client library to authenticate and send this data to your previously created Pub/Sub topic. Ensure you have the proper authentication setup, like a service account key, to authorize the Pub/Sub API requests.
Example in Python (using the google-cloud-pubsub library):
```python
from google.cloud import pubsub_v1
import json
def publish_to_pubsub(data):
publisher = pubsub_v1.PublisherClient()
topic_path = publisher.topic_path('your-project-id', 'your-topic-name')
data = json.dumps(data).encode('utf-8')
future = publisher.publish(topic_path, data)
future.result()
def handle_webhook(request):
if request.method == 'POST':
payload = request.get_json()
publish_to_pubsub(payload)
return 'Webhook received and processed', 200
else:
return 'Invalid request', 400
```
Adjust the code to your specific server setup and programming language.
Finally, test the entire setup by making a change in your GitLab repository that triggers the webhook. Monitor your server for incoming requests and verify that the data is successfully published to Google Pub/Sub. You can check the Pub/Sub console for messages in your topic to confirm successful data transfer.
By following these steps, you can effectively move data from GitLab to Google Pub/Sub without relying on third-party connectors.
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.
GitLab is web-based Git repository manager. Whereas GitHub emphasizes infrastructure performance, GitLab’s focus is a features-oriented system. As an open-source collaborative platform, it enables developers to create code, review work, and deploy codebases collaboratively. It offers wiki, code reviews, built-in CI/CD, issue-tracking features, and much more.
GitLab's API provides access to a wide range of data related to a user's GitLab account and projects. The following are the categories of data that can be accessed through GitLab's API:
1. User data: This includes information about the user's profile, such as name, email, and avatar.
2. Project data: This includes information about the user's projects, such as project name, description, and visibility.
3. Repository data: This includes information about the user's repositories, such as repository name, description, and access level.
4. Issue data: This includes information about the user's issues, such as issue title, description, and status.
5. Merge request data: This includes information about the user's merge requests, such as merge request title, description, and status.
6. Pipeline data: This includes information about the user's pipelines, such as pipeline status, duration, and job details.
7. Job data: This includes information about the user's jobs, such as job status, duration, and artifacts.
8. Group data: This includes information about the user's groups, such as group name, description, and visibility.
Overall, GitLab's API provides access to a comprehensive set of data that can be used to automate and streamline various aspects of a user's GitLab workflow.
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: