Connect File URL / CSV to Google Sheets
Read a CSV, TSV, JSON, JSON Lines or Excel file straight from a URL (or your stored files). Handles gzip/zip and picks the format automatically. Great for vendor exports dropped at a link.
What you can pull from File URL / CSV
A File URL / CSV job pulls records into a flat table on your schedule. Nested fields are flattened into ordinary columns, so what lands in Google Sheets is ready to sort, filter and total rather than needing another cleanup step.
- CSV / TSV / JSON / Excel
- Auto format & compression
- Public URL or stored file
Options you can set
- location
- 'http' for a URL, 'storage' for a file in your account — defaults to
http - file_format
- auto, csv, tsv, delimited, json, jsonl or excel — defaults to
auto - compression
- auto, none, gzip, zip, bz2 or xz — defaults to
auto - has_header
- First row holds column names (delimited only) — defaults to
true - skip_rows
- Rows to skip before the header, for files with a preamble — defaults to
0 - encoding
- For files that are not UTF-8 — defaults to
utf-8 - max_rows
- Cap the rows a run reads
How it lands in Google Sheets
Google Sheets accepts append and overwrite writes. Overwrite replaces the target range, which suits a snapshot; append adds rows underneath, which suits a log you are accumulating. There is no upsert here, so rows are added or replaced rather than merged.
- Append adds rows below existing content; overwrite replaces the target range.
- No upsert: a spreadsheet has no primary key, so there is nothing to merge on. Use Airtable or Postgres if rows must be updated in place.
- Google caps a spreadsheet at 10 million cells across all tabs. Filter before writing rather than after.
Authentication
No credential is needed for a public URL. If the file is not publicly reachable, upload it to your account storage and read it from there instead.
Keeping runs incremental
Not for this source: The whole file is re-read each run. Where that is expensive, narrow the job itself and run it less often.
Because Google Sheets has no upsert, decide what a re-run should mean before you schedule it. Overwrite keeps a current snapshot; append accumulates history and will grow without bound.
Limits and pacing
These are the provider-side ceilings that shape a schedule, not ours. Knowing them up front is the difference between a job that runs quietly every morning and one that starts failing the week your data grows.
| Limit | Value | Applies to |
|---|---|---|
| File size Streamed rather than loaded whole, so the cap is about the pipeline. | 256 MB | File URL / CSV |
| Redirect hops The destination is re-validated at every hop. | 5 | File URL / CSV |
Common gotchas
Most of what goes wrong with a scheduled sync is not a bug — it is a detail of how one side behaves that nobody wrote down. These are the ones that come up for this pair.
Format detection trusts the extension first
Then the Content-Type header. Override it explicitly when a URL lies about what it serves, which happens more often than it should.
The link must return the current file
A URL that returns yesterday's export forever will sync perfectly and tell you nothing. This is the most common cause of a job that looks healthy but reports stale numbers.
An open-ended range beats a padded one
Writing to A2:D is better than A2:D1000 for appends: the padded form reserves rows you may not need and makes the append boundary ambiguous.
Set it up in four steps
- 1
Connect File URL / CSV
A public HTTPS link, or a file in your own account storage. No credential needed for a public URL.
- 2
Connect Google Sheets
Connect your Google account once. Paste a spreadsheet URL or ID.
- 3
Shape the data
Select the columns you want, filter rows, cast types and add computed fields. Everything else is dropped before it reaches the destination.
- 4
Schedule it
Run once, or on a cron. Every run refreshes Google Sheets with the latest File URL / CSV data.
Do I need an add-on or extension for this?
No. The job runs server-side and writes into Google Sheets through its API, so there is nothing installed in the spreadsheet itself. It keeps running when nobody has the file open, and a copy of the file does not need anything installed to work.
How often does the data refresh?
On whatever schedule you set with a cron expression — hourly, daily, or a specific time on specific days. Each run pulls the latest from File URL / CSV.
Do I need to write any code?
No. You connect both sides, map the fields in a wizard and set a schedule. Computed fields accept small expressions — abs, round, min, max, len — but there is nothing to host or maintain.
Does the file have to be public?
No. A public HTTPS link works with no credential, but you can also upload the file to your account storage and read it from there when it is not publicly reachable.
What happens if the URL redirects?
Up to five hops are followed, and the destination is re-validated at every one. A link that later starts redirecting somewhere internal does not quietly become a request to somewhere it should not go.
Do I have to give access to my whole Google Drive?
No. Only the spreadsheets scope is requested. The Drive scope that most spreadsheet tools ask for is a restricted scope granting read access to every file you own; it is deliberately not requested here, which is why you paste a spreadsheet URL rather than browsing Drive.
Will this keep working if I copy the sheet?
The job writes to a specific spreadsheet ID, so a copy will not receive data until you point a job at it. Nothing is installed in the file itself, though, so copying never breaks the original.
Is the File URL / CSV connector free to use?
You can connect File URL / CSV and start syncing on the free plan.
Other sources into Google Sheets
Related reading
Airtable upsert: stop creating duplicate records
Appending on every run turns a tidy base into six copies of every row. Here is how upsert works in Airtable, and how to choose a merge key that holds up.
Export Stripe data to Google Sheets
Stripe's dashboard exports are manual and stale the moment you download them. Here is how to keep customers, invoices and charges fresh in a sheet instead.
Import a CSV from a URL into Airtable
Point a job at a CSV link and it re-reads it on your schedule — no download, no manual import. Here is the setup, and the field-type trap to avoid first.