List Tasks
ms_todo.list_tasks
ActionBusiness appsconnection required
Calls the Microsoft To Do API with the connection's credentials.
List the tasks in a task list, optionally narrowed by an OData filter such as a status.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Microsoft To Do
- Secret shape
- {"client_id": "…", "client_secret": "…", "refresh_token": "…"} with the Tasks.ReadWrite delegated scope
- Config it needs
- tenant
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
list_id The task list id, from ms_todo.list_task_lists or ms_todo.create_task_list. | string | Yes | — | — | — |
filter OData $filter over the task properties, e.g. "status ne 'completed'". Leave blank for every task. | string | No | — | — | — |
max_results How many tasks to return at most; Graph pages are followed until this many. | number | No | 50 | 1–1000 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_results": 50
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The tasks found. | array | — |
count How many tasks were returned. | number | — |
{
"count": 0,
"items": []
}Related Microsoft To Do nodes
See List Tasks run in a workflow.
In a technical demo we add the Microsoft To Do connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.