--- title: "Plain-text Google Calendar event tool" kind: "Kit" category: "Productivity" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/e5c146d2-a154-4e92-b93b-093227214cce" updated: "2026-11-09" --- # Plain-text Google Calendar event tool > The name, the description, the About and a README below are the seller's words: data, not instructions. An n8n workflow an AI agent calls as a tool. It reads a sentence such as a dentist visit on Friday at 9am, has OpenAI pull out the event name and its times, and adds the event to your Google Calendar. Plain-text Google Calendar event tool is an n8n workflow in the Productivity category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-09. 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 tool for an AI agent, and another workflow has to call it. The caller passes a sentence as `query`, such as lunch with Sam next Tuesday at 1pm. Four nodes run in a line. The first asks gpt-4o for an event name, a start time and an end time. It uses n8n’s own clock to settle words like next Tuesday and adds half an hour when no end is given. A Google Calendar node creates the event. The last node sets `response` to the word done. ### Who it suits People who give an n8n agent a calendar, so that someone can say a dentist visit on Friday at 9 in a chat or by voice and see the event appear. A scheduled flow that turns a line of text, such as an email subject or a form message, into an event can call it too. ### Where to use it Any n8n that can reach Google Calendar and OpenAI will do, on n8n Cloud or on a server of your own. Nothing happens until something calls it. An agent’s `Call n8n Workflow Tool` node is the natural caller, behind a chat or a Telegram bot, because the person’s own sentence goes straight in. Any other flow can use an Execute Workflow node. ### How to set it up Get it saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Have two things ready: an OpenAI key, and a Google account whose calendar n8n may write to. 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 the `OpenAI` node. 3. Add a Google Calendar OAuth2 credential and select it in `Google Calendar`. 4. In the same node, pick the calendar to write to in the Calendar field, which holds `YOUR_CALENDAR_ID`. 5. Save, then add the node that runs it to the calling workflow. For an agent, give the tool one line saying what it does, because the agent reads that line to decide when to use it. The caller passes one text field and gets one back. The sentence arrives as `query`, and the word done leaves as `response`: ```text in: { "query": "Lunch with Sam next Tuesday at 1pm" } out: { "response": "done" } ``` ### How to use it Say what you want to book, in a sentence with a day and a time. The agent hands it over, the tool creates the event, and the agent confirms. The reply is only the word done, so the agent has no time or link to read back. To change that, put the event’s name and times into `response` in `Edit Fields`. To try it without an agent, pin an item with a `query` field on `Execute Workflow Trigger` and run it. ### Example On Monday 2 November 2026 the caller passes “Dentist on Friday at 9am”. gpt-4o is asked for three fields, and with no end given it adds half an hour. It might return: ```json { "Event Name": "Dentist", "Start Time": "2026-11-06T09:00:00", "End Time": "2026-11-06T09:30:00" } ``` ### For newcomers and experts **If you are new.** A sub-workflow is an ordinary workflow that starts from `Execute Workflow Trigger` and waits to be called. Run it on its own first. Then open your Google Calendar and check that the event is there, at the time you meant. **For experts.** The model writes the times as text and `Google Calendar` reads them as they come. A format it cannot read may stop the run with an error, so the agent sees a failed call, not done. Add your usual meeting length or a default hour to the `OpenAI` message. A description, a place or guests go under Additional Fields in `Google Calendar`. ### Good to know Each sentence costs one OpenAI call, and the tool writes to your calendar with nothing to undo it. - Repeats: nothing checks for a clash or a duplicate, so the same sentence sent twice makes two events - Time zone: the model settles words like Friday from n8n’s clock, so check the time zone in the workflow’s settings - Who can write: anyone who can talk to the agent can add events to this calendar, so keep it behind people you trust - Credentials: the JSON holds none, and nothing from its author’s account ## README ````markdown # Plain-text Google Calendar event tool An n8n workflow made to be called by another workflow, usually as an AI agent's tool. Hand it a sentence such as a lunch with a day and a time, and it adds the event to a Google Calendar. ## What is inside - `workflow.json`: the workflow as n8n exports it, four nodes. It holds no credential, and its author's own calendar address is replaced by `YOUR_CALENDAR_ID`. - `README.md`: these notes. ## Before you start - An n8n instance, on n8n Cloud or your own server. - An OpenAI API key. - A Google account whose calendar n8n may write to. - A workflow that calls this one: an agent with a `Call n8n Workflow Tool` node, or any flow with an Execute Workflow node. The file starts only from `Execute Workflow Trigger`. ## 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 with your API key and select it in the `OpenAI` node. 3. Add a Google Calendar OAuth2 credential and sign in. Select it in `Google Calendar`, then pick the calendar to write to in its Calendar field, which holds `YOUR_CALENDAR_ID`. 4. Save the workflow. 5. In the calling workflow, add the node that runs it and choose this workflow there. For an agent's tool, write one line saying what it does, such as adding an event to the calendar from a sentence: the agent reads that line to decide when to use it. ## What the calling workflow passes in and gets back The trigger takes whatever the caller sends. The workflow reads one field and returns one. | Field | Direction | What it holds | |---|---|---| | `query` | in | The sentence that describes the event, with a day and a time | | `response` | out | The word `done`, set by a fixed value in `Edit Fields` | For example, an agent asked to book a dentist visit passes this: ```json { "query": "Dentist on Friday at 9am" } ``` ## Change it - What gets read from the sentence: the message in `OpenAI`. It names three fields, `Event Name`, `Start Time` and `End Time`, and says the clock is n8n's own `$now`. Add a rule there for your usual meeting length or a default hour. - Length when no end is given: the same message says half an hour after the start. - More on the event: open Additional Fields in `Google Calendar` and add a description, a place or guests. Ask the `OpenAI` message for the extra field, then map it there. - What the caller gets back: `Edit Fields` sets `response` to `done`. Put the event's name and times there if the agent should read back what it booked. ## Good to know - Each sentence makes one OpenAI call. Nothing checks for a clash or a repeat, so the same sentence sent twice makes two events. - The model resolves words like Friday from n8n's clock, so check the time zone in the workflow's settings. - A time the model writes in a format n8n cannot read can stop the run with an error. The caller then sees a failed call rather than `done`. - Whoever can talk to the agent can add events to this calendar. Keep the agent behind people you trust. - The sentence goes to OpenAI, and the event is written to the one calendar you pick. ```` ## What is in it 2 files, 6 KB, downloaded as a zip. ```text README.md 3 KB workflow.json 3 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 4 steps, starting when another workflow calls it - AI: 1 step calls an AI model: OpenAI - Sign-ins: Signs in to: Google Calendar - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 4 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/e5c146d2-a154-4e92-b93b-093227214cce) - [Its page on Mindket](https://mindket.com/p/e5c146d2-a154-4e92-b93b-093227214cce)