DiscoveryVIP / Apps Script AcademyHelp

64. Form submission and time-driven triggers

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

Open Interactive Lesson

Discover

How can you use form submission and time-driven triggers without changing the wrong data?

Predict

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

Understand

A spreadsheet form-submit event supplies values and namedValues; a Form-bound event supplies response. Their handlers are not interchangeable. Test each event shape and document which trigger to install. A time-driven event is not a row submission and has no submitted values. This example expects the spreadsheet variant only.

Example 1: Working automation

The prepared event’s second value is the person’s name; the first is a timestamp.

function main() {
  if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
  console.log(e.values[1]);
  SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[1], "Registered"]);
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 3: console.log(e.values[1]);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[1], "Registered"]);
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Alex"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ],
      [
        "Alex",
        "Registered"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ]
    ]
  }
}

Example 2: Investigate a reproducible failure

Predict the effect of e.values[0], "Registered" and identify the first mismatch. This example is intentionally faulty.

function main() {
  if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
  console.log(e.values[1]);
  SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[0], "Registered"]);
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 3: console.log(e.values[1]);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[0], "Registered"]);
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 5: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Alex"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ],
      [
        "2026-11-18",
        "Registered"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ]
    ]
  }
}

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() {
  if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
  console.log(e.values[1]);
  SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[1], "Registered"]);
}
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: if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 3: console.log(e.values[1]);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[1], "Registered"]);
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
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": [
    "Alex",
    "Alex"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ],
      [
        "Alex",
        "Registered"
      ],
      [
        "Alex",
        "Registered"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ]
    ]
  }
}

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() {
  if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
  console.log(e.values[1]);
  SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[1], "Registered"]);
}
function main() {
  console.log("Start: Form submission and time-driven 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: if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 3: console.log(e.values[1]);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[1], "Registered"]);
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
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: Form submission and time-driven 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: Form submission and time-driven triggers",
    "Alex",
    "Completed operation"
  ],
  "error": null,
  "resource": "sheets",
  "value": {
    "People": [
      [
        "Name",
        "Status"
      ],
      [
        "Alex",
        "Pending"
      ],
      [
        "Jordan",
        "Pending"
      ],
      [
        "Morgan",
        "Pending"
      ],
      [
        "Alex",
        "Registered"
      ]
    ],
    "Sales": [
      [
        "Customer",
        "Amount",
        "Approved"
      ],
      [
        "Alex",
        120,
        true
      ],
      [
        "Jordan",
        80,
        false
      ],
      [
        "Morgan",
        200,
        true
      ]
    ],
    "Tasks": [
      [
        "Task",
        "Status"
      ],
      [
        "Review invoice",
        "Open"
      ],
      [
        "Publish report",
        "Complete"
      ]
    ]
  }
}

Build and test

Repair the supplied script so that: The prepared event’s second value is the person’s name; the first is a timestamp. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
  console.log(e.values[1]);
  SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[0], "Registered"]);
}

Graduated hints

Hint 1

Inspect the operation containing e.values[0], "Registered". Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns e.values[1], "Registered". Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses e.values[1], "Registered" where the broken source uses e.values[0], "Registered". Explain why before applying it.

Reference solution

function main() {
  if (!e || !Array.isArray(e.values)) throw new Error("Choose Spreadsheet form submission");
  console.log(e.values[1]);
  SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().appendRow([e.values[1], "Registered"]);
}

Explain and reflect

Which operation proves the intended result in form submission and time-driven triggers? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the input records and sheets 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 sheets 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. Select the prepared event shown in this lesson; Manual has no event object. 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: Event objects, permissions and execution identity