Motion

Your assistant can identify you from the connected key, list your tasks filtered to you, and read the individual task records, which come back with the scheduling information Motion worked out as well as the due date you typed in. Your work hours and timezone are readable too. The interesting part is the gap between when something is due and when Motion has found room for it. Nothing here writes.

What you end up with. A plain-language account of your week, naming the tasks Motion has scheduled tight against their deadline.

Start with it bringing you the information and you deciding.

Never without. Remember that Motion is only scheduling what somebody entered. A calm-looking week usually means the real work never got written down, not that the week is calm.

Built on: Get My User Information / List Tasks / Get Task by ID / List Schedules / List Projects

It can list the people in a workspace, list the tasks assigned to each, and read the projects and statuses those tasks sit under. That produces the workload picture before the standup rather than during it, and it is more honest than counting tickets, because it can separate what is due this week from what is merely open. Reading only.

What you end up with. A per-person view of assigned tasks with due dates and status, showing where the next piece of work should not go.

Start with it bringing you the information and you deciding.

Never without. Never turn this into a comparison between people. Task counts measure how work was entered, not how hard anyone is working, and the person with the fewest tasks is often the one carrying the thing nobody logged.

Built on: List users / List Workspaces / List Tasks / List Projects / List Statuses

It can find the right workspace and project, read the statuses and the people available in it, and create each task with a name, description, priority, due date and assignee. Motion then schedules them itself. Doing this straight after the call, while the wording is still fresh, is the version that works, and it is a step worth watching the first few times so you can see how it interprets a vague commitment.

What you end up with. Each agreed item in Motion as its own task with an owner and a due date, and a written list of what it created.

Start with it doing the work and checking with you.

Never without. Confirm the workspace and the assignees before it creates anything. A task filed into the wrong workspace is invisible to the person who needs it, and assigning work to a colleague in Motion drops it straight into their schedule without asking them.

Built on: List Workspaces / List Projects / List Statuses / List users / Create Task

It can create the project in a named workspace with a due date, description and priority, read the workspace custom fields, set values on the project, and create the standard task list underneath it. If part of the work repeats every week, it can set that up as a recurring task rather than as ten copies. This is the setup people do by hand each time and abbreviate under pressure.

What you end up with. A project with its custom fields filled in, its standard tasks created, and any weekly work set up to repeat.

Start with it doing the work and checking with you.

Never without. Check the recurrence pattern before you approve it. A recurring task set to daily instead of weekly generates instances in everyone's schedule until someone notices, and the noticing usually happens on a Monday.

Built on: List Workspaces / Create Project / List Custom Fields / Add Custom Field to Project / Create Task / Create Recurring Task

It can list what is open, read the individual tasks with their current scheduling, and update the ones that need to change: due date, priority, status, or who is holding them. Only the fields you name get touched. The useful pattern is two moves, a proposed set of changes first, then the update, because deciding what slips is the part you should keep.

What you end up with. A revised week with new dates and priorities in Motion, and a written record of every task that moved and why.

Start with it doing the work and checking with you.

Never without. Never let it move a deadline that somebody outside the team is waiting on. Motion will reschedule the work quietly and nobody downstream is told, so any date that was promised to a client changes in a conversation first and in Motion second.

Built on: List Tasks / Get Task by ID / List Statuses / Update Task

It can list what is assigned to you, list the people who could take it, reassign what is moving with an update, comment on each task so the context travels with it, and unassign the ones that should sit unowned until you are back. Unassigning clears the assignee and leaves the task with nobody on it, which is the point, and also the risk.

What you end up with. Your open work either reassigned with a handover comment attached, or deliberately unassigned and listed for your return.

Start with it doing the work and checking with you.

Never without. Never unassign in bulk without keeping your own list of who held each task. The connector's unassign action only clears the assignee, so an unassigned task with no comment on it becomes work that belongs to nobody and gets found in three weeks.

Built on: List Tasks / List users / Update Task / Create Comment / Unassign Task

It can, and Motion's own wording for both routes is permanent: Delete Task permanently removes a task, and Delete Recurring Task removes a recurring task permanently. Nothing on this connector restores one. Run it in two moves. Have it list the candidates, whether one-off tasks or repeats that nobody has completed in months, read that list yourself, then approve deletion of exactly that set.

What you end up with. The abandoned tasks and stale repeats gone, and a saved list of everything deleted with its name, project and last status.

Start with it doing the work and checking with you.

Never without. Never approve a deletion described only as a rule, such as anything untouched for ninety days. Have it name every task first and approve that exact list, because a deleted Motion task takes its comments and history with it and cannot be restored through the connection.

Built on: List Tasks / List Recurring Tasks / Get Task by ID / Delete Task / Delete Recurring Task