SERGEY REVIN
← All work

Every recurring call is scheduled six months ahead — with links and no manual setup

A team running several projects has the same calls every week: the general stand-up, meetings per area, a call for each project. They are created by hand for every date, the Zoom link is dug out of chats, and when a project’s schedule moves the meetings are recalculated from scratch.

183 days ahead

meetings are built and reconciled every hour

How it runs at the client: an education company, under NDA

  • ≈2 h

    of creating meetings by hand every six months

    Estimate: 5 recurring meetings a week × 26 weeks × ~1 minute

Before

Every week, by hand

  1. Person

    Create next week’s meeting

  2. Person

    Find the Zoom link in a chat

  3. Person

    Repeat for every series and every project

  4. Person

    A project moved — recalculate its meetings

Someone forgot to create a meeting — it did not happen or half the team missed it.

After

Set up once

  1. Persononce

    Fill in one table once: meeting, link, how often

  2. System

    Every hour the system fills in meetings six months ahead

  3. System

    Project meetings are counted from the project dates

  4. System

    Change a rule — future meetings rebuild themselves

How it works

  1. 1

    One table of rules

    Each row is a recurring meeting: name, call link and how often it runs — weekly or every two weeks. Project meetings are tied to that project’s dates.

  2. 2

    Six months of meetings

    Once an hour the system compares the table with the meetings database in Notion and fills in whatever is missing for the next 183 days. Every meeting already carries its call link.

  3. 3

    Changes without rebuilding

    A changed link is updated in every future meeting. When a series ends or its day changes, the extra future meetings are removed. Meetings someone created or edited by hand are left alone.

  4. 4

    Next — the calendar and recordings

    Every future meeting already has a page in Notion. When the call happens, its recording and transcript will find that page through the link and land there.

What it is made of

  • Rules table

    Which meetings recur, where the call happens and how often. Kept by the manager or an admin.

  • Notion

    The meetings database: every meeting has its own page.

  • n8n

    The invisible helper that reconciles the table and the database every hour.

What it looks like

Mock-up with demo data

🔁Recurring meetings

MeetingRepeatsLink
Team stand-upWeeklyzoom.us/j/…
Sales reviewEvery 2 weekszoom.us/j/…
Group callFrom project dateszoom.us/j/…
Meetings built through April
Rules table — demo data

A good fit if

  • Your team has many recurring calls — general and per project.
  • Project dates move, and the meetings have to move with them.
  • Call links are dug out of chats every time.

Common questions

Will meetings reach Google Calendar?

The generator creates meetings in a Notion database. Sending Google Calendar invitations to participants can be added as the next step — participants are listed in the rules table for that.

What if one meeting needs to move manually?

Move it as usual. Meetings created or changed by hand are never overwritten.

How it works under the hood →Stack, architecture and details — for whoever implements it.

Have a similar problem? Get in touch — we start by mapping your processes.

Message me on Telegram