Can Microsoft To Do and Teamwork talk in both directions?

Yes. Build one flow that starts in Microsoft To Do and acts in Teamwork, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect Microsoft To Do to Teamwork

Move data between Microsoft To Do and Teamwork the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore Microsoft To Do Explore Teamwork

Microsoft To Do triggers: 4
Microsoft To Do actions: 13
Teamwork triggers: 7
Teamwork actions: 18

Automation ideas

What you can build with Microsoft To Do and Teamwork

A few flows teams run between Microsoft To Do and Teamwork. Use one as a starting point, or build your own from scratch.

New Task in Microsoft To Do creates Create Project in Teamwork
Triggers when a new task is created.
New Task in Teamwork creates Create Task in Microsoft To Do
Fires when a task is created.
New Task in Microsoft To Do creates Create Task List in Teamwork
Triggers when a new task is created.
New Task in Teamwork creates Create Task List in Microsoft To Do
Fires when a task is created.
New Task in Microsoft To Do creates Create Task in Teamwork
Triggers when a new task is created.
New Task in Teamwork creates List Tasks in Microsoft To Do
Fires when a task is created.