Lesson 61: Writing Emails with OpenClaw

Email automation should not jump from generation to sending. A reliable assistant separates recipient context, thread history, tone, attachments, risk, and final approval.

Skills Used

Search skills.lc for email, gmail, imap, or smtp. In this environment, use himalaya for IMAP/SMTP, gog for Gmail and Google Workspace, documents for formal attachments, and spreadsheets for bulk recipient lists.

Workflow

For a new email, identify the purpose: inform, request, apologize, follow up, invite, or recap. Each purpose has a different structure.

For replies, summarize the thread first. The last email alone may not contain the real context.

For follow-ups, include the previous commitment, the next requested action, and a low-friction way for the recipient to respond.

For bulk email, generate personalized drafts from a spreadsheet and sample-check names, company names, dates, amounts, and attachments.

Human Review

OpenClaw can draft. A human should approve sending, especially for pricing, contracts, account access, complaints, or sensitive relationships.

Exercise

Create five follow-up email drafts from a customer list and produce a sending checklist.

The assistant drafts and checks; you decide whether to send.