Connect external data via Apps Script

Connect external data via Apps Script in Google Sheets — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need an Apps Script that pulls the sales CRM JSON feed every 10 minutes and writes it into a…
I need an Apps Script that pulls the sales CRM JSON feed every 10 minutes and writes it into a sheet called CRM_Ingest, appending new rows and de-duplicating by Deal ID. Schedule the trigger, include exponential backoff for failed fetches, and log the last successful pull timestamp into a cell on the sheet. Verify the script runs under my account and report any permission scopes it needs.

Improve — make it easier to accept

+
Before I deploy the Apps Script to run nightly, harden it for the contract team. Surface the points…
Before I deploy the Apps Script to run nightly, harden it for the contract team. Surface the points where it can fail silently: API timeouts, auth token expiry, schema changes in the JSON payload, and quota limits. Add retry logic, a compact error summary written to an Errors sheet, and a clear place to drop a new API key so non-developers can rotate credentials without editing code.

Decide — diagnose the stuck moment

+
My nightly ingest triggered but the log shows a 401 Unauthorized on the first fetch. I updated the…

scheduled script failed with 401

My nightly ingest triggered but the log shows a 401 Unauthorized on the first fetch. I updated the API key two days ago but I’m not sure if the script uses a cached key, an old stored property, or a different credential store. I can share the script file name, when I rotated the key, and the error text. What likely went wrong and what precise steps will get the job running tonight?

Become — change the pattern

+
We have five small Apps Scripts across projects and every token rotation or API change becomes a…

maintaining many scripts eats time

We have five small Apps Scripts across projects and every token rotation or API change becomes a firefight. I own platform ops. Which concise practices—how to store credentials, how to deploy triggers, and how to audit runs—would reduce incidents and handoffs so the scripts require minimal maintenance while staying secure?

Next to this one

Other spreadsheet work people do in Google Sheets.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.