

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


"The intake layer of Datadog’s self-serve analytics platform is largely built on Airbyte.Airbyte’s ease of use and extensibility allowed any team in the company to push their data into the platform - without assistance from the data team!"


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


“We chose Airbyte for its ease of use, its pricing scalability and its absence of vendor lock-in. Having a lean team makes them our top criteria. The value of being able to scale and execute at a high level by maximizing resources is immense”
1.1 Create a Connected App in Salesforce
- Log in to your Salesforce account.
- Go to Setup.
- In the Quick Find box, type "App Manager" and select it.
- Click on "New Connected App".
- Fill in the necessary details such as the name, API name, and contact email.
- Enable OAuth settings and set the callback URL (you can use `http://localhost` for development purposes).
- Choose the OAuth scopes required for your application (at minimum, you will need "Access and manage your data (api)").
- Save the new connected app and take note of the Consumer Key and Consumer Secret.
1.2 Authenticate and Get Access Token
- Send an OAuth authentication request to Salesforce's token endpoint using your connected app's credentials.
- You can use tools like Postman or write a script in a language like Python to make the HTTP request.
- The request will return an access token that you will use to make API calls to Salesforce.
1.3 Use Salesforce REST API to Query Data
- Use the access token to authenticate your API requests.
- Use the Salesforce REST API's query endpoint to run SOQL queries and extract the data you need.
- The endpoint will look something like this: `https://yourinstance.salesforce.com/services/data/vXX.0/query/?q=SELECT+fields+FROM+object`.
- Replace `yourinstance` with your Salesforce instance, `vXX.0` with the API version, `fields` with the fields you want to retrieve, and `object` with the Salesforce object you are querying.
- Parse the JSON response to extract the data.
2.1 Create a New Google Sheet
- Log in to your Google account and open Google Sheets.
- Create a new sheet where you will insert the Salesforce data.
2.2 Get Google Sheets API Access
- Go to the Google Developers Console.
- Create a new project or select an existing one.
- Enable the Google Sheets API for your project.
- Create credentials for your project (OAuth client ID).
- Download the JSON file with your credentials.
- Use the credentials to authenticate your application with Google's OAuth 2.0.
3.1 Authenticate with Google Sheets API
- Use the credentials JSON file to authenticate your script or application with the Google Sheets API.
- The authentication process will provide you with an access token to make API requests.
3.2 Use Google Sheets API to Insert Data
- Use the Google Sheets API to select the sheet and the range where you want to insert the data.
- Format the data from Salesforce to match the structure expected by the Google Sheets API.
- Make an HTTP request to the Google Sheets API to insert the data into the specified range.
- Handle the API response and check for errors.
If you need to move data regularly, you could automate the process by writing a script that runs at scheduled intervals (e.g., daily, weekly).
- Write a script that encapsulates the steps above.
- Schedule the script using a scheduler like cron (for Linux/Mac) or Task Scheduler (for Windows).
- Make sure the script logs its activity and can handle errors gracefully.
Final Notes
- Always ensure you handle sensitive information, such as access tokens and client secrets, securely.
- Respect API limits and quotas for both Salesforce and Google Sheets to avoid service disruptions.
- Test your setup thoroughly before relying on it for production data.
Please note that this guide assumes you have a developer background and are comfortable with concepts like OAuth, API usage, HTTP requests, and programming/scripting in general. If you're not, you might want to consider using a third-party integration tool or seeking assistance from a developer.
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.
Salesforce is a cloud-based customer relationship management (CRM) platform providing business solutions software on a subscription basis. Salesforce is a huge force in the ecommerce world, helping businesses with marketing, commerce, service and sales, and enabling enterprises’ IT teams to collaborate easily from anywhere. Salesforces is the force behind many industries, offering healthcare, automotive, finance, media, communications, and manufacturing multichannel support. Its services are wide-ranging, with access to customer, partner, and developer communities as well as an app exchange marketplace.
Salesforce's API provides access to a wide range of data types, including:
1. Accounts: Information about customer accounts, including contact details, billing information, and purchase history.
2. Leads: Data on potential customers, including contact information, lead source, and lead status.
3. Opportunities: Information on potential sales deals, including deal size, stage, and probability of closing.
4. Contacts: Details on individual contacts associated with customer accounts, including contact information and activity history.
5. Cases: Information on customer service cases, including case details, status, and resolution.
6. Products: Data on products and services offered by the company, including pricing, availability, and product descriptions.
7. Campaigns: Information on marketing campaigns, including campaign details, status, and results.
8. Reports and Dashboards: Access to pre-built and custom reports and dashboards that provide insights into sales, marketing, and customer service performance.
9. Custom Objects: Ability to access and manipulate custom objects created by the organization to store specific types of data.
Overall, Salesforce's API provides access to a comprehensive set of data types that enable organizations to manage and analyze their customer relationships, sales processes, and marketing campaigns.
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: