← Back to library

Create calendar entries by typing a sentence into n8n chat

Soham Mehta's freeCodeCamp tutorial shows a tiny n8n assistant for personal scheduling: a chat trigger receives a message, an AI Agent node with a clock tool extracts the event details, and structured output creates the calendar entry you asked for.

  • OutcomeType an event in plain words and have it appear in Google Calendar with title, place and times filled in.
  • SetupUnder an hour
  • LevelStarter
  • CreditSoham Mehta
View original
Works with
n8nChatGPT

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 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?

  1. Add a chat triggerStart with a node that listens for messages; optionally make the chat public.
  2. Add the agentConnect a chat model and give it a date-time tool so relative dates resolve.
  3. Define structured outputRequest name, place and timing as separate fields.
  4. Create the eventFeed the extracted fields to the Google step that saves the entry.
  5. 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.

Prompt0 variables
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?
So the agent knows today's date when someone says tomorrow.
Can others use it?
The tutorial enables a public chat URL friends can use to put events on your calendar.

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.

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

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

Ask one narrow assistant in Slack to triage email, check your schedule or add a task, with sending and deleting held for your confirmation.

Credit: Wyndo

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Confirm padel court times from a chat channel

Customers book, change or cancel courts by chatting, while a deterministic workflow assigns courts and prevents clashes.

Credit: u/PriceNew5674 on r/n8n

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Schedule meetings from email threads with locks

Meeting requests in your inbox get answered with times you're really free, and confirmed meetings appear on your calendar.

Credit: u/BigFollowing9345 on r/SideProject

Under an hour