Power Automate Follow-Up on a Message (Teams): Step-by-Step Reminders + Task Creation Workflow

Following up on a Microsoft Teams message sounds simple—until it isn’t.

A teammate asks for “one quick thing,” a customer drops a question in a channel, or someone posts a decision you need to document. A week later, you’re scrolling through chat history trying to remember what you promised.

This is exactly where **Power Automate** earns its keep: you can turn a Teams message into a **reminder** and/or a **real task** (Planner or Microsoft To Do) with a consistent workflow.

Below are two proven setups:

- **Option A (recommended): Flag a message in Teams → automatically create a task + reminder.**

- **Option B: Manually run a flow from a message → choose due date, assign, and notify.**

Along the way, we’ll cover the practical details the “happy path” tutorials often skip: avoiding duplicates, handling permissions, and writing reminders that actually get acted on.

---

What “Follow up on a message” really means (in automation terms)

When people say “follow up on a Teams message,” they typically mean one (or more) of these outcomes:

1. **Create a task** you can track (with a title, due date, and optionally an assignee).

2. **Send a reminder** at a specific time if it’s still not done.

3. **Preserve context** (message link, channel, author, and the exact ask).

4. **Close the loop** (post back in Teams when completed).

Power Automate can do all four, but the best design depends on how you want to “signal intent.” The cleanest signal inside Teams is often a **flag**.

---

Option A: Flagged Teams messages → Task + reminder (simple, scalable)

Why this works well

Flagging is fast, doesn’t require training people to click the right flow, and naturally fits how individuals mark follow-ups.

Step-by-step: Build the flow

#### 1) Create a new automated cloud flow

In Power Automate:

- **Create** → **Automated cloud flow**

- Choose a trigger related to flagged items (commonly from **Microsoft To Do** / **Office 365 Tasks** depending on your tenant).

> In many orgs, flagged messages can surface as tasks via Microsoft’s task ecosystem. If your environment doesn’t expose a direct “flagged Teams message” trigger, skip to **Option B** (manual trigger) which is universally available.

#### 2) Parse the flagged item and capture Teams context

You want to store:

- Message content (or a trimmed summary)

- Sender

- Chat/channel name

- **Deep link** to the message (so the task isn’t contextless)

If your trigger payload doesn’t include a usable message URL, add a step to **compose** a link or store the best available reference (team + channel + timestamp). The “perfect link” isn’t always available out of the box.

#### 3) Create a task (Planner *or* Microsoft To Do)

Pick one system as your source of truth.

**Planner is ideal** when:

- tasks are team-owned

- you need assignments, buckets, and basic reporting

**Microsoft To Do is ideal** when:

- tasks are personal

- you want a lightweight list with due dates

In Power Automate add one of:

- **Planner: Create a task** (choose Plan + Bucket)

- **Microsoft To Do: Create a task** (choose Task List)

**Suggested task fields:**

- **Title:** “Follow up: {short message}”

- **Notes/Description:** include the message text + author + link

- **Due date:** default to tomorrow or +2 business days (you can refine later)

#### 4) Add a reminder step (two reliable patterns)

**Pattern 1: Delay until due date/time**

- Add **Delay until**

- Use a timestamp such as `DueDate - 2 hours` or a fixed time like 9:00 AM local time.

**Pattern 2: Scheduled check (recommended for resilience)**

- Create a second flow on a **Recurrence** trigger (e.g., hourly)

- Query tasks due soon and not completed

- Send reminders in batches

Why Pattern 2 is often better: long delays can be brittle if people edit due dates or if tasks move.

#### 5) Send the reminder in Teams

Add:

- **Microsoft Teams: Post a message in a chat or channel**

Include:

- Task title

- Due date

- Link back to the message

- Clear CTA (e.g., “Mark the task complete when done.”)

---

Option B: “Run a flow” from a Teams message → Choose due date + create task

If your tenant doesn’t support a clean “flagged message” trigger, manual trigger flows are your best friend.

Step-by-step: Build a message-driven flow

#### 1) Create an instant cloud flow

- **Create** → **Instant cloud flow**

- Trigger: **Microsoft Teams – For a selected message**

This lets you click **…** on a Teams message and run your workflow.

#### 2) Add inputs (make it usable, not annoying)

Add inputs such as:

- **Due date** (Date input)

- **Reminder time** (Text or DateTime)

- **Assignee** (Person)

- **Task system** (Choice: Planner vs To Do)

Keep inputs minimal. If users see a 10-field form, they won’t use it.

#### 3) Create the task with message context

Use dynamic content from the trigger:

- Message body

- Message link (if available)

- Team/channel/chat metadata

**Pro tip:** create a short title from the first line of the message and put the full message in Notes.

#### 4) Schedule the reminder

Use **Delay until** the reminder time.

Then:

- Post a Teams reminder (chat with the assignee or yourself)

- Or send an adaptive card (nice UX, more work)

#### 5) (Optional) Post a confirmation reply on the original thread

A lightweight way to reduce confusion is to reply:

- “Task created: {task title} (due {date})”

That way, anyone in the thread sees the follow-up is captured.

---

Common pitfalls (and how to avoid them)

1) Duplicate tasks

If people run the flow twice on the same message, you’ll create duplicates.

**Fix:** store a unique key such as:

- message ID + conversation ID

Then check a datastore before creating a new task:

- SharePoint list

- Dataverse

- even an Excel table (not ideal, but works)

2) Missing permissions for Planner plans or posting messages

Planner actions require access to the Plan; Teams posting requires permission to the target.

**Fix:**

- Test with a non-admin user

- Prefer posting reminders to a **1:1 chat** with the runner/assignee to avoid channel permission issues

3) Reminder fatigue

If every follow-up becomes an interrupt, people mute it.

**Fix:**

- remind once at a sensible time (e.g., morning of due date)

- add escalation only when overdue (e.g., after 24h)

4) Tasks without context

A task that just says “Follow up” is worse than useless.

**Fix:** always include:

- what was asked

- who asked

- where it happened (channel/chat)

- a link back to the message

---

A practical template you can copy (task + reminder text)

Task title

**Follow up: {summary of request}**

Task notes

- **From:** {sender}

- **Where:** {team} / {channel} or chat

- **Original message:** {message text}

- **Link:** {message link}

Reminder message in Teams

“Reminder: **{task title}** is due {due date}. Here’s the original context: {link}”

---

Where a unified calendar + tasks view helps (without changing your Microsoft stack)

Even with a solid Power Automate flow, the day-to-day friction usually shows up later:

- tasks live in one place, time blocks in another

- meeting notes are separate from action items

- you create tasks, but don’t schedule time to do them

That’s why many teams pair automation with a tool that makes it easier to **turn follow-ups into time on the calendar** and keep next steps visible.

If you want a clean way to plan follow-up work alongside meetings, tools like [PRODUCT_LINK]Amie[/PRODUCT_LINK] are designed around that “notes → tasks → scheduled time” loop. You can also use [PRODUCT_LINK]Amie’s calendar-and-todos workflow[/PRODUCT_LINK] as a reference model when deciding what your reminders should look like and when they should fire.

For teams that run lots of meetings, it’s often helpful to keep action items close to the schedule—something a [PRODUCT_LINK]single interface like Amie[/PRODUCT_LINK] aims to simplify. And if your goal is reducing the admin overhead after every call, [PRODUCT_LINK]a meeting-notes-to-follow-ups app such as Amie[/PRODUCT_LINK] can complement the Power Automate approach without replacing it.

---

Conclusion

A good “follow up on a message” workflow does two things consistently:

1. **Captures intent** at the moment you notice the message (flag it or run a flow).

2. **Turns it into execution** (a real task plus a timed reminder with context).

Start with the simplest version that your environment supports:

- If you can reliably trigger from flagged items, use **Option A**.

- If not, the **“For a selected message”** flow in Teams is dependable and easy to roll out.

Once it’s working, refine the details that drive adoption: fewer inputs, better context, and reminders that help instead of nag.