44. Personalized drafts and HTML messages
Module 9 · 20 minutes · Lesson 43; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use personalized drafts and html messages without changing the wrong data?
- Explain personalized drafts and html messages in your own words
- Trace the actual drafts state change 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
Build personalized messages from validated records and show recipients before any send. Provide plain text alongside HTML. Escape untrusted text when inserting it into markup. This example uses fixed trusted sample text; the separate escaping helper in the reference shows how dynamic data differs. Draft creation is a real side effect in Google even though nothing is sent.
Example 1: Working automation
Both a plain-text body and HTML alternative are recorded for human review.
function main() {
const name = "Alex";
GmailApp.createDraft("alex@example.com", "Hello " + name, "Welcome, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
}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 name = "Alex";
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: GmailApp.createDraft("alex@example.com", "Hello " + name, "Welcome, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-1",
"to": "alex@example.com",
"subject": "Hello Alex",
"body": "Welcome, Alex",
"htmlBody": "<p>Welcome, <strong>Alex</strong></p>"
}
]
}Example 2: Investigate a reproducible failure
Predict the effect of "Goodbye, " + name and identify the first mismatch. This example is intentionally faulty.
function main() {
const name = "Alex";
GmailApp.createDraft("alex@example.com", "Hello " + name, "Goodbye, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
}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 name = "Alex";
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: GmailApp.createDraft("alex@example.com", "Hello " + name, "Goodbye, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-1",
"to": "alex@example.com",
"subject": "Hello Alex",
"body": "Goodbye, Alex",
"htmlBody": "<p>Welcome, <strong>Alex</strong></p>"
}
]
}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 name = "Alex";
GmailApp.createDraft("alex@example.com", "Hello " + name, "Welcome, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
}
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 name = "Alex";
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: GmailApp.createDraft("alex@example.com", "Hello " + name, "Welcome, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- 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": [],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-1",
"to": "alex@example.com",
"subject": "Hello Alex",
"body": "Welcome, Alex",
"htmlBody": "<p>Welcome, <strong>Alex</strong></p>"
},
{
"id": "draft-2",
"to": "alex@example.com",
"subject": "Hello Alex",
"body": "Welcome, Alex",
"htmlBody": "<p>Welcome, <strong>Alex</strong></p>"
}
]
}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 name = "Alex";
GmailApp.createDraft("alex@example.com", "Hello " + name, "Welcome, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
}
function main() {
console.log("Start: Personalized drafts and HTML messages");
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 name = "Alex";
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: GmailApp.createDraft("alex@example.com", "Hello " + name, "Welcome, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- 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: Personalized drafts and HTML messages");
- 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: Personalized drafts and HTML messages",
"Completed operation"
],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-1",
"to": "alex@example.com",
"subject": "Hello Alex",
"body": "Welcome, Alex",
"htmlBody": "<p>Welcome, <strong>Alex</strong></p>"
}
]
}Build and test
Repair the supplied script so that: Both a plain-text body and HTML alternative are recorded for human review. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const name = "Alex";
GmailApp.createDraft("alex@example.com", "Hello " + name, "Goodbye, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
}Graduated hints
Hint 1
Inspect the operation containing "Goodbye, " + name. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns "Welcome, " + name. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses "Welcome, " + name where the broken source uses "Goodbye, " + name. Explain why before applying it.
Reference solution
function main() {
const name = "Alex";
GmailApp.createDraft("alex@example.com", "Hello " + name, "Welcome, " + name, {htmlBody: "<p>Welcome, <strong>" + name + "</strong></p>"});
}Explain and reflect
Which operation proves the intended result in personalized drafts and html messages? 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.