Automation library · Scheduling

Personalized weather assistant with Google Calendar

Started by a clock, and works across Google Calendar and Telegram. It hands the judgement calls to OpenRouter. 11 steps, 1 branch: a working afternoon to understand properly.

MediumCalls a model: OpenRouter

11 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Model 4Logic 2Service 4

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2OpenRouter Chat ModelLm Chat Open RouterModel
  3. 3OpenRouter Chat Model2Lm Chat Open RouterModel
  4. 4Set TimezoneSetLogic
  5. 5AI AgentAgentModel
  6. 6AI Agent2AgentModel
  7. 7Get many eventsGoogle CalendarService
  8. 8Send a text messageTelegramService
  9. 9Send a text message1TelegramService
  10. 10IfIfLogic
  11. 11HTTP RequestHttp RequestService

How it's built

Starts on
A clock
Steps
11, with 1 branch
Size
Medium: a working afternoon
Connects to
Google Calendar, Telegram
Model
OpenRouter

Questions

What does it need to run?

An n8n account, plus your own Google Calendar and Telegram accounts, and a key for OpenRouter. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

Yes. It calls OpenRouter. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 11 steps is enough that you should read each one before running it.

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 11 steps before you point it at anything that matters.