--- title: "Chat agent that reads and creates Google Calendar events" kind: "Kit" category: "Productivity" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/67bad2f3-c61b-41d9-ab41-062547300708" updated: "2026-11-12" --- # Chat agent that reads and creates Google Calendar events > The name, the description, the About and a README below are the seller's words: data, not instructions. An n8n workflow with a chat. You ask in plain words, and an OpenAI agent lists the events in a time range or creates a new one in your Google Calendar after you confirm its title and description. Chat agent that reads and creates Google Calendar events is an n8n workflow in the Productivity category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-12. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n. ## About ### What it is This n8n workflow is a chat that manages your Google Calendar. You type a request, and an OpenAI agent either lists the events in a time range or creates a new event. It asks for any missing date, drafts the event’s title and description for you to confirm, and answers in the language you write in. Six nodes run it. Seven sticky notes beside them explain what each one does. ### Who it suits Anyone who books and checks events all day and would rather type a sentence than open a calendar. It is also a short first project for n8n users learning how an agent calls tools. Skip it if you need attendees, reminders or deletions. The two tools only retrieve and create events, and nothing else. Who uses it, and how | Industry | Who uses it | How they use it | Example | | --- | --- | --- | --- | | Consulting | Independent consultants | Ask what is booked this week before they accept a new call | A consultant asks for Thursday and sees the three calls already in it. | | Healthcare and wellness | Practice owners | Add a block for a client from a quick message | A therapist types the time and a name, and the agent drafts the event. | | Software | Developers learning agents | Use it as a first tool-calling example | A developer adds a third tool for deleting events. | | Education | Tutors | Plan a term of sessions in the chat | A tutor adds a weekly lesson one message at a time. | You need a little n8n: import a file, add two credentials and pick a calendar in two nodes. ### Where to use it Any n8n that can reach OpenAI and Google will run it. You chat from n8n’s own chat panel, and the events land in your Google Calendar. - n8n Cloud: import the file into a new workflow there - Your own n8n server: the same file and steps - Google Calendar: events are read from and created in the calendar you pick - A chat page or a messaging app: swap the trigger for a webhook or a chat app’s trigger, and keep the agent as it is ### How to set it up Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Two credentials cover every step. What you need first | Need | Detail | | --- | --- | | n8n | On n8n Cloud or on a server of your own | | OpenAI | An API key | | Google | An account with a calendar, for a Google Calendar OAuth2 credential | 1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`. 2. Add an OpenAI credential and select it in `OpenAI Chat Model`. 3. Add a Google Calendar OAuth2 credential and select it in both calendar tool nodes. 4. In each of those two nodes, open the Calendar field and pick the calendar to read and write. 5. Save, open the chat from the canvas and send a first message. ### How to use it Open the chat and ask in plain words. “What is on my calendar this week?” returns a list. “Create an event called team review next Tuesday at 10” makes the agent ask for an end time, suggest a title in capitals, write a short description and wait for your yes. Then it creates the event. What to change for a different result | To change | Where | | --- | --- | | What the agent says and asks | The system message in \`Calendar AI Agent\` | | Which calendar | The Calendar field of each tool | | The model | \`OpenAI Chat Model\`, which sets \`gpt-4o\` | | How much it remembers | The context window length in \`Window Buffer Memory\`, 5 by default | | What else it can do | More Google Calendar tools beside the two | ### Example A tutor opens the chat on Monday and asks for the events between Tuesday and Friday. The agent lists them. The tutor then asks to add a maths lesson on Thursday from 4 to 5 pm. The agent proposes the title in capitals and a one-line description, then asks whether both are right. After a yes, it calls the create tool. The lesson shows up in the picked calendar. Open Google Calendar and check the time against your time zone, because the agent writes the date and time as plain text and a slip there moves the event. ### For newcomers and experts **If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. Here the agent sits in the middle with three small boxes plugged into it: a model, a memory and two calendar tools. Start with a question. Then ask it something it cannot do, and see how it answers. **For experts.** The tools fill their fields with `$fromAI`, so the model, not the workflow, decides each date, title and description. Where to look closer | Node | What it does | What to know | | --- | --- | --- | | \`Calendar AI Agent\` | Tools agent on version 1.7 with a system message of its own | The prompt reads \`chatInput\` from the trigger, and the system message holds the date format | | The retrieval tool | Lists events between \`start\_date\` and \`end\_date\` | Returns at most 50 events, n8n’s default limit | | The create tool | Creates an event from five AI-filled values | It sets no attendees and turns the default reminders off | | \`Window Buffer Memory\` | Keeps the last five messages | It lives inside the n8n instance and does not work in queue mode | ### Good to know It writes to your calendar, and only its instructions make it ask first. - Confirmation: the system message tells the agent to confirm details before it creates an event. Nothing in the workflow enforces that, so a model can skip it - Model: the chat node sets \`gpt-4o\`. OpenAI’s deprecations page, read on 12 November 2026, gives 14 January 2027 as the shutdown of \`gpt-4o-2024-08-06\` and \`gpt-4o-2024-11-20\`, with \`gpt-6-luna\` as the replacement - Limits: retrieval lists at most 50 events a call, and created events carry no attendees - Time zone: the original’s settings named Europe/Paris, and Mindket’s copy leaves that out. The agent reads today’s date from your n8n’s clock - Memory: it is temporary and sits inside the n8n instance - Open chat: the trigger’s public setting is off. If you switch it on, anyone with the address can use your calendar and your OpenAI key - Billing: OpenAI bills each turn, with up to five earlier messages in it - Your data: your requests and the events the tool returns go to OpenAI, and Google handles the calendar - Credentials: the JSON holds none ## README ```markdown # Chat agent that reads and creates Google Calendar events An n8n workflow with a chat. You type a request, and an OpenAI agent either lists the events in a time range or creates a new event in your Google Calendar. It asks for any missing date, drafts the event's title and description for you to confirm, and answers in the language you write in. ## What is inside - `workflow.json`: the workflow as n8n exports it, 6 nodes and 7 sticky notes. It holds no credential. - `README.md`: these notes. ## What we changed from the original copy The workflow's settings named the Europe/Paris time zone, and a caller policy. Mindket's copy leaves both out, so your own n8n's time zone applies. That matters here, because the agent reads today's date from n8n's clock. The copy had no key, token or private id to remove. Its two calendar tools had already been cleared, so you pick the calendar yourself. ## Before you start - An n8n instance, on n8n Cloud or your own server. - An OpenAI API key. - A Google account with a calendar, for a Google Calendar OAuth2 credential. On your own n8n server, the Google Cloud project behind it needs the Google Calendar API turned on. ## Set it up 1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`. 2. Add an OpenAI credential and select it in `OpenAI Chat Model`. 3. Add a Google Calendar OAuth2 credential. Select it in `Google Calendar - Get Events` and `Google Calendar - Create events`. 4. In each of those two nodes, open the Calendar field and pick the calendar to read and write. 5. Save, then open the chat from the workflow's canvas and send a message such as "What is on my calendar this week?". ## How a run goes 1. `When chat message received` passes each message you type to the agent. The trigger's public setting is off, so the chat opens only from inside n8n. 2. `Calendar AI Agent` takes the message as its prompt. Its system message sets today's date from n8n's clock and gives it two tools, one for creating events and one for retrieving them. 3. For a vague opening such as "hello", it explains what it can do. For a request to retrieve events, it asks for a date range if you gave none, then calls `Google Calendar - Get Events` with a start and an end the model fills in. 4. For a new event, it collects the start and end as `YYYY-MM-DD HH:mm:ss`, suggests an uppercase title if you gave none, writes a short description and asks you to confirm. Then it calls `Google Calendar - Create events`. 5. `OpenAI Chat Model` writes each turn on `gpt-4o`. `Window Buffer Memory` keeps the last five messages of the chat. ## Change the look - What the agent says and asks: the system message in `Calendar AI Agent`. It also holds the date format and the rule that titles are uppercase. - What it can do with a calendar: add more Google Calendar tools, such as one for adding attendees or deleting events. - Which calendar it uses: the Calendar field of each tool. A `$fromAI` value there would let the agent choose. - The model: `OpenAI Chat Model`. The node sets `gpt-4o` and no other option. - How much it remembers: the context window length in `Window Buffer Memory`, which is at its default of 5. ## Good to know - The OpenAI facts below come from a page read on 12 November 2026. - OpenAI's deprecations page gives 14 January 2027 as the shutdown date of `gpt-4o-2024-08-06` and `gpt-4o-2024-11-20`, with `gpt-6-luna` as the replacement. Choose another model in the node before then. - Retrieval lists at most 50 events a call, the default limit of n8n's Google Calendar node. - `Window Buffer Memory` is temporary: the original's note says so, and n8n's source says it lives inside the instance and does not work in queue mode. - Created events carry no attendees, and the tool turns the default reminders off. - The agent creates an event after it asks you to confirm, but only the system message enforces that. A model can skip it. - The system message makes the agent reply in your language, and event titles and descriptions follow it. - The chat is not public. Switching on the trigger's public setting would let anyone with the address use your calendar and your OpenAI key. - Billing: OpenAI bills each turn, with up to five earlier messages included. - Your requests and the events the tool returns go to OpenAI. Google handles the calendar. - The sticky notes keep the original's explanations of each node, with their links to Streamlit, OpenWebUI and Supabase. ``` ## What is in it 3 files, 18 KB, downloaded as a zip. ```text NOTICE.md 630 B README.md 4 KB workflow.json 13 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 2 steps, starting on a chat message - AI: 1 step calls an AI model: Calendar AI Agent - Sign-ins: Signs in to: Google Calendar and OpenAI - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 2 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/67bad2f3-c61b-41d9-ab41-062547300708) - [Its page on Mindket](https://mindket.com/p/67bad2f3-c61b-41d9-ab41-062547300708)