When should you use it?
- You want a first n8n agent project
- You often type events into chat anyway
- You want others to request time via a link
Not for: Calendars that need approval rules; Complex recurring events
What do you need, and what do you get?
You need
- n8n account
- Model credentials
- Google Calendar connection
You get
- Calendar event created from a message
How does it work, step by step?
- Add a chat triggerStart with a node that listens for messages; optionally make the chat public.
- Add the agentConnect a chat model and give it a date-time tool so relative dates resolve.
- Define structured outputRequest name, place and timing as separate fields.
- Create the eventFeed the extracted fields to the Google step that saves the entry.
- Test edge casesTry phrases like next Friday afternoon and fix the prompt.
The prompt
Our own prompt, inspired by Soham Mehta and written to work in n8n and ChatGPT. Values in lime are placeholders.
You turn a message into one calendar event. Today's date and time come from the date tool. Extract: title, location (or blank), start and end in ISO format (default one hour if no end given), and a one-line description. If the date is ambiguous, ask a single clarifying question instead of guessing. Return only these fields as JSON.
Inspired by Soham Mehta: How to Build AI Workflows with n8n. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Without the current date, relative times land on the wrong day.
- A public chat link lets anyone add events; share carefully.
Our take
A good starter project because each part is visible: trigger, model, tool, structured output, action. If you share the chat publicly, add a step that sends you the event for approval instead of writing straight to the calendar. Soham's tutorial is a clean introduction to agent building because every part does one visible job. The detail people skip is the clock tool. Without the current date, phrases like next Friday afternoon land on the wrong day, so give the agent a date-time tool and test relative phrases early. Ask for structured output with name, place and timing as separate fields; it makes the calendar step reliable and easy to debug. A public chat link lets anyone create events, so share it carefully or route requests to you for approval. Check time zones and daylight saving changes with a few test entries, and know how to delete a wrong event quickly. Complex recurring events are better entered by hand.
Where the time goes back: Adding an event takes one sentence instead of filling a form.
FAQ
Why a date-time tool?
Can others use it?
Source and credit
Inspired by Soham Mehta. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How to Build AI Workflows with n8n
- Creator
- Soham Mehta
- Published on
- freeCodeCamp.org
- Original date
- Oct 13, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and 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 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.