Pull container milestones from a tracking API with UrlFetchApp and update Sheet statuses. The workbook becomes the system of record; Apps Script owns the joins and business rules so analysts are not pasting monthly formulas.
Entry point `syncContainerTracking` reads typed columns with SpreadsheetApp batch APIs. UrlFetchApp is the primary service; Time-driven describes how you usually invoke it after authorization.
Keep thresholds (grace days, bands, alert emails, API keys) in Config cells or Script Properties so the same .gs file promotes from sandbox to production without code edits.
This page is technical only: sheet layout, edge cases, runnable code, deploy steps, and FAQs for sync container tracking via urlfetch. No consulting pitch—just the pattern you can paste and harden.
Need this built? Hire a Google Apps Script developer →
Sheet / project setup
| Tab | Columns | Notes |
|---|---|---|
| Containers | Container + milestone cols | Updated by API |
What this script does
syncContainerTracking() pull container milestones from a tracking API with UrlFetchApp and update Sheet statuses.
- Bearer API key
- Milestone JSON
- Skip DELIVERED
Prerequisites
Container-bound script on the workbook that contains the tabs in the setup table. Authorize UrlFetchApp scopes on first run.
- V8 runtime
- Exact sheet names
- Script timezone = ops timezone
Walkthrough
For non-DELIVERED containers, UrlFetch tracking API, parse JSON milestones into Sheet columns.
Paste the code, set Config/Properties, run syncContainerTracking once, verify the output tab, then attach a Time-driven trigger.
Edge cases
Non-200 API responses skip that container without failing the whole batch.
Testing
Use a sandbox copy with 3–5 known rows. Compute expected outputs for sync container tracking via urlfetch offline, run syncContainerTracking, and diff the output tab including one intentional bad row.
Hardening
Add LockService around multi-sheet writes if triggers can overlap. Log run timestamps. Keep API keys and alert emails in PropertiesService—not in shared cells.
Variations
Fork ideas: filter to one business unit, change grain (daily→weekly), or POST a summary payload after syncContainerTracking succeeds.
Operations notes
Assign an owner for the output tab, document regenerate steps, and treat `syncContainerTracking` as source of truth over ad-hoc cell formulas.
Full code: syncContainerTracking()
Run syncContainerTracking when source tabs are current. Edit sheet names and Config/Properties first.
function syncContainerTracking(){
const props=PropertiesService.getScriptProperties();
const endpoint=props.getProperty('TRACK_API_URL');
const key=props.getProperty('TRACK_API_KEY');
const ss=SpreadsheetApp.getActive();
const sh=ss.getSheetByName('Containers');
const data=sh.getDataRange().getValues();
for(let i=1;i<data.length;i++){
const cn=String(data[i][0]);
if(!cn|| String(data[i][5]).toUpperCase()==='DELIVERED') continue;
const url=endpoint+'?container='+encodeURIComponent(cn);
const res=UrlFetchApp.fetch(url,{headers:{Authorization:'Bearer '+key}, muteHttpExceptions:true});
if(res.getResponseCode()!==200) continue;
const json=JSON.parse(res.getContentText());
data[i][2]=json.lastEvent||data[i][2];
data[i][3]=json.location||data[i][3];
data[i][4]=json.eventTime? new Date(json.eventTime): data[i][4];
data[i][5]=json.status||data[i][5];
}
sh.getRange(2,3,data.length,6).setValues(data.slice(1).map(r=>[r[2],r[3],r[4],r[5]]));
}- Line 1: Entry point — bind triggers to syncContainerTracking.
- Line 2: Script Properties for thresholds/secrets.
- Line 7: Batch read; avoid per-cell getValue in loops.
- Line 12: HTTP integration; muteHttpExceptions recommended.
- Line 20: Batch write output rows in one setValues call.
Deploy this example
- 01
Open Apps Script
In the bound spreadsheet: Extensions → Apps Script. For standalone projects, create one at script.google.com and link your Sheet by ID.
- 02
Paste and save
Add a .gs file, paste the code below, rename constants at the top (sheet names, column letters, API property keys), then save.
- 03
Authorize once
Run the main function from the editor. Accept OAuth scopes when prompted — triggers cannot run until authorization succeeds once.
- 04
Add the trigger
Triggers → Add trigger → choose the handler function and event (time-driven, on edit, or on form submit). Delete test triggers before production.
Before you run: sync container tracking via urlfetch
- 1Setup tabs exist with headers matching syncContainerTracking
- 2Dry-run on a copy workbook
- 3Timezone verified
- 4UrlFetchApp authorization completed
- 5Output spot-checked against hand calc
- 6Time-driven trigger added only after validation
- 7Owners + alert recipients documented
Frequently asked questions
At minimum the tabs listed in the setup table for Sync Container Tracking via UrlFetch. Output tabs may be cleared each run—do not store source-of-truth data there.
Run from the Apps Script editor for dry runs. Production usually uses a Time-driven trigger after OAuth succeeds once.
Non-200 API responses skip that container without failing the whole batch.
Per-cell calls burn quota and wall time. One read + one write keeps this pattern under the 6-minute execution cap longer.
PropertiesService (Script Properties) for API keys and alert inboxes. Config sheet is fine for non-secret thresholds.
Simple ratios maybe; sync container tracking via urlfetch needs joins, branching, or side effects (email/Docs/API) that Apps Script handles cleanly.
Keep the .gs in clasp/git. Avoid divergent copies of formulas on the output tab—regenerate from the script.