CHATBOTS

Visitor Meeting Room Prep Reminder

Each morning it reads the day's Google Calendar room bookings that have external guests, looks up any prep notes in Airtable.

CategoryChatbots
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled weekday morning run
  • ActionRead today's room events from Google CalendarGoogle CalendarGoogle Calendar
  • LogicKeep only meetings with external guests
  • ActionLook up room prep notes in AirtableAirtableAirtable
  • OutputDM each host a Slack prep checklistSlack

What it does

Makes sure rooms are ready before external visitors arrive. Every morning it reviews the day's room calendar, isolates meetings that include outside guests, pulls any room-specific prep notes, and proactively reminds each host in Slack what to set up.

When to use it

Use this when client or candidate meetings need rooms prepared (badges, AV, catering, a clean whiteboard) and hosts forget. It shifts prep from a last-minute scramble to a predictable morning routine driven off the calendar you already maintain.

How it works

  1. 1A scheduled trigger runs early each weekday morning.
  2. 2The workflow reads today's room events from Google Calendar and keeps only those with external attendees.
  3. 3For each event it looks up the room's standing prep notes and any special instructions in Airtable.
  4. 4It assembles a per-meeting checklist (room, time, guest count, AV, catering, access).
  5. 5It sends each host a Slack DM with their meeting's checklist and a single thread for facilities to confirm completion.

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.