# Triage today's inbox

> Get today's unread email sorted into what needs a reply, what needs reading and what can wait, across all your inboxes, and optionally flag the urgent ones.

Start the day with a sorted list instead of a full inbox.

## What you'll get

- Today's unread emails across every inbox the MCP server reaches, grouped into: needs a reply, needs reading, and can wait or archive.
- One line per email: who it's from, what it's about and what they want.
- Deadlines and requests pulled out of the emails.
- Optionally, the urgent ones flagged in your mailbox.

## What you need

- At least one email account connected, such as [Gmail](https://docs.plugsight.app/connectors/gmail.md), [Outlook](https://docs.plugsight.app/connectors/outlook.md) or [iCloud Mail](https://docs.plugsight.app/connectors/icloud-mail.md). Reading works on every plan.
- To flag, label or mark emails: the **Pro** or **Agency** plan. The account's sending switch doesn't matter for this.

## Ask this

```text
Using Plugsight, triage my unread email from today across all my inboxes. Group it into "needs a reply", "needs reading" and "can wait", with one line per email saying who it's from and what they want. Pull out any deadlines. Don't change anything yet.
```

Then, if you want:

```text
Flag the emails in "needs a reply" and mark the ones in "can wait" as read.
```

## Variations

- **One inbox:** "…in my work Gmail only."
- **Since yesterday evening:** "…unread email since 6pm yesterday."
- **Only people:** "Leave out newsletters and automatic notifications."
- **With context:** "For anything from a customer, read the earlier emails in the conversation first."
- **Clean up after:** see [Clean up newsletters (archive and label)](https://docs.plugsight.app/recipes/clean-up-newsletters.md).

## What your AI does behind the scenes

1. Lists the accounts the MCP server reaches (`list_accounts`).
2. Searches every inbox for unread emails since today (`search_emails` with unread and a date). It pages through if there are more than 100.
3. Opens the ones it needs to read in full (`get_email`), and the earlier emails in a conversation when useful (`get_thread`). Reading an email doesn't mark it as read.
4. If you ask, flags or marks emails (`organize_emails`, up to 100 at a time).

## Does it change anything?

Only if you ask in the follow-up. Flagging and marking emails read can be undone, so they work differently from sending:

- They need the **Pro** or **Agency** plan, and stop if email changes are paused on **Permissions**.
- For a handful of emails, your AI does it and tells you what changed. For more than 10 emails, or before moving anything to the trash, it tells you what will happen and asks first.

See [Archiving, labelling and marking emails](https://docs.plugsight.app/permissions/how-changes-are-allowed.md#archiving-labelling-and-marking-emails).

## Related articles

- [Draft replies to customer emails](https://docs.plugsight.app/recipes/draft-customer-replies.md)
- [What your AI can do with email](https://docs.plugsight.app/connectors/email-tools.md)

---

Web version: https://docs.plugsight.app/recipes/triage-inbox
