DiscoveryVIP / Apps Script AcademyHelp

41. GmailApp and MailApp

Module 9 · 20 minutes · Lesson 40; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use gmailapp and mailapp without changing the wrong data?

Predict

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

Understand

GmailApp can inspect mailbox threads and create drafts, while MailApp focuses on sending messages and checking recipient quota. Use the narrowest service needed. This academy defaults to drafts and never delivers mail. A remaining-quota value is not a promise that every other limit or permission will allow a send.

Example 1: Working automation

A valid recipient creates a draft. The quota is a configurable local scenario, not a live account limit.

function main() {
  GmailApp.createDraft("alex@example.com", "Workshop reminder", "Please review your notes.");
  console.log(MailApp.getRemainingDailyQuota());
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: GmailApp.createDraft("alex@example.com", "Workshop reminder", "Please review your notes.");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: console.log(MailApp.getRemainingDailyQuota());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "10"
  ],
  "error": null,
  "resource": "drafts",
  "value": [
    {
      "id": "draft-1",
      "to": "alex@example.com",
      "subject": "Workshop reminder",
      "body": "Please review your notes.",
      "htmlBody": ""
    }
  ]
}

Example 2: Investigate a reproducible failure

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

function main() {
  GmailApp.createDraft("invalid", "Workshop reminder", "Please review your notes.");
  console.log(MailApp.getRemainingDailyQuota());
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: GmailApp.createDraft("invalid", "Workshop reminder", "Please review your notes.");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: console.log(MailApp.getRemainingDailyQuota());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [],
  "error": "Invalid simulated recipient.",
  "resource": "drafts",
  "value": []
}

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() {
  GmailApp.createDraft("alex@example.com", "Workshop reminder", "Please review your notes.");
  console.log(MailApp.getRemainingDailyQuota());
}
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: GmailApp.createDraft("alex@example.com", "Workshop reminder", "Please review your notes.");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: console.log(MailApp.getRemainingDailyQuota());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
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: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "10",
    "10"
  ],
  "error": null,
  "resource": "drafts",
  "value": [
    {
      "id": "draft-1",
      "to": "alex@example.com",
      "subject": "Workshop reminder",
      "body": "Please review your notes.",
      "htmlBody": ""
    },
    {
      "id": "draft-2",
      "to": "alex@example.com",
      "subject": "Workshop reminder",
      "body": "Please review your notes.",
      "htmlBody": ""
    }
  ]
}

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() {
  GmailApp.createDraft("alex@example.com", "Workshop reminder", "Please review your notes.");
  console.log(MailApp.getRemainingDailyQuota());
}
function main() {
  console.log("Start: GmailApp and MailApp");
  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: GmailApp.createDraft("alex@example.com", "Workshop reminder", "Please review your notes.");
Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
Line 3: console.log(MailApp.getRemainingDailyQuota());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: console.log("Start: GmailApp and MailApp");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 7: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: 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 9: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: GmailApp and MailApp",
    "10",
    "Completed operation"
  ],
  "error": null,
  "resource": "drafts",
  "value": [
    {
      "id": "draft-1",
      "to": "alex@example.com",
      "subject": "Workshop reminder",
      "body": "Please review your notes.",
      "htmlBody": ""
    }
  ]
}

Build and test

Repair the supplied script so that: A valid recipient creates a draft. The quota is a configurable local scenario, not a live account limit. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  GmailApp.createDraft("invalid", "Workshop reminder", "Please review your notes.");
  console.log(MailApp.getRemainingDailyQuota());
}

Graduated hints

Hint 1

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

Hint 2

The repair concerns "alex@example.com". Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses "alex@example.com" where the broken source uses "invalid". Explain why before applying it.

Reference solution

function main() {
  GmailApp.createDraft("alex@example.com", "Workshop reminder", "Please review your notes.");
  console.log(MailApp.getRemainingDailyQuota());
}

Explain and reflect

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

Adapt the input records and drafts 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 drafts 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: Messages and threads