81. Gemini and AI-powered applications
Module 17 · 20 minutes · Lesson 80; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use gemini and ai-powered applications without changing the wrong data?
- Explain gemini and ai-powered applications in your own words
- Trace the actual console result from the source
- Repair the supplied failing operation and verify the result
Predict
Which values or resources will change, and which should stay unchanged? Write your prediction before execution.
Understand
A language model generates probabilistic output, not guaranteed facts. A useful automation defines the task, supplies only needed data, validates the response and asks a person to review consequential changes. The academy uses authored recorded-style JSON fixtures and never claims a live model answered. The Apps Script editor’s Gemini side panel is a separate product from calling a model API in your own script.
Example 1: Working automation
The explicit fixture label prevents a deterministic example from being mistaken for a live AI response.
function main() {
const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
console.log("AUTHORED FIXTURE");
console.log(authoredResponse.summary);
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: console.log("AUTHORED FIXTURE");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(authoredResponse.summary);
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"AUTHORED FIXTURE",
"Customer asks for an invoice"
],
"error": null,
"resource": "logs",
"value": null
}Example 2: Investigate a reproducible failure
Predict the effect of authoredResponse.summaries and identify the first mismatch. This example is intentionally faulty.
function main() {
const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
console.log("AUTHORED FIXTURE");
console.log(authoredResponse.summaries);
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: console.log("AUTHORED FIXTURE");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(authoredResponse.summaries);
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"AUTHORED FIXTURE",
"undefined"
],
"error": null,
"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() {
const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
console.log("AUTHORED FIXTURE");
console.log(authoredResponse.summary);
}
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: const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: console.log("AUTHORED FIXTURE");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(authoredResponse.summary);
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 6: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 7: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- 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: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"AUTHORED FIXTURE",
"Customer asks for an invoice",
"AUTHORED FIXTURE",
"Customer asks for an invoice"
],
"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() {
const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
console.log("AUTHORED FIXTURE");
console.log(authoredResponse.summary);
}
function main() {
console.log("Start: Gemini and AI-powered applications");
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: const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: console.log("AUTHORED FIXTURE");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 4: console.log(authoredResponse.summary);
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 6: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 7: console.log("Start: Gemini and AI-powered applications");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 8: try { lessonAction(); console.log("Completed operation"); }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 9: 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 10: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Start: Gemini and AI-powered applications",
"AUTHORED FIXTURE",
"Customer asks for an invoice",
"Completed operation"
],
"error": null,
"resource": "logs",
"value": null
}Build and test
Repair the supplied script so that: The explicit fixture label prevents a deterministic example from being mistaken for a live AI response. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
console.log("AUTHORED FIXTURE");
console.log(authoredResponse.summaries);
}Graduated hints
Hint 1
Inspect the operation containing authoredResponse.summaries. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns authoredResponse.summary. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses authoredResponse.summary where the broken source uses authoredResponse.summaries. Explain why before applying it.
Reference solution
function main() {
const authoredResponse = {category: "support", summary: "Customer asks for an invoice"};
console.log("AUTHORED FIXTURE");
console.log(authoredResponse.summary);
}Explain and reflect
Which operation proves the intended result in gemini and ai-powered applications? 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.