CHATBOTS

Post a daily team leave digest from the shared calendar to Slack

Every morning, reads the upcoming time-off entries from the team's Google Calendar and posts a clear who's-out digest to Slack so managers can plan coverage without chasing anyone.

CategoryChatbots
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionRead upcoming leave from shared calendarGoogle CalendarGoogle Calendar
  • LogicFilter approved leave and group by date
  • ActionFormat who's-out digest
  • OutputPost digest to Slack channelSlack

What it does

On a fixed schedule each workday, this workflow scans the next two weeks of the shared team calendar for approved leave, formats a tidy summary of who is out and when, and posts it to a team Slack channel. It keeps everyone aware of coverage gaps before they become a problem.

When to use it

Use this when leave is booked on a shared calendar but nobody actually looks at it, and managers keep getting surprised by absences. A deterministic, scheduled job — no chat interaction needed.

How it works

  1. 1A daily schedule trigger fires each weekday morning.
  2. 2The workflow reads time-off events from the shared Google Calendar for the next 14 days.
  3. 3A logic step filters to approved leave and groups entries by date and person.
  4. 4It formats a readable digest of upcoming absences.
  5. 5The digest is posted to the designated Slack channel; if no one is out, it posts a short all-clear.

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.