DiscoveryVIP / Apps Script AcademyHelp

72. Web applications with doGet

Module 15 · 20 minutes · Lesson 71; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use web applications with doget without changing the wrong data?

Predict

Which values or resources will change, and which should stay unchanged? Write your prediction before execution.

Understand

A web app entry point returns HtmlOutput or TextOutput. The event argument can contain request parameters; it is not an edit event. Deploying does not make every server function safe to expose. Keep secrets on the server, avoid returning tokens and review which identity accesses the data.

Example 1: Working automation

Returning the output object is essential; defining or constructing it without return produces undefined.

function main() {
  console.log(doGet().getContent());
}
function doGet() {
  return HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(doGet().getContent());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function doGet() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: return HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
End this function and pass its value to the caller; logging alone does not return a result.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "<h1>Task workshop</h1><p>Ready to learn.</p>"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 2: Investigate a reproducible failure

Predict the effect of HtmlService and identify the first mismatch. This example is intentionally faulty.

function main() {
  console.log(doGet().getContent());
}
function doGet() {
  HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(doGet().getContent());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function doGet() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": "Cannot read properties of undefined (reading 'getContent')",
  "resource": "logs",
  "value": null
}

Example 3: Separate setup from execution and inspect repeat behavior

Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.

function lessonAction() {
  console.log(doGet().getContent());
}
function doGet() {
  return HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
}
function main() {
  lessonAction();
  lessonAction();
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(doGet().getContent());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function doGet() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: return HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
End this function and pass its value to the caller; logging alone does not return a result.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 7: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 8: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 9: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 10: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "<h1>Task workshop</h1><p>Ready to learn.</p>",
    "<h1>Task workshop</h1><p>Ready to learn.</p>"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 4: Add a diagnostic boundary around the operation

Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.

function lessonAction() {
  console.log(doGet().getContent());
}
function doGet() {
  return HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
}
function main() {
  console.log("Start: Web applications with doGet");
  try { lessonAction(); console.log("Completed operation"); }
  catch(error) { console.error("Failed operation: " + error.message); throw error; }
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log(doGet().getContent());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 4: function doGet() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 5: return HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
End this function and pass its value to the caller; logging alone does not return a result.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 7: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 8: console.log("Start: Web applications with doGet");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 9: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 10: catch(error) { console.error("Failed operation: " + error.message); throw error; }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 11: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Web applications with doGet",
    "<h1>Task workshop</h1><p>Ready to learn.</p>",
    "Completed operation"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Build and test

Repair the supplied script so that: Returning the output object is essential; defining or constructing it without return produces undefined. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  console.log(doGet().getContent());
}
function doGet() {
  HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
}

Graduated hints

Hint 1

Inspect the operation containing HtmlService. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns return HtmlService. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses return HtmlService where the broken source uses HtmlService. Explain why before applying it.

Reference solution

function main() {
  console.log(doGet().getContent());
}
function doGet() {
  return HtmlService.createHtmlOutput("<h1>Task workshop</h1><p>Ready to learn.</p>").setTitle("Task workshop");
}

Explain and reflect

Which operation proves the intended result in web applications with doget? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the calculation or validation to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.

Troubleshooting

If the console is empty, inspect the logs preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Use Manual unless investigating a trigger. Changing input data also changes the expected result; restore sample data before the authored checks.

Knowledge check

Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.

Optional AI practice

Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.

Transfer to Google and authorization guide

Next lesson: HTML, CSS and client JavaScript