Every week you write a progress update to your advisor — same subject format, same structure, just different content. How long does drafting that email actually take?
search_emails from yesterday showed me which emails are unread. Drafting takes 5–10 minutes — opening Gmail, writing the greeting, filling in the update, typing the subject line correctly.
GMAIL_CREATE_EMAIL_DRAFT does the drafting for you. It creates the draft in your Gmail account without sending it — safe to test with any recipient, review before sending, and modify in the app if needed. Write actions always come with a safety note: test drafts to yourself first, confirm before enabling send:
result = toolset.execute_action(
Action.GMAIL_CREATE_EMAIL_DRAFT,
{"to": "you@gmail.com", "subject": "Thesis update — Week 4", "body": "Hi, here is this week's progress..."}
)
draft_id = result.get("id", "")
print(f"Draft created: {draft_id}")
GMAIL_CREATE_EMAIL_DRAFT — does this actually appear in my Gmail drafts folder? I can open Gmail and see it?
Yes — it appears in your real Gmail Drafts folder. You can open it, edit it, and decide to send manually. This is the safe automation pattern: Python drafts, human reviews, human decides to send:
def draft_email(to: str, subject: str, body: str) -> dict:
result = toolset.execute_action(
Action.GMAIL_CREATE_EMAIL_DRAFT,
{"to": to, "subject": subject, "body": body}
)
draft_id = result.get("id", "")
print(f"Draft created for {to}: {draft_id}")
return result
I can call this with the week number and the progress summary — the subject line formats itself, the body fills in, the draft lands in Gmail. Five minutes of typing becomes one function call.
Your advisor gets a consistent format every week without you remembering the exact subject line they preferred.
I'm building the capstone piece by piece — this is the draft step of the research-progress workflow.
Always pair write actions with confirmation in real workflows. GMAIL_CREATE_EMAIL_DRAFT is safe because it doesn't send. When you escalate to GMAIL_SEND_EMAIL in the track, treat the test recipient as a required argument — never hardcode your advisor's address in test code.
GMAIL_CREATE_EMAIL_DRAFT creates a draft in your Gmail Drafts folder. No email is sent.
| Param | Type | Example |
|---|---|---|
to | str | "advisor@university.edu" |
subject | str | "Thesis update — Week 4" |
body | str | Full email body text |
Every week you write a progress update to your advisor — same subject format, same structure, just different content. How long does drafting that email actually take?
search_emails from yesterday showed me which emails are unread. Drafting takes 5–10 minutes — opening Gmail, writing the greeting, filling in the update, typing the subject line correctly.
GMAIL_CREATE_EMAIL_DRAFT does the drafting for you. It creates the draft in your Gmail account without sending it — safe to test with any recipient, review before sending, and modify in the app if needed. Write actions always come with a safety note: test drafts to yourself first, confirm before enabling send:
result = toolset.execute_action(
Action.GMAIL_CREATE_EMAIL_DRAFT,
{"to": "you@gmail.com", "subject": "Thesis update — Week 4", "body": "Hi, here is this week's progress..."}
)
draft_id = result.get("id", "")
print(f"Draft created: {draft_id}")GMAIL_CREATE_EMAIL_DRAFT — does this actually appear in my Gmail drafts folder? I can open Gmail and see it?
Yes — it appears in your real Gmail Drafts folder. You can open it, edit it, and decide to send manually. This is the safe automation pattern: Python drafts, human reviews, human decides to send:
def draft_email(to: str, subject: str, body: str) -> dict:
result = toolset.execute_action(
Action.GMAIL_CREATE_EMAIL_DRAFT,
{"to": to, "subject": subject, "body": body}
)
draft_id = result.get("id", "")
print(f"Draft created for {to}: {draft_id}")
return resultI can call this with the week number and the progress summary — the subject line formats itself, the body fills in, the draft lands in Gmail. Five minutes of typing becomes one function call.
Your advisor gets a consistent format every week without you remembering the exact subject line they preferred.
I'm building the capstone piece by piece — this is the draft step of the research-progress workflow.
Always pair write actions with confirmation in real workflows. GMAIL_CREATE_EMAIL_DRAFT is safe because it doesn't send. When you escalate to GMAIL_SEND_EMAIL in the track, treat the test recipient as a required argument — never hardcode your advisor's address in test code.
GMAIL_CREATE_EMAIL_DRAFT creates a draft in your Gmail Drafts folder. No email is sent.
| Param | Type | Example |
|---|---|---|
to | str | "advisor@university.edu" |
subject | str | "Thesis update — Week 4" |
body | str | Full email body text |
Create a free account to get started. Paid plans unlock all tracks.