OTHER

Send the front desk a daily digest of expected visitors

Each morning it scans the day's calendar for meetings with external guests and posts a single Slack summary to reception listing every expected visitor, their host, and arrival…

CategoryOther
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionFetch today's calendar eventsGoogle CalendarGoogle Calendar
  • LogicFilter and sort external-guest events
  • OutputPost arrivals digest to receptionSlack

What it does

This workflow runs once every morning, gathers all of the day's calendar events that include external attendees, and posts a consolidated arrivals digest to your reception Slack channel. The front desk starts the day knowing exactly who is expected and when.

When to use it

Use this when your reception team wants a single at-a-glance list of the day's visitors instead of hunting through individual calendars. It works well for offices without a dedicated visitor-management system that still want predictability at the desk.

How it works

  1. 1A morning schedule triggers the run on business days.
  2. 2The flow pulls today's events from the office calendar.
  3. 3It filters to events that contain at least one external-domain attendee and sorts them by start time.
  4. 4It formats each visitor into a digest line with guest name, host, time, and room.
  5. 5The complete digest is posted as a single message to the reception Slack channel; if there are no visitors today, it posts a short all-clear note.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.