← Back to library

Command a narrow inbox, schedule and to-do bot in Slack

Wyndo, tired of mail, calendar and to-dos that never talked to each other, built one narrow Make agent he drives from Slack. It labels mail, drafts replies, manages calendar and Notion tasks, and waits for confirmation before sending or deleting.

  • OutcomeAsk one narrow assistant in Slack to triage email, check your schedule or add a task, with sending and deleting held for your confirmation.
  • SetupAn afternoon+
  • LevelIntermediate
  • CreditWyndo
View original
Works with
MakeChatGPTn8n

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • You juggle email, calendar and a task app all day
  • You already live in Slack
  • You prefer typed commands to another dashboard

Not for: Shared inboxes where others expect human replies; Fully autonomous sending

What do you need, and what do you get?

You need

  • Connections to your mailbox, schedule and task database
  • A Slack bot
  • Your label set, such as urgent or follow-up

You get

  • Daily triage summary
  • Calendar events with conflict warnings
  • Notion tasks with project, priority and due date

How does it work, step by step?

  1. Pick the toolsConnect mail, calendar and the task database in an automation platform with an AI agent step.
  2. Define each tool actionList exactly what it may do: label, search, summarize, draft, create event, create or update task.
  3. Gate the risky onesRequire an explicit yes before it sends mail or deletes an event.
  4. Wire Slack as the front doorRoute your messages to the agent and its answers back to the same thread.
  5. Start with three commandsUse triage yesterday's mail, what's on today and add a task until you trust the routing.

The prompt

Our own prompt, inspired by Wyndo and written to work in Make, ChatGPT and n8n. Values in lime are placeholders.

Prompt0 variables
You are my assistant inside Slack. You can reach my mail, my calendar and the task list in Notion. When I ask, you may: label and summarize email from a time range, draft replies, show my schedule, create events and warn about conflicts, and create, update or list tasks with project, priority and due date. Before sending any email or deleting any event, show me what you will do and wait for yes. If a request is unclear, ask which tool I mean.

Inspired by Wyndo: I Built an AI Agent That Actually Manages My Email, Calendar, and Tasks. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • A do-everything prompt routes badly; keep the action list short and named.
  • Watch API spend if you let it summarize large inboxes daily.

Our take

Useful mostly because of what it refuses to be. He had argued that broad agents are unreliable, then showed that a narrow one with three jobs can still earn trust. The design lesson is to name a short list of actions and refuse everything else: label, search, summarize, draft, create an event, create or update a task. Wyndo gated the two risky moves, sending mail and deleting events, behind an explicit yes, and that is the minimum for anything touching your inbox. Driving it from a Slack thread you already watch removes yet another dashboard. Start with the three commands he suggests and add more only once the routing proves reliable; a do-everything prompt sends requests to the wrong tool. Daily summaries of a large inbox can run up API spend, so watch usage in the first month. Shared inboxes, where other people expect a human reply, are a poor fit. This is a personal assistant with a deliberately small job.

Where the time goes back: It removes the small cross-tool decisions, like whether an email needs a calendar block, that eat attention all day.

FAQ

Is this a general assistant?
No. The author's point is that a narrow agent with a few tools works where a catch-all one does not.
Can it send email by itself?
Only after you confirm in the thread.

Source and credit

Inspired by Wyndo. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I Built an AI Agent That Actually Manages My Email, Calendar, and Tasks
Creator
Wyndo
Published on
aimaker.substack.com (Substack)
Original date
Dec 18, 2025
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Make
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Answer meeting-request emails with specific open times

Emails that ask for a meeting are spotted automatically and answered with concrete times that fit your calendar, with a buffer between meetings.

Credit: n8n Team (n8n-team)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Build a funding database from grants found online

Have an automation agent search the web for grants by country and add each one to a structured table you can review and publish.

Credit: u/Ste_XD on r/zapier

Under an hour