

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
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


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


“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.”

"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, ensure you have a Google Cloud Project set up. If not, create one in the [Google Cloud Console](https://console.cloud.google.com/). Enable billing and make sure you have access to the necessary Google Cloud services like Google Cloud Storage (GCS) and Google Pub/Sub.
In your Google Cloud Project, enable the necessary APIs: Google Cloud Storage API and Google Pub/Sub API. You can do this from the APIs & Services section in the Google Cloud Console by searching for these APIs and enabling them.
Navigate to the Google Cloud Storage section in the Console and create a new bucket or use an existing one. Upload the data files you wish to transfer to Pub/Sub into this bucket. Ensure that the bucket permissions allow reading of the files you want to process.
In the Pub/Sub section of the Google Cloud Console, create a new topic that will be used to publish messages. This topic will hold the data coming from your GCS bucket. Make sure to note the topic's unique identifier, as it will be used in your script or application.
Go to the Cloud Functions section and create a new function. Configure this function to trigger whenever a new file is created in your GCS bucket. Set the event type to "Cloud Storage" and the event "Finalize/Create". This function will contain the logic to publish the file data to the Pub/Sub topic.
In the Cloud Function editor, write the code that reads the file from GCS and publishes its content to the Pub/Sub topic. Use the Google Cloud client libraries for Node.js, Python, or your preferred language. Make sure your code includes proper error handling and logging for debugging purposes.
Example in Python:
```python
import base64
from google.cloud import pubsub_v1
from google.cloud import storage
def gcs_to_pubsub(event, context):
# Initialize clients
storage_client = storage.Client()
pubsub_client = pubsub_v1.PublisherClient()
# Retrieve bucket and file information
bucket_name = event['bucket']
file_name = event['name']
# Access the file from the bucket
bucket = storage_client.get_bucket(bucket_name)
blob = bucket.blob(file_name)
file_data = blob.download_as_bytes()
# Specify the Pub/Sub topic
topic_path = pubsub_client.topic_path('your-project-id', 'your-topic-id')
# Publish the file data to the Pub/Sub topic
future = pubsub_client.publish(topic_path, data=file_data)
future.result() # Ensure the publish is complete
print(f'File {file_name} from {bucket_name} sent to {topic_path}.')
```
Deploy your Cloud Function with the appropriate settings and permissions. Ensure that the service account running the function has sufficient permissions to read from GCS and publish to Pub/Sub. After deployment, upload a new file to the GCS bucket and check the Pub/Sub topic to verify that the data is being successfully published. Monitor logs in the Cloud Functions section for any errors or issues.
By following these steps, you can move data from Google Cloud Storage to Google Pub/Sub using native Google Cloud services and tools, without the need for third-party connectors or integrations.
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.
Google Cloud Storage is a cloud-based storage service that allows users to store and access their data from anywhere in the world. It provides a highly scalable and durable storage solution for businesses and individuals, with features such as automatic data replication, versioning, and access control. Google Cloud Storage offers different storage classes to suit different needs, including multi-regional, regional, nearline, and coldline storage. It also integrates with other Google Cloud services, such as BigQuery and Cloud Functions, to enable data analysis and processing. Overall, Google Cloud Storage provides a reliable and flexible storage solution for businesses of all sizes.
Google Cloud Storage's API provides access to various types of data, including:
1. Object data: This includes files and other data objects stored in Google Cloud Storage buckets.
2. Metadata: This includes information about the objects stored in the buckets, such as their size, creation date, and content type.
3. Access control data: This includes information about who has access to the objects stored in the buckets and what level of access they have.
4. Bucket data: This includes information about the buckets themselves, such as their name, location, and storage class.
5. Logging data: This includes information about the activity in the buckets, such as who accessed them and when.
6. Transfer data: This includes information about data transfers to and from the buckets, such as the amount of data transferred and the transfer speed.
Overall, the Google Cloud Storage API provides access to a wide range of data related to object storage and management in the cloud.
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: