Short answer: Drop the "Microsoft To Do → Create Microsoft To Do Task" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Task List ID listId | string | Required | Task List ID |
Title title | string | Required | Title |
Notes body | string | Optional | Message body content. Plain text unless the API specifies HTML/markdown. |
Importance importance | options | Optional | Importance. Options: Low, Normal, High |
Due Date dueDateTime | date | Optional | Due Date. (date/time) |
{"listId": "{{trigger.listId}}","title": "{{trigger.title}}","body": "e.g. Hi there, thanks for reaching out.","importance": "{{trigger.importance}}","dueDateTime": "{{trigger.dueDateTime}}"}
{"id": "task123","title": "Review proposal","status": "notStarted","importance": "normal","createdDateTime": "2026-04-11T10:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.