ChatGPT in Google Sheets Without Paying for an Add-On

You can use ChatGPT in Google Sheets with about twenty lines of Apps Script and no add-on at all. The code is the easy part and most tutorials cover it adequately.

What they leave out is the constraint that decides whether this works for you: Google gives custom functions thirty seconds to return, and filling one down a thousand rows fires a thousand simultaneous API calls.

What It Costs Before You Start

This is the number that decides whether the whole exercise makes sense, and it is smaller than most people assume.

For a typical spreadsheet task such as classifying a short piece of text, each row uses roughly a hundred input tokens and a handful of output tokens. On gpt-5-nano that works out at approximately one cent per thousand rows.

Worth putting beside a subscription. If your use is a few thousand rows a month, the API route costs a few cents where an add-on costs a monthly fee or a lifetime deal price. If your use is far larger, the calculation changes and you should do it properly rather than assuming.

The Script

Open your sheet, then Extensions, then Apps Script. Delete whatever is in the editor and paste this.

function GPT(prompt) {
  const key = PropertiesService.getScriptProperties()
                .getProperty('OPENAI_API_KEY');
  if (!key) return 'No API key set';

  const res = UrlFetchApp.fetch(
    'https://api.openai.com/v1/chat/completions', {
      method: 'post',
      contentType: 'application/json',
      headers: { Authorization: 'Bearer ' + key },
      payload: JSON.stringify({
        model: 'gpt-5-nano',
        messages: [{ role: 'user', content: prompt }]
      }),
      muteHttpExceptions: true
    });

  const data = JSON.parse(res.getContentText());
  if (data.error) return 'Error: ' + data.error.message;
  return data.choices[0].message.content.trim();
}

Save it. That is the whole function. Two details in it matter more than the rest.

The key is not in the code

The function reads the key from Script Properties rather than having it typed into the script. To set it, go to Project Settings in the Apps Script editor, scroll to Script Properties, and add a property named OPENAI_API_KEY with your key as the value.

Never paste a real key into the code itself. A key in the script body ends up in every copy of the sheet anyone makes, and in any version history.

Errors return text rather than throwing

The muteHttpExceptions option and the error check mean a failed call puts a readable message in the cell instead of a generic failure. When something goes wrong at row 400, you want to know whether it was a rate limit or a bad key.

Using It

In any cell, call it like a normal function. The prompt is just text, so you build it by joining a fixed instruction to a cell reference.

Telling it what shape the answer should take matters far more here than in a chat window. A cell wants one value, so ask for one word or one line, and say what to do when it does not know.

The Thirty-Second Limit, and Why Fill-Down Fails

This is the part that turns a working demonstration into a frustrating afternoon, and Google documents it plainly.

A custom function call must return within thirty seconds. If it does not, the cell shows #ERROR! and a note reading exceeded maximum execution time. That is fine for one cell and a serious problem for a thousand.

Fill the formula down a large column and Sheets fires all those calls at once. Many will queue behind rate limits, exceed the thirty seconds, and error. You end up with a column of mixed results and errors, and no obvious way to retry only the failures.

The working approach

• Fill in batches. Fifty rows at a time, wait for them to resolve, then copy that block and paste it back over itself as values.
• Convert to values as you go. This is not optional. A custom function recalculates, and every recalculation is a fresh API call you pay for again.
• Then move to the next batch. Slower than one fill-down, and it actually finishes.

If you genuinely need thousands of rows regularly, a custom function is the wrong shape for the job. A menu-driven script that processes rows in a controlled loop and writes results directly is the right answer, and at that point a paid add-on that has already solved batching may be worth the money.

Troubleshooting

Four failures account for nearly everything that goes wrong here, and each has a distinct symptom.

The last row is worth a guard in the function. If your source column has blanks, you are paying for calls that ask the model to classify nothing. Adding a check that returns an empty string when the prompt is empty costs one line and stops that.

Other Limits Worth Knowing

Google documents several restrictions on custom functions beyond the time limit. Three of them affect this use directly.

Custom functions cannot change other cells

A custom function returns a value into its own cell and nothing else. It cannot write to a neighbouring column, add a sheet or format anything. If you want results written into a range, that needs a menu-driven script rather than a formula.

Volatile functions cannot be arguments

You cannot pass NOW() or RAND() into a custom function. This rules out anything that asks the model to work with the current time, which surprises people building anything date-aware.

Authorization-dependent services are unavailable

Custom functions never prompt for authorization, so they can only call services that do not touch personal data. UrlFetchApp is explicitly permitted, which is why this approach works at all. Reading another spreadsheet from inside the function is not.

There is also a wrinkle with properties. Google notes that getUserProperties only returns the spreadsheet owner’s properties, and editors cannot set user properties from a custom function. That is precisely why the script above uses Script Properties instead.

Script or Add-On

The honest comparison, since this article exists partly because add-ons dominate the search results.

The script is cheaper by a wide margin and gives you control over which model runs. The add-on removes exactly the parts that irritate people: managing a key, handling batching, retrying failures, and having someone to ask when it breaks.

If you would rather buy the convenience, the SheetMagic ChatGPT integration is one of the established options and available as a lifetime deal. Compare its cost against a few cents of API usage honestly before deciding, because for light use the script is hard to beat.

Common Questions

The Short Version

API pricing and Apps Script limits checked against OpenAI’s and Google’s own documentation on 30 August 2026.