Your list_tasks shows existing tasks. Now the other side — creating one. What task do you always forget to add after a customer demo?
After list_tasks I can see my existing follow-ups. But I always forget to add the '48-hour check-in' task for new Enterprise customers. It's not complex — just a reminder with a note — but I skip it when I'm busy.
GOOGLETASKS_INSERT_TASK creates the task for you. Three parameters: the task list ID, the task title, and an optional notes string. The task appears in Google Tasks exactly as if you'd typed it:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": list_id, "title": title, "notes": notes}
)
print(result.get("id", "no task id"))
Can I set a due date for the task too? Or is it just title and notes?
You can add "due": "2026-04-22T00:00:00.000Z" to the params — an ISO8601 datetime for the due date. For the capstone we keep it simple: title and notes. Due dates are an easy extension once the base pattern works. Here's the full function:
def add_task(list_id: str, title: str, notes: str) -> dict:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": list_id, "title": title, "notes": notes}
)
print(f"Task created: {result.get('id', 'no id')}")
return result
So create_event for the demo booking, then add_task for the follow-up reminder — two function calls that replace three manual steps. That's the workflow the capstone will chain.
Your '48-hour check-in' just automated itself. It will never fall through the cracks again.
Calendar and Tasks together — the full booking workflow. One function per action, composable in any order. Week 4 is going to be interesting.
Verify the task list ID before inserting. list_tasks(list_id) first — if it returns without error, the list ID is valid. An invalid list ID raises an error from Composio that's easier to debug before you build a chain around it.
GOOGLETASKS_INSERT_TASK creates a task in a specific list. Automating follow-up task creation after every demo booking ensures no customer check-in falls through the cracks.
toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": "@default", "title": "Send prep materials", "notes": "48h before demo"}
)| Field | Value |
|---|---|
due | ISO8601 due datetime |
notes | Plain text task notes |
status | "needsAction" (default) or "completed" |
Always verify the task list ID with list_tasks before inserting. An invalid list ID raises a Composio error.
Your list_tasks shows existing tasks. Now the other side — creating one. What task do you always forget to add after a customer demo?
After list_tasks I can see my existing follow-ups. But I always forget to add the '48-hour check-in' task for new Enterprise customers. It's not complex — just a reminder with a note — but I skip it when I'm busy.
GOOGLETASKS_INSERT_TASK creates the task for you. Three parameters: the task list ID, the task title, and an optional notes string. The task appears in Google Tasks exactly as if you'd typed it:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": list_id, "title": title, "notes": notes}
)
print(result.get("id", "no task id"))Can I set a due date for the task too? Or is it just title and notes?
You can add "due": "2026-04-22T00:00:00.000Z" to the params — an ISO8601 datetime for the due date. For the capstone we keep it simple: title and notes. Due dates are an easy extension once the base pattern works. Here's the full function:
def add_task(list_id: str, title: str, notes: str) -> dict:
result = toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": list_id, "title": title, "notes": notes}
)
print(f"Task created: {result.get('id', 'no id')}")
return resultSo create_event for the demo booking, then add_task for the follow-up reminder — two function calls that replace three manual steps. That's the workflow the capstone will chain.
Your '48-hour check-in' just automated itself. It will never fall through the cracks again.
Calendar and Tasks together — the full booking workflow. One function per action, composable in any order. Week 4 is going to be interesting.
Verify the task list ID before inserting. list_tasks(list_id) first — if it returns without error, the list ID is valid. An invalid list ID raises an error from Composio that's easier to debug before you build a chain around it.
GOOGLETASKS_INSERT_TASK creates a task in a specific list. Automating follow-up task creation after every demo booking ensures no customer check-in falls through the cracks.
toolset.execute_action(
Action.GOOGLETASKS_INSERT_TASK,
{"tasklist": "@default", "title": "Send prep materials", "notes": "48h before demo"}
)| Field | Value |
|---|---|
due | ISO8601 due datetime |
notes | Plain text task notes |
status | "needsAction" (default) or "completed" |
Always verify the task list ID with list_tasks before inserting. An invalid list ID raises a Composio error.
Create a free account to get started. Paid plans unlock all tracks.