Sender importance is a poor proxy for message importance
Sender importance is the default sort because it is simple, and it is almost always wrong. The most important person on your list usually sends the least urgent message. A junior colleague sends the one that stops a release.
The request determines urgency. A blocker to your decision matters more than a lengthy update from anyone. Only the content tells the difference.
Deadlines are usually not stated as dates. "before the release" is a deadline only if you know the release date. A system that reasons only from explicit dates will miss most of these cases.
A fourth type of message should be identified: messages that require you to know something but ask for nothing in return. Put those in a digest, not in a queue. Mixing them with everything else is what makes the inbox look infinite.
How the agent is built in Agent Studio
What you need is a personal definition. Write the system prompt in the first person, because it names the decisions only you make, the projects you own, and the people whose requests you never want to batch.
Prompt skills hold your current commitments and deadlines, so the agent can read "before the release" as a date.
A Start Scheduled flow assembles the backlog. Slack, Discord, and Email nodes read the channels. The Filter node removes notifications and automated messages. The Agent Chat node then forwards the rest. The result is four groups instead of a ranked list: those that need a decision, those that need a reply, those that need you to know, and those that need nothing. You can deal with four groups. You cannot deal with a ranked list of sixty.
A Slack node delivers the groups that need a decision or a reply. A Notion node holds the group that needs you to know as a digest.
Google Sheets records the items the agent deprioritized and those you later escalated yourself. Use that record to adjust the system prompt. Review it once a week during the first month.
What this agent is built from
- System prompt: written in the first person, covering the decisions only you make and the people never to batch.
- Prompt skills: current commitments and deadlines, so implicit dates can be read.
- Slack (Communication): reads the channels alongside Discord and Email.
- Filter (Data): drops notifications and automated messages before anything is read.
- Agent Chat (Util): a scheduled flow hands off the human messages.
- Notion (Integration): holds the “needs you to know” group as a digest rather than a queue.
- When an ActionFlow is enough: If a keyword or sender rule catches the obvious cases, use a workflow. The agent is for the ones the rule keeps missing.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.