ActionMicrosoft To DoUpdated May 2026

How do I create a Microsoft To Do task?

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.

Use this action All 3 Microsoft To Do actions

Inputs

The fields this action accepts.

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)

Sample request

{
  "listId": "{{trigger.listId}}",
  "title": "{{trigger.title}}",
  "body": "e.g. Hi there, thanks for reaching out.",
  "importance": "{{trigger.importance}}",
  "dueDateTime": "{{trigger.dueDateTime}}"
}

Returns

{
  "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.

Triggered by

Apps that pair well as the trigger for Create Microsoft To Do Task.

Any of these apps can fire this action as part of a workflow.

Gmail → Microsoft To Do

1 Gmail triggers

Slack → Microsoft To Do

13 Slack triggers

Google Sheets → Microsoft To Do

2 Google Sheets triggers

HubSpot → Microsoft To Do

18 HubSpot triggers

FAQ

Questions about Create Microsoft To Do Task.

What does the Create Microsoft To Do Task action do in Microsoft To Do?

Adds a task to a specific list with title, due date, body. For "external event → personal todo" workflows in Microsoft-ecosystem teams.

What inputs does Create Microsoft To Do Task require?

Required: Task List ID, Title. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Microsoft To Do returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Microsoft To Do Task support batch operations?

Yes. Run Create Microsoft To Do Task inside a Loop node to process arrays. Tiny Command handles Microsoft To Do's rate limits automatically so you don't have to throttle manually.

More actions