list_tasks from yesterday reads your research to-dos. Every time you create a Calendar event for a deadline, you also need a corresponding task to track the actual work. How do you add a task?
list_tasks showed me the task list structure. The insert action should take the list ID, a title, and notes — same params I'd fill in the Tasks UI.
GOOGLETASKS_INSERT_TASK takes exactly those: tasklist ID, title, and notes. Write action — always use list_tasks first to verify the list exists before inserting. Returns the created task dict:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": "@default", "title": "Review 50 survey responses", "notes": "Week 4 batch from Qualtrics export"}
)
task_id = result.get("id", "")
print(f"Task created: {task_id}")
notes — is that an optional field? What happens if I don't pass it?
Optional. The task creates with an empty notes field. Pass it when you have context to add — the deadline source, the link, the week number. Good task notes are the difference between a useful checklist and a cryptic list of words:
def add_task(list_id: str, title: str, notes: str) -> dict:
existing = list_tasks(list_id)
print(f"Adding to list with {len(existing)} existing tasks")
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": list_id, "title": title, "notes": notes}
)
print(f"Task '{title}' created: {result.get('id', '')}")
return result
I can chain create_event and add_task — one email announcement becomes both a Calendar block and a Task in one script.
Your three-app manual routine — read email, add to Calendar, add to Tasks — is now a two-function call. You could run it from the terminal walking out of the committee meeting.
Week 2 is the full deadline loop: list calendars, find events, create events, list tasks, add tasks. Five functions that replaced my entire scheduling ritual.
GOOGLETASKS_INSERT_TASK adds the task at the top of the list by default. If ordering matters — due date, priority — use GOOGLETASKS_UPDATE_TASK after creation to set additional fields. For the capstone workflow, default ordering is fine.
Required params:
| Param | Type | Example |
|---|---|---|
tasklist | str | "@default" or list ID |
title | str | "Review 50 survey responses" |
notes | str | Context or source info (optional) |
list_tasks(list_id) → confirm list exists → GOOGLETASKS_INSERT_TASK → verify created task
Empty string "" is valid if you have no notes. Task appears in the Tasks UI immediately after insert.
list_tasks from yesterday reads your research to-dos. Every time you create a Calendar event for a deadline, you also need a corresponding task to track the actual work. How do you add a task?
list_tasks showed me the task list structure. The insert action should take the list ID, a title, and notes — same params I'd fill in the Tasks UI.
GOOGLETASKS_INSERT_TASK takes exactly those: tasklist ID, title, and notes. Write action — always use list_tasks first to verify the list exists before inserting. Returns the created task dict:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": "@default", "title": "Review 50 survey responses", "notes": "Week 4 batch from Qualtrics export"}
)
task_id = result.get("id", "")
print(f"Task created: {task_id}")notes — is that an optional field? What happens if I don't pass it?
Optional. The task creates with an empty notes field. Pass it when you have context to add — the deadline source, the link, the week number. Good task notes are the difference between a useful checklist and a cryptic list of words:
def add_task(list_id: str, title: str, notes: str) -> dict:
existing = list_tasks(list_id)
print(f"Adding to list with {len(existing)} existing tasks")
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": list_id, "title": title, "notes": notes}
)
print(f"Task '{title}' created: {result.get('id', '')}")
return resultI can chain create_event and add_task — one email announcement becomes both a Calendar block and a Task in one script.
Your three-app manual routine — read email, add to Calendar, add to Tasks — is now a two-function call. You could run it from the terminal walking out of the committee meeting.
Week 2 is the full deadline loop: list calendars, find events, create events, list tasks, add tasks. Five functions that replaced my entire scheduling ritual.
GOOGLETASKS_INSERT_TASK adds the task at the top of the list by default. If ordering matters — due date, priority — use GOOGLETASKS_UPDATE_TASK after creation to set additional fields. For the capstone workflow, default ordering is fine.
Required params:
| Param | Type | Example |
|---|---|---|
tasklist | str | "@default" or list ID |
title | str | "Review 50 survey responses" |
notes | str | Context or source info (optional) |
list_tasks(list_id) → confirm list exists → GOOGLETASKS_INSERT_TASK → verify created task
Empty string "" is valid if you have no notes. Task appears in the Tasks UI immediately after insert.
Create a free account to get started. Paid plans unlock all tracks.