How to Turn Email and Teams Follow-Ups into Todoist Tasks with Due Dates Using Copilot

Why This Post

Important follow-ups often start in email or Teams chat, but they get lost when they are not converted into a task system. This draft combines the email follow-up, Teams follow-up, and Todoist automation ideas into one stronger article.

What You Will End Up With

• A repeatable way to identify follow-up commitments from messages.
• A clean Todoist task format with due date, context, and source.
• A review-first workflow so AI suggestions do not create incorrect tasks automatically.

Recommended Workflow

Practical toolchain

• Outlook captures the email thread and sent follow-up context.
• Microsoft Teams captures quick commitments that rarely make it into formal notes.
• Copilot Pro or Microsoft 365 Copilot can extract candidate tasks, owners, dates, and confidence levels.
• Todoist becomes the personal execution layer once the extracted task is reviewed.
• Power Automate Desktop can later automate repetitive movement between tools, but only after the extraction rules are stable.

I would start manually with Copilot plus Todoist first. Once the task format is consistent, then automation becomes safer.

1. Select the email thread or Teams message that contains the follow-up.
2. Ask Copilot to extract commitments, owners, and due dates.
3. Review the result manually.
4. Create a Todoist task with a clear title, due date, project, and label.
5. Add the source link or short context note so the task is traceable.

Prompt Template

From this email or Teams conversation, extract only real follow-up tasks.
Return a table with:
Task title, Owner, Due date, Source, Context, Confidence.
Do not invent dates. If no due date exists, mark it as No explicit due date.

Todoist Task Format

Follow up with [person/team] on [specific outcome] due [date]
#Project @follow-up @work
Comment: Source: Outlook/Teams link or short context

Safety and Accuracy Notes

• Do not auto-create tasks without review unless the source is very structured.
• Keep personal/client-sensitive content out of screenshots.
• Use labels like @waiting, @follow-up, and @urgent only when the message clearly supports them.

Related reading

• Start with meeting transcription in Microsoft Stream
• Generate meeting minutes and action items with Copilot
• Private AI task manager and Todoist-style workflow
• Introduction to Windows Power Automate Desktop