--- title: "Google Calendar day summary tool" kind: "Kit" category: "Productivity" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/38c04cbc-878c-442a-b53e-fa22a4926ed5" updated: "2026-11-09" --- # Google Calendar day summary 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. Given a question about a day, such as tomorrow, it works out the date with OpenAI, reads that day’s Google Calendar events and returns a short summary of each. Google Calendar day summary 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 the user’s question as `query`, such as what is on tomorrow. Seven nodes run in a line. The first asks gpt-4o which day the question means, from n8n’s own clock, and gets that day and the next one back. A Google Calendar node reads the events between them, ten at most. Two more nodes keep each event’s name and times and have gpt-4o write a note on it. The last two join the notes into a `response` field. ### Who it suits People who build an n8n agent that answers questions about a schedule, from a chat or a voice message, and want the calendar part ready as one tool. Anyone with no agent can still use it from a scheduled workflow that calls it with `query` set to today. ### 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 usual caller, behind a chat or a Telegram bot. An Execute Workflow node in a morning schedule works too, with the next node sending the reply on. ### 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 read. 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 `Find Current Date` and in `Summarize Calendar`. 3. Add a Google Calendar OAuth2 credential and select it in `Google Calendar`. 4. In the same node, pick your calendar 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 agent’s words arrive as `query`, and the notes leave as `response`: ```text in: { "query": "What is on my calendar tomorrow?" } out: { "response": "" } ``` ### How to use it Ask the agent about a day in its own words. It hands the question to the tool, which works out the date. The agent then builds its answer from `response`. To try it without an agent, pin an item with a `query` field on `Execute Workflow Trigger` and run the workflow from the editor. ### Example Ask about tomorrow on a day that holds a stand-up and a dentist visit. `Find Current Date` answers with the two dates below, `Google Calendar` returns both events, and `Summarize Calendar` writes a note on each, which the agent gets in `response`: ```json { "Requested day": "2026-11-03", "Next day": "2026-11-04" } ``` ### 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. Every node shows what it received and what it sent, so a wrong date or an empty calendar turns up there before an agent is involved. **For experts.** Both OpenAI nodes use gpt-4o, and the note-writing node makes one call per event, so a full day costs eleven calls. A question about next week still gets one day’s range, because the date node is asked for a single day. Raise `limit` for busier days. Rewrite the date node’s prompt if the agent should ask for longer ranges. ### Good to know Each question costs money. The event names leave your calendar for OpenAI too. - Billing: OpenAI charges for the date call and for each event’s note - All-day events: Google gives them a date and no time, and the workflow reads times, so their start and end arrive empty - Time zone: the day comes from n8n’s clock, so check the time zone in the workflow’s settings - Credentials: the JSON holds none, and nothing from its author’s account ## README ````markdown # Google Calendar day summary tool An n8n workflow made to be called by another workflow, usually as an AI agent's tool. Hand it a question about a day and it returns a short summary of each event on that day. ## What is inside - `workflow.json`: the workflow as n8n exports it, seven 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 you want read, and permission to sign n8n in to it. - 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. Select it in `Find Current Date` and in `Summarize Calendar`. 3. Add a Google Calendar OAuth2 credential and sign in. Select it in `Google Calendar`, then pick your calendar 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 looking up what is on the calendar for a day: 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 question about a day, in plain words | | `response` | out | The summaries of that day's events, gathered into one field | For example, an agent asking about tomorrow passes this: ```json { "query": "What is on my calendar tomorrow?" } ``` ## Change it - Number of events: `limit` in `Google Calendar`, ten as exported. - What each summary says: the message in `Summarize Calendar`. It is given the event's name and its start and end times, so add a field to `Edit Fields` and to that message to bring in a place or a description. - Which day it reads: the message in `Find Current Date`. It asks for one day, so a question about a whole week still gets one day's range. - Model: both OpenAI nodes use gpt-4o. ## Good to know - Each question makes one OpenAI call for the date and one call per event, so eleven at most with the default limit. - Google gives an all-day event a date and no time. The workflow reads the times, so those events arrive with empty start and end. - The event names and times go to OpenAI. Only the calendar you pick is read. - The date comes from n8n's clock, so check the time zone in the workflow's settings. ```` ## What is in it 2 files, 9 KB, downloaded as a zip. ```text README.md 3 KB workflow.json 6 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 7 steps, starting when another workflow calls it - AI: 2 steps call an AI model: Find Current Date and Summarize Calendar - Sign-ins: Signs in to: Google Calendar - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 5 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/38c04cbc-878c-442a-b53e-fa22a4926ed5) - [Its page on Mindket](https://mindket.com/p/38c04cbc-878c-442a-b53e-fa22a4926ed5)