Per-pair page

Connect Microsoft To Do to Slack in two minutes.

Real-time triggers from Microsoft To Do, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect Microsoft To Do and Slack See reverse direction

Trigger app

Microsoft To Do as the trigger

Workflows fire when something happens in Microsoft To Do.

Microsoft To Do has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Microsoft To Do → Slack

When something happens in Microsoft To Do, do it in Slack.

0 Microsoft To Do triggers wired to 45 Slack actions.

Slack → Microsoft To Do

Or fire it the other way around.

13 Slack triggers wired to 3 Microsoft To Do actions downstream.

See Slack → Microsoft To Do →

How it works

Connect Microsoft To Do and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Microsoft To Do and Slack
Open Tiny Command, authorize Microsoft To Do and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Microsoft To Do trigger
Drop the Microsoft To Do → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/microsoft-todo.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Slack action
Drop the Slack → Add Reaction action below it. Map fields from the Microsoft To Do payload into the Slack inputs.
slack.add-reaction
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Microsoft To Do + Slack.

How long does it take to connect Microsoft To Do and Slack on Tiny Command?

Under two minutes. Authorize Microsoft To Do and Slack once each, drop the Microsoft To Do trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Microsoft To Do ↔ Slack integration real-time?

Yes. Both Microsoft To Do and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Microsoft To Do and Slack?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.

What Microsoft To Do events can trigger a Slack workflow?

Use Tiny Command's universal Webhook trigger to receive Microsoft To Do events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use Microsoft To Do with Slack?

No. There's a free tier that covers most Microsoft To Do+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → Microsoft To Do instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/microsoft-todo page with the reverse-direction triggers and actions.