PERSONAL PRODUCTIVITY

Team Meeting-Load Rollup to Airtable

Each week, aggregates calendar meeting hours and focus-block availability across a roster of team members, writes per-person and team-level metrics to Airtable for trend tracking.

CategoryPersonal Productivity
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly rollup schedule fires
  • ActionPull each member's calendar eventsGoogle CalendarGoogle Calendar
  • LogicCompute per-person load metrics
  • ActionUpsert weekly rows to AirtableAirtableAirtable
  • OutputPost team load summary to SlackSlack

What it does

Produces a team-wide view of meeting load. For every person on a configured roster, it tallies weekly meeting hours, count of days with no focus block, and largest average free window, then logs one row per person per week to Airtable so trends are visible over time. It also surfaces the most overloaded people in a Slack summary so managers can rebalance.

When to use it

Use it when you manage a team and need data, not anecdotes, about where meeting load is concentrated. The Airtable history makes it easy to show whether a calendar-hygiene push actually moved the numbers month over month.

How it works

  1. 1A weekly schedule trigger starts the rollup.
  2. 2The flow iterates the roster and pulls each member's events from Google Calendar.
  3. 3A logic step computes per-person meeting hours, focus-starved days, and free-window averages.
  4. 4It upserts one row per person for the week into an Airtable table.
  5. 5A team summary highlighting the most meeting-heavy people is posted to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.