Task Lists

Google Tasks organizes to-dos into separate lists, such as one per project or one for a shared team. A Beam agent reads an approved source event, like a new support ticket or a task mentioned in an email, and adds it to the list that event maps to, filling in the title and any note from the source. It does not decide which list a brand new type of request belongs on. A source event that fits no existing list, or a task with conflicting details, is routed to a person to place and, if needed, add a new mapping rule.

Due Dates and Reminders

A task in Google Tasks can carry a due date and a reminder, which shows up alongside the task until it is marked complete. A Beam agent sets the due date on a new task using an approved rule, such as matching a deadline mentioned in the source ticket or email, and updates it if that source date changes. It does not decide the deadline on its own. A task with an unclear or missing date in the source, or one where the mentioned date has already passed, is routed to a person to confirm and set manually.

Subtasks

A task in Google Tasks can be broken into subtasks, useful for a to-do with several steps that need checking off one at a time. A Beam agent adds subtasks to a task under an approved rule, such as splitting a checklist mentioned in the source ticket into individual lines, and checks each one off as the linked step is confirmed complete. It does not reorder or rewrite the checklist itself. A checklist too long or unclear to split cleanly is routed to a person to break down and add manually.