Automation library · Scheduling

Time spent in meetings every week with Google Calendar

Started by a clock, and works across Google Calendar and Twilio. 5 steps: small enough to read in one sitting and change without fear.

Small

5 stepsSmall: readable in one sitting
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 2Service 2

The steps in the order they run, from what starts it.

  1. 1Weekly TriggerCronStarts it
  2. 2Start and end of weekFunctionLogic
  3. 3Meetings this weekGoogle CalendarService
  4. 4Total meeting durationFunctionLogic
  5. 5Send SMS notificationTwilioService

How it's built

Starts on
A clock
Steps
5
Size
Small: readable in one sitting
Connects to
Google Calendar, Twilio
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Calendar and Twilio accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Not long. At 5 steps it can be read in one sitting and changed without fear.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 5 steps before you point it at anything that matters.