Most of us run the day from a calendar we only look at when something is about to go wrong. The 9am call surprises you at 8:58, and the afternoon block you set aside for real work has quietly been eaten by an invitation you accepted on your phone last Tuesday.

The fix is small and a little old-fashioned. Read the day before it starts, in the one place you already check first thing, which for most people means the inbox. This tutorial builds exactly that in n8n, the open-source workflow automation tool: every weekday at 7am it reads today's events from Google Calendar, tidies them into a short list, and emails the list to you with Gmail.

It is a good first automation for a solo founder, a freelancer or anyone who runs a small business from their laptop. There is one trigger and three steps, nothing gets written anywhere, and the only person it ever emails is you. As a rough estimate, it saves five to ten minutes a day of opening and scrolling the calendar, and rather more in calls you would otherwise have walked into cold. It takes about 20 minutes to build.

What you need

The flow at a glance

Four nodes run in a straight line. A node is one step in an n8n workflow, and each passes its output to the next.

  1. Every Weekday at 7am (Schedule Trigger) starts the run Monday to Friday.

  2. Get Today's Calendar Events (Google Calendar) fetches every event between midnight and midnight today.

  3. Build the Day Plan Email (Code) drops cancelled events, formats the times and writes the subject line and the email body.

  4. Email Me the Day Plan (Gmail) sends one email to your own address.

n8n canvas: Every Weekday at 7am, Get Today's Calendar Events, Build the Day Plan Email, Email Me the Day Plan

Illustration of the n8n canvas, drawn from the built and tested workflow.

Build it step by step

Create a new workflow in n8n and name it something you will recognise in six months. Ours is called Email me my Google Calendar events every weekday morning with Gmail. Then add the four nodes in order.

Step 1: Every Weekday at 7am (Schedule Trigger)

A trigger is the node that starts a workflow. Add a Schedule Trigger, rename it Every Weekday at 7am, and set:

  • Trigger Interval: Custom (Cron)

  • Expression: 0 0 7 * * 1-5

A cron expression is a compact way of writing a timetable. n8n reads its six fields as second, minute, hour, day of month, month and day of week, so this one means second 0, minute 0, hour 7, any day of the month, any month, Monday to Friday. Change the 7 to 6 if you are an early riser, or 1-5 to * if you want weekends too.

Then open the workflow's Settings and set Timezone to your own. The Schedule Trigger fires on the workflow's time zone if one is set and otherwise on the instance's, which the n8n docs say defaults to America/New York on self-hosted installs and GMT on n8n Cloud. Skip this and your 7am email arrives at someone else's 7am.

Step 2: Get Today's Calendar Events (Google Calendar)

Add a Google Calendar node, rename it Get Today's Calendar Events, and set:

  • Credential to connect with: your Google Calendar account

  • Resource: Event. Operation: Get Many

  • Calendar: By ID, primary (Google's name for your main calendar, so you do not need to look up an ID)

  • Return All: on

  • After: {{ $now.setZone('Australia/Sydney').startOf('day').toISO() }}

  • Before: {{ $now.setZone('Australia/Sydney').endOf('day').toISO() }}

  • Options: Order By set to Start Time, and Recurring Event Handling set to All Occurrences

The two date fields are expressions, which are small pieces of code inside double curly brackets that n8n works out when the node runs. Read them left to right. $now is the current moment, setZone('Australia/Sydney') moves it into a named time zone, startOf('day') and endOf('day') snap it to midnight at either end of that day, and toISO() writes the result in the date format Google expects. Replace Australia/Sydney with your own zone name, such as Europe/London or America/New_York.

Why name the zone here when you already set it in Settings? Because the test of this workflow showed the risk plainly. Without it, an n8n server running on US time decided that a 9am Sydney stand-up began at 5pm, and that "today" was yesterday. Naming the zone in the node makes the calendar window correct wherever n8n happens to run.

Order By keeps the events in time order, and All Occurrences makes a weekly meeting show up as today's instance rather than as the series it belongs to.

Step 3: Build the Day Plan Email (Code)

Google returns each event as its own item, with more fields than you will ever want in an email. A Code node, which runs a few lines of JavaScript inside the workflow, turns that pile into one subject line and one short list. Add a Code node, rename it Build the Day Plan Email, set Mode to Run Once for All Items and Language to JavaScript, and paste:

const TIME_ZONE = 'Australia/Sydney';
const events = $input.all().map(item => item.json).filter(e => e.start && e.status !== 'cancelled');
const fmt = iso => DateTime.fromISO(iso).setZone(TIME_ZONE).toFormat('h:mm a');
const rows = events.map(e => {
  const allDay = !e.start.dateTime;
  const when = allDay ? 'All day' : fmt(e.start.dateTime) + ' to ' + fmt(e.end.dateTime);
  const where = e.location ? ' (' + e.location + ')' : '';
  return '<li><strong>' + when + '</strong>: ' + (e.summary || 'Untitled event') + where + '</li>';
});
const dayName = $now.setZone(TIME_ZONE).toFormat('cccc d LLLL');
const count = events.length;
const subject = 'Your day: ' + count + (count === 1 ? ' event' : ' events') + ' on ' + dayName;
const html = '<p>Good morning. Here is your day.</p><ul>' + rows.join('') + '</ul>';
return [{ json: { subject, html, count } }];

Line by line, it does this:

  • TIME_ZONE holds your zone name in one place. Use the same value as in Step 2.

  • events collects every item from the Calendar node and keeps only those that have a start time and have not been cancelled.

  • fmt is a small helper that turns a timestamp such as 2026-11-23T09:00:00+11:00 into 9:00 AM in your time zone. DateTime comes from Luxon, the date library n8n makes available inside Code nodes.

  • rows builds one list item per event. All-day events have a start.date but no start.dateTime, so they are labelled "All day"; timed events get a start and finish; a location, if there is one, goes in brackets.

  • dayName writes today as, for example, "Monday 23 November".

  • subject and html assemble the email, and the last line hands them to the next node as a single item, with count kept for later use.

Step 4: Email Me the Day Plan (Gmail)

Add a Gmail node, rename it Email Me the Day Plan, and set:

  • Credential to connect with: your Gmail account

  • Resource: Message. Operation: Send

  • To: your own address, for example [email protected]

  • Subject: {{ $json.subject }}

  • Email Type: HTML

  • Message: {{ $json.html }}

  • Options: add Append n8n Attribution and switch it off, so the email ends with your events rather than a line about the software

$json means "the item that arrived from the previous node", so these two expressions pick up the subject and body the Code node just built.

Test it

You do not have to wait until tomorrow morning. Put two or three events in today's calendar, including one all-day event and one you then cancel, and click Execute workflow in the n8n editor. The Schedule Trigger fires at once in a manual run, and each node shows a green tick and an item count when it succeeds.

We tested this build with sample data in place of a real calendar: a 9:00 stand-up on Google Meet, an 11:30 phone call with Alex Taylor of Acme Bakery, a 2:00 supplier catch-up marked cancelled, a 3:00 to 4:30 writing block, and an all-day "Invoice day". The Code node produced this, word for word:

❝

Your day: 4 events on Friday 20 November

Good morning. Here is your day.

9:00 AM to 9:15 AM: Team stand-up (Google Meet)
11:30 AM to 12:00 PM: Call with Alex Taylor, Acme Bakery (Phone)
3:00 PM to 4:30 PM: Write the weekly newsletter
All day: Invoice day

Five events went in and four came out, with the cancelled meeting dropped and the all-day event labelled correctly, which is what success looks like. (The date in the subject is the day of the test run, because the subject is built from the current date rather than from the events.) When the output looks right, switch the workflow to active with the toggle at the top of the editor, and the schedule takes over from there.

Common problems and fixes

  • The times are hours out. This is the time zone problem from Step 2, and it is the one our own test hit first. Check the zone name in the After and Before expressions, in TIME_ZONE in the Code node, and in the workflow's Settings. All three should match.

  • The email arrives at the wrong hour. The Schedule Trigger follows the workflow time zone, then the instance time zone. Set Timezone in the workflow's Settings, as the Schedule Trigger docs describe.

  • Nothing arrives at all. A scheduled workflow only runs once it is saved and switched to active. Also, on a day with no events the Calendar node returns nothing, and n8n then skips the later steps; the second variation below changes that.

  • A weekly meeting is missing or shows the wrong date. Set Recurring Event Handling to All Occurrences, so Google returns today's instance of the series. The options are listed on the Google Calendar event operations page.

  • Google refuses the credential. Reconnect it from the Credentials page and make sure you granted Calendar and Gmail access when Google asked. The Google credentials guide covers the consent screen step by step.

Make it yours

  • Add tomorrow for evening planners. Move the trigger to 6pm (0 0 18 * * 1-5) and add .plus({ days: 1 }) after $now.setZone(...) in After, Before and dayName, and you read tomorrow's plan before you log off.

  • Get a note on clear days too. In the Calendar node's Settings, turn on Always Output Data. On an empty day the node then passes one blank item along, the Code node's existing e.start check drops it, and you receive "Your day: 0 events", which is pleasant news in its own way.

  • Read more than one calendar. Duplicate the Calendar node, point the copy at a second calendar ID, and join both into the Code node with a Merge node set to Append. Work and family commitments then arrive in one list.

Download the workflow

Copy the JSON below, then in n8n open a new workflow and paste it straight onto the canvas (or use Import from File). Credentials are not included, so you will be asked to pick your own Google Calendar and Gmail accounts in Steps 2 and 4. Change [email protected] to your address and Australia/Sydney to your time zone in the three places it appears, then set the workflow time zone in Settings.

{
  "name": "Email me my Google Calendar events every weekday morning with Gmail",
  "nodes": [
    {
      "name": "Every Weekday at 7am",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.3,
      "position": [240, 300],
      "parameters": {
        "rule": { "interval": [ { "field": "cronExpression", "expression": "0 0 7 * * 1-5" } ] }
      }
    },
    {
      "name": "Get Today's Calendar Events",
      "type": "n8n-nodes-base.googleCalendar",
      "typeVersion": 1.3,
      "position": [480, 300],
      "parameters": {
        "resource": "event",
        "operation": "getAll",
        "calendar": { "__rl": true, "mode": "id", "value": "primary" },
        "returnAll": true,
        "timeMin": "={{ $now.setZone('Australia/Sydney').startOf('day').toISO() }}",
        "timeMax": "={{ $now.setZone('Australia/Sydney').endOf('day').toISO() }}",
        "options": { "orderBy": "startTime", "recurringEventHandling": "expand" }
      }
    },
    {
      "name": "Build the Day Plan Email",
      "type": "n8n-nodes-base.code",
      "typeVersion": 2,
      "position": [720, 300],
      "parameters": {
        "mode": "runOnceForAllItems",
        "language": "javaScript",
        "jsCode": "const TIME_ZONE = 'Australia/Sydney';\nconst events = $input.all().map(item => item.json).filter(e => e.start && e.status !== 'cancelled');\nconst fmt = iso => DateTime.fromISO(iso).setZone(TIME_ZONE).toFormat('h:mm a');\nconst rows = events.map(e => {\n  const allDay = !e.start.dateTime;\n  const when = allDay ? 'All day' : fmt(e.start.dateTime) + ' to ' + fmt(e.end.dateTime);\n  const where = e.location ? ' (' + e.location + ')' : '';\n  return '<li><strong>' + when + '</strong>: ' + (e.summary || 'Untitled event') + where + '</li>';\n});\nconst dayName = $now.setZone(TIME_ZONE).toFormat('cccc d LLLL');\nconst count = events.length;\nconst subject = 'Your day: ' + count + (count === 1 ? ' event' : ' events') + ' on ' + dayName;\nconst html = '<p>Good morning. Here is your day.</p><ul>' + rows.join('') + '</ul>';\nreturn [{ json: { subject, html, count } }];\n"
      }
    },
    {
      "name": "Email Me the Day Plan",
      "type": "n8n-nodes-base.gmail",
      "typeVersion": 2.2,
      "position": [960, 300],
      "parameters": {
        "resource": "message",
        "operation": "send",
        "sendTo": "[email protected]",
        "subject": "={{ $json.subject }}",
        "emailType": "html",
        "message": "={{ $json.html }}",
        "options": { "appendAttribution": false }
      }
    }
  ],
  "connections": {
    "Every Weekday at 7am": { "main": [ [ { "node": "Get Today's Calendar Events", "type": "main", "index": 0 } ] ] },
    "Get Today's Calendar Events": { "main": [ [ { "node": "Build the Day Plan Email", "type": "main", "index": 0 } ] ] },
    "Build the Day Plan Email": { "main": [ [ { "node": "Email Me the Day Plan", "type": "main", "index": 0 } ] ] }
  },
  "settings": { "executionOrder": "v1" }
}

A calendar that emails itself to you will not make the day any shorter, but it does mean you meet the 9am call at 7am, over coffee, with time to do something about it.

Sources