06:00 UTC













Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Enter the Azure SQL server host, database, and login details. Catchr verifies the destination before any marketing data is exported.
Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your AzureSQL table.
Open the dedicated route for each platform. Its field catalog, reporting grain, historical constraints, and warehouse use cases should be specific to that source.
Answers about AzureSQL setup, available source data, schedules, table updates, and SQL use cases.
Add your Airtable personal access token, save the Azure SQL connection details, and pair both systems in a datastream. Catchr discovers Airtable data as Base / Table pairs so you can select the table to load.
Select fields from the chosen Airtable table, rename the destination columns if needed, preview the result, and write the data to Azure SQL. Numeric, boolean, and date-like values retain suitable data types.
Catchr maps discovered Airtable fields by their field IDs rather than display names, helping the Azure SQL mapping remain stable when someone renames a field in Airtable.
Linked records, attachments, and multi-select arrays are preserved as JSON strings when Catchr loads them into Azure SQL, while scalar values remain easier to query as native types.
The associated job can begin with a historical Airtable fetch and continue on a recurring schedule. Available history and frequency depend on the Airtable API and your Catchr plan.
Yes. Connect an existing Azure SQL database first. The Catchr job creates and populates the destination table you configure inside that database.
Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.
Our teams is always here to responds to any question you could have about our data connector.