Skip to main content
Source components define where your ETL pipeline reads data from. Integrate.io supports databases (PostgreSQL, MySQL, Redshift, BigQuery, Snowflake), SaaS platforms (Salesforce, HubSpot, Google Ads, Facebook Ads), file storage (S3, SFTP, Google Drive), and REST APIs. Each guide covers connection setup and component configuration.

Amazon Redshift

Bing Ads

Database

Dummy Source

Facebook Ads Insights

File Storage

Google Ads

Google Analytics

Google Analytics 4 (GA4)

Google BigQuery

Google Cloud Spanner

MongoDB

NetSuite

REST API

Salesforce

Snowflake

Crisp Chat

Gmail

Google Sheets

SharePoint

Mouseflow

SugarCRM

Zendesk

Amazon Athena

Amazon RDS

Amazon S3

DB2

Dynamics 365

FTPS

Google Cloud SQL for MySQL

Google Cloud SQL for PostgreSQL

Google Cloud Storage

Google Drive

Google Sheets

Google Sheets (Service Account)

HDFS

Heroku Postgres

Gmail

HubSpot

HubSpot (Service Token)

IBM i (AS/400)

Instagram

Intercom

LinkedIn

Marketing Cloud (REST)

Marketing Cloud (SOAP)

Microsoft SQL Server

MySQL

Oracle

PostgreSQL

SAP HANA

SFTP

SFTPToGo

SharePoint

Shopify

TikTok Ads

Universal OAuth

Xero

YouTube

Windows File Share

API Ingestion Guide

Ingesting a Postman API Call

Moving Data Incrementally Between Databases

Reading File Storage Data Incrementally

Salesforce Objects Reference

Salesforce PK Chunking

Selecting File Input Format

API Endpoints with Pagination

Pattern Matching in Source Paths

​
Snapshot CDC Sources

Read only changed records from a database using a Snapshot CDC source component. Each database has its own connector; see the Snapshot CDC Source overview for the shared configuration, storage, and change detection reference.

Snapshot CDC Overview

MySQL

PostgreSQL

SQL Server

Oracle

Oracle ADW

Amazon Redshift

Snowflake

Google Cloud SQL

Google Cloud Postgres

Heroku Postgres

AlloyDB

Vertica

Azure Synapse Analytics

IBM DB2

SAP HANA

Last modified on June 29, 2026