Data Connectors for Google Sheets

On This Page

Introduction

Most spreadsheet work starts with an export. Data Connectors remove that step. Pull an Airtable table, a SQL query result or a Salesforce object into Flookup Staging inside your own spreadsheet, clean it with Flookup custom functions or Data Cleaning Automation, then send back only the rows you changed, after a preview.

Nothing is exported to a file, nothing is re-imported and no record is deleted. Credentials stay with your Google account and the pulled rows stay in your spreadsheet.

What makes this different. Write-back sends only the fields that differ, never the whole row and rows missing from the staging sheet are left alone. A preview lists the new, changed and unchanged rows before anything is sent.

Open the sidebar from Extensions > Flookup Data Wrangler > Data Connectors.

Worked example. The pull, clean, preview and apply cycle across Airtable, SQL and Salesforce is shown in Data Connectors Case Study for Google Sheets.


Before You Begin

Three things decide whether a pull succeeds: your pass, your permission on the source and where the rows land.

A one-off look at a source is usually faster as a CSV export. Connectors pay off when the same source is pulled repeatedly or when cleaned rows have to return without a manual re-import.


How It Works

  1. Connect the source. Add an Airtable token, a SQL connection or a Salesforce Connected App in the sidebar. Credentials stay with your Google account.
  2. Pull to staging. Choose the base and table, run a read-only query or pick a Salesforce object. Up to 25,000 rows per run on a pass (5,000 on the trial) land in Flookup Staging with a bold header row.
  3. Clean, then write back. Run Custom function data cleaning on the staging sheet. When you are ready, preview the differences against the source and confirm the write.

Pulling again replaces the staging sheet. Write-back never deletes source records.


Available Connectors

Every connector writes into a hidden staging sheet, so cleaning and matching use the same tools as any other tab. Salesforce is read only; Airtable and SQL databases can send changed rows back.

Typical jobs:

Which connector fits

Source Sign-in Write-back Reach for it when
Airtable Personal access token Yes, changed fields only The base holds operational records and the same people report on them in a sheet.
SQL database JDBC URL with user and password Yes, through a key column The table is large, a query already narrows it and the key is stable enough to match on.
Salesforce OAuth through a Connected App No, read only Leads, contacts or custom objects need a cleanup pass before a merge or an import.

How Write-Back Works

Write-back compares the staging sheet with the live source and reports three numbers: new, changed and unchanged. A sample of the first rows is shown before anything is written.

The write only starts after you click Apply changes on the preview. Each run applies at most 500 changes and tells you when the cap stopped the rest.

Every applied change is appended to a Flookup Changes sheet with the timestamp, connector, target table, staging row, record id, action, field, before value and after value. The log is written after the source confirms the change, so an Airtable run that fails part way still records the batches that were written.


Automatic Pull

The Automatic pull card schedules the saved connector to refresh Flookup Staging on its own. Choose a daily time on a quarter hour or an interval from 1 to 24 hours and save the schedule. The schedule belongs to your account and the spreadsheet that was open when you saved it. Each run opens that spreadsheet, replaces the staging sheet with a fresh pull and records the result in the card.

This scene is separate from Data Cleaning Automation. Automation cleans ranges inside a sheet; Automatic Pull refreshes the staging sheet from the source. Keep both on their own schedules when a source should arrive and then be cleaned without an export.


Limits

Limit Value
Rows per pull 25,000 rows per run on a pass (5,000 on the trial). The pull reports when the cap stopped it.
Changes per write-back 500. Preview and apply again for the remainder.
SQL connections per day Google's JDBC quota applies to your account: 10,000 connections for consumer accounts, 50,000 for Workspace.
Airtable rate limit Flookup pauses between pages and honours rate-limit responses.

Credentials and Privacy

Tokens and database passwords are stored with the Google account that set them up. They are never returned to the sidebar and you can remove them with Clear in the connector card.

Pulled rows exist only in your spreadsheet. The connector calls the source API or database directly; Flookup does not receive a copy of your data.


Frequently Asked Questions

Does write-back delete records?

No. Write-back sends new rows and changed fields only. Rows that are missing from the staging sheet are left untouched in the source.

Where is the pulled data stored?

In a sheet called Flookup Staging inside your own spreadsheet. Credentials are stored with your own Google account and are never shown back in the sidebar.

Can I schedule connector pulls?

Yes. Use Automatic pull in the connector sidebar to refresh the staging sheet on a saved schedule. Write-back is never automatic.


Related guides