When should you use it?
- Routine admin eats your focus every day
- You want scheduling and follow-ups handled for you
- You can start with one workflow and expand
Not for: Letting it send or schedule for VIPs without confirmation; Automating everything at once before testing
What do you need, and what do you get?
You need
- A visual automation tool and connected accounts
- Access to email, calendar and a task tool
- Safety rules for quiet hours and approvals
You get
- An inbox filtered to what matters
- Invites checked against your calendar
- Follow-up reminders that stop things slipping
How does it work, step by step?
- Start with one workflowBegin with email triage, test it for a week, then add more.
- Let it handle invitesDetect calendar invites, check for conflicts and propose or accept times.
- Turn words into tasksHave it parse natural-language requests into tasks with due dates and priority.
- Automate follow-upsTrack items waiting on others and send polite reminders so nothing is dropped.
- Add safety checksBlock late-night sends, require approval for VIP emails, and confirm before scheduling.
The prompt
The original prompt by Nova, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in n8n. Values in lime are placeholders.
Original prompt by Nova
You are a personal AI assistant. Analyze the user's request and categorize it into one of these actions: - EMAIL: User wants to send, check, or manage emails - CALENDAR: User wants to schedule, check, or manage calendar events - TASK: User wants to create, update, or check tasks - GENERAL: General questions or conversations Respond with just the category name, nothing else.
Exactly as published by Nova in How I Built a Personal Assistant AI Agent with n8n in 2 Hours (No Code Step-by-Step).
Our adapted version (optional)
Build a personal assistant workflow that: filters my inbox to only messages needing attention; detects calendar invites and checks my calendar for conflicts before proposing or accepting times; turns requests like 'nudge me next Friday about the proposal' into tasks with due dates; and sends polite follow-up reminders for items waiting on others. Add safety rules: no sends between 10pm and 8am, and confirm before scheduling with VIPs.
What can go wrong?
- An early version emailed the wrong people and scheduled at 2am; add guardrails before trusting it.
- Automating everything at once hides which part broke; expand one workflow at a time.
Our take
Nova's write-up is valuable mainly for its candor about what went wrong. An assistant left without guardrails behaved like an overeager new hire, sending messages and accepting meetings at absurd times, until rules were added. Put those rules in before the first run, not after the first embarrassment. Good starting limits: nothing sends without a draft you approve, no meetings accepted outside working hours, and no messages to family or clients without review. Build one workflow at a time, beginning with inbox triage, which only reads and labels, then invite handling, then follow-ups, so you can see which piece causes trouble. The natural-language task creation is the quiet win, since turning a passing phrase into a dated, prioritized task removes the friction that makes people abandon task apps. Check how the tool stores email content and credentials, especially if you self-host, and keep access tokens out of shared workflow exports. Review the assistant's actions weekly for a month; most problems show up as small oddities before they become real mistakes.
Where the time goes back: The daily drag of invites, replies and reminders moves off your plate, after a week of setup, so routine admin stops owning your attention.
FAQ
Where should I start?
How do I avoid embarrassing mistakes?
Source and credit
The original prompt on this page is by Nova, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- How I Built a Personal Assistant AI Agent with n8n in 2 Hours (No Code Step-by-Step)
- Creator
- Nova
- Published on
- DEV Community (dev.to)
- Original date
- Mar 28, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- n8n
- 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 23, 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.