Data Connectors for Google Sheets
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.
- Pass. Connectors are included in the 14-day trial with 50 action credits. A pass is needed after the trial.
- Permission. The token or database user needs read access to everything you intend to pull and write access only if you plan to send changes back. The Salesforce profile only needs read access.
- Destination. Each pull writes to Flookup Staging. Keep your own analysis on a separate tab, because pulling again clears that sheet.
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
- Connect the source. Add an Airtable token, a SQL connection or a Salesforce Connected App in the sidebar. Credentials stay with your Google account.
- 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.
- 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
Airtable
Pull a base and table with a personal access token, keep record ids for safe updates and write changed fields back in batches.
SQL Database
PostgreSQL, MySQL, Microsoft SQL Server and Oracle through Apps Script's JDBC service, with a read-only query and a key column for write-back.
Salesforce
Connect with OAuth through a Connected App, pick objects and fields, run a SOQL query and pull records into the staging sheet. Read only in this version.
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:
- Clean an Airtable base in a sheet where the whole table is visible at once. Airtable dedupe walkthrough
- Deduplicate Salesforce leads and contacts before a merge, then review the groups in the staging sheet. Salesforce dedupe walkthrough
- Reconcile orders, invoices or supplier records against a database query. Order reconciliation guide
- Follow a full operations month across Airtable, SQL and Salesforce, from the first pull to the Airtable and SQL write back. Data connectors case study
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.
- New rows: staged rows with no matching source record are inserted.
- Changed rows: only the fields that differ are sent, so untouched columns are not overwritten.
- Unchanged rows: compared field by field and skipped entirely.
- Missing rows: source records that are not in the staging sheet are left alone. Nothing is deleted.
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.
- The schedule uses the connector settings saved at run time, so changing the base, table or query changes the next pull.
- Each run replaces the staging sheet. Anything you edited there is replaced, so keep cleaned results on another tab.
- Write-back is never automatic. A scheduled pull only reads from the source.
- The card shows the last run, its status and the next run time. A failed run records the error there.
- Each run checks your pass. If it has expired, the run is skipped and the card records why. Pulls resume when the pass is active again.
- A failed run records the error and emails you. A repeated failure sends at most one notice every 12 hours and a successful run resets the count.
- Saving a different connector or clearing the current one removes the schedule.
- Each run is limited to 25,000 rows on a pass (5,000 on the trial), the same as a manual pull.
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.