DiscoveryVIP / Apps Script AcademyHelp

63. Installable triggers

Module 13 · 20 minutes · Lesson 62; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use installable triggers without changing the wrong data?

Predict

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

Understand

Installable triggers can call authorized services subject to the installer’s identity and permissions. A trigger’s owner and source matter. Keep setup separate from the handler and inspect existing project triggers to avoid duplicates. The export includes setup instructions; the local trigger record does not schedule real background work.

Example 1: Working automation

The trigger targets spreadsheet edits, which provide a different event contract from form submissions.

function main() {
  const id = SpreadsheetApp.getActiveSpreadsheet().getId();
  ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onEdit().create();
}
function handleEdit(event) { console.log(event.range.getRow()); }
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 id = SpreadsheetApp.getActiveSpreadsheet().getId();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 3: ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onEdit().create();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function handleEdit(event) { console.log(event.range.getRow()); }
Define a named block of instructions. Run Script calls main; helpers run only when called.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "triggers",
  "value": [
    {
      "handler": "handleEdit",
      "source": "synthetic-workbook",
      "type": "onEdit",
      "id": "trigger-1"
    }
  ]
}

Example 2: Investigate a reproducible failure

Predict the effect of onFormSubmit().create() and identify the first mismatch. This example is intentionally faulty.

function main() {
  const id = SpreadsheetApp.getActiveSpreadsheet().getId();
  ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onFormSubmit().create();
}
function handleEdit(event) { console.log(event.range.getRow()); }
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 id = SpreadsheetApp.getActiveSpreadsheet().getId();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 3: ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onFormSubmit().create();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function handleEdit(event) { console.log(event.range.getRow()); }
Define a named block of instructions. Run Script calls main; helpers run only when called.
Exact expected output and resource
{
  "logs": [],
  "error": null,
  "resource": "triggers",
  "value": [
    {
      "handler": "handleEdit",
      "source": "synthetic-workbook",
      "type": "onFormSubmit",
      "id": "trigger-1"
    }
  ]
}

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 id = SpreadsheetApp.getActiveSpreadsheet().getId();
  ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onEdit().create();
}
function handleEdit(event) { console.log(event.range.getRow()); }
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 id = SpreadsheetApp.getActiveSpreadsheet().getId();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 3: ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onEdit().create();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function handleEdit(event) { console.log(event.range.getRow()); }
Define a named block of instructions. Run Script calls main; helpers run only when called.
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": [],
  "error": null,
  "resource": "triggers",
  "value": [
    {
      "handler": "handleEdit",
      "source": "synthetic-workbook",
      "type": "onEdit",
      "id": "trigger-1"
    },
    {
      "handler": "handleEdit",
      "source": "synthetic-workbook",
      "type": "onEdit",
      "id": "trigger-2"
    }
  ]
}

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 id = SpreadsheetApp.getActiveSpreadsheet().getId();
  ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onEdit().create();
}
function handleEdit(event) { console.log(event.range.getRow()); }
function main() {
  console.log("Start: Installable triggers");
  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 id = SpreadsheetApp.getActiveSpreadsheet().getId();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 3: ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onEdit().create();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function handleEdit(event) { console.log(event.range.getRow()); }
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: console.log("Start: Installable triggers");
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: Installable triggers",
    "Completed operation"
  ],
  "error": null,
  "resource": "triggers",
  "value": [
    {
      "handler": "handleEdit",
      "source": "synthetic-workbook",
      "type": "onEdit",
      "id": "trigger-1"
    }
  ]
}

Build and test

Repair the supplied script so that: The trigger targets spreadsheet edits, which provide a different event contract from form submissions. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const id = SpreadsheetApp.getActiveSpreadsheet().getId();
  ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onFormSubmit().create();
}
function handleEdit(event) { console.log(event.range.getRow()); }

Graduated hints

Hint 1

Inspect the operation containing onFormSubmit().create(). Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns onEdit().create(). Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses onEdit().create() where the broken source uses onFormSubmit().create(). Explain why before applying it.

Reference solution

function main() {
  const id = SpreadsheetApp.getActiveSpreadsheet().getId();
  ScriptApp.newTrigger("handleEdit").forSpreadsheet(id).onEdit().create();
}
function handleEdit(event) { console.log(event.range.getRow()); }

Explain and reflect

Which operation proves the intended result in installable triggers? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the input records and triggers output 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 triggers 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: Form submission and time-driven triggers