A new arXiv paper arrived that's directly relevant to your systematic review. In your current workflow, how do you make sure you actually read it before the next literature review meeting?
list_tasks from Day 13 showed me the existing task backlog. For adding a new task I'd use GOOGLETASKS_INSERT_TASK — same pattern as create_event, but for the task list instead of the calendar.
Exactly. Three fields: tasklist_id, title, and notes. The notes field is where you store the paper DOI, the arXiv link, or the reason it's relevant — the context that makes the task actionable when you open it three days later:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist_id": list_id, "title": title, "notes": notes}
)
Does adding a task here show up in the Google Tasks mobile app too? Or only in the browser?
It shows up everywhere — browser, mobile app, Gmail sidebar. Google Tasks is synced across all surfaces. The task you create here is a real task in your account, same as one you'd add by hand. The difference is that your Python script can create 20 tasks from a literature search result in the time it takes to type one manually.
So I could wire this into the citation Sheet from the Week 3 capstone — read new rows, create a task for each one automatically. That's the Monday morning literature pipeline.
That's the Week 4 capstone preview. For now, one task at a time:
def add_task(list_id: str, title: str, notes: str) -> dict:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist_id": list_id, "title": title, "notes": notes}
)
print(f"Task added: {title}")
return result
Week 2 is the entire deadline and coordination layer of my research workflow — in code. Calendar for deadlines, Tasks for papers to review, Gmail for co-author updates. Connected.
One housekeeping note: GOOGLETASKS_INSERT_TASK creates a new task every call — it doesn't check for duplicates. If you run the script twice on the same citation list, you'll get duplicate tasks. The Week 4 error-handling lesson covers the deduplication pattern — for now, check list_tasks before inserting.
toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{
"tasklist_id": list_id,
"title": "Review Smith 2024 — working memory and age",
"notes": "arXiv:2403.12345 — relevant to H2 in our pre-reg"
}
)| Field | Purpose |
|---|---|
tasklist_id | Which task list to add to |
title | Task name (shows in app) |
notes | Context — DOI, link, reason for relevance |
due | Optional ISO 8601 due date |
Every call creates a new task. Check list_tasks before inserting if you're running in a loop over a citation list.
A new arXiv paper arrived that's directly relevant to your systematic review. In your current workflow, how do you make sure you actually read it before the next literature review meeting?
list_tasks from Day 13 showed me the existing task backlog. For adding a new task I'd use GOOGLETASKS_INSERT_TASK — same pattern as create_event, but for the task list instead of the calendar.
Exactly. Three fields: tasklist_id, title, and notes. The notes field is where you store the paper DOI, the arXiv link, or the reason it's relevant — the context that makes the task actionable when you open it three days later:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist_id": list_id, "title": title, "notes": notes}
)Does adding a task here show up in the Google Tasks mobile app too? Or only in the browser?
It shows up everywhere — browser, mobile app, Gmail sidebar. Google Tasks is synced across all surfaces. The task you create here is a real task in your account, same as one you'd add by hand. The difference is that your Python script can create 20 tasks from a literature search result in the time it takes to type one manually.
So I could wire this into the citation Sheet from the Week 3 capstone — read new rows, create a task for each one automatically. That's the Monday morning literature pipeline.
That's the Week 4 capstone preview. For now, one task at a time:
def add_task(list_id: str, title: str, notes: str) -> dict:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist_id": list_id, "title": title, "notes": notes}
)
print(f"Task added: {title}")
return resultWeek 2 is the entire deadline and coordination layer of my research workflow — in code. Calendar for deadlines, Tasks for papers to review, Gmail for co-author updates. Connected.
One housekeeping note: GOOGLETASKS_INSERT_TASK creates a new task every call — it doesn't check for duplicates. If you run the script twice on the same citation list, you'll get duplicate tasks. The Week 4 error-handling lesson covers the deduplication pattern — for now, check list_tasks before inserting.
toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{
"tasklist_id": list_id,
"title": "Review Smith 2024 — working memory and age",
"notes": "arXiv:2403.12345 — relevant to H2 in our pre-reg"
}
)| Field | Purpose |
|---|---|
tasklist_id | Which task list to add to |
title | Task name (shows in app) |
notes | Context — DOI, link, reason for relevance |
due | Optional ISO 8601 due date |
Every call creates a new task. Check list_tasks before inserting if you're running in a loop over a citation list.
Create a free account to get started. Paid plans unlock all tracks.