CHATBOTS

File a PTO request from a Slack conversation and book it on the calendar

Turns a conversational time-off request in Slack into a structured leave entry: it checks the request against policy, books the dates on a shared team calendar.

CategoryChatbots
Enginepaperclip
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEmployee requests time off in SlackSlack
  • ActionExtract dates, duration, and leave type
  • LogicValidate against policy rules
  • ActionCreate leave event on shared calendarGoogle CalendarGoogle Calendar
  • OutputConfirm booking and balance in SlackSlack

What it does

An employee tells the bot "I want to take next Thursday and Friday off." The assistant parses the dates, confirms the request type against your leave policy, creates the time-off event on a shared Google Calendar, and replies with a confirmation plus their updated balance. It removes the friction of forms while keeping every request on the books.

When to use it

Use this when you want time-off requests captured in chat where people already work, without a separate HR portal. Ideal for teams that coordinate coverage off a shared calendar.

How it works

  1. 1An employee describes a time-off request in Slack.
  2. 2The assistant extracts the dates, duration, and leave type from the message.
  3. 3A logic step validates the request against policy rules (notice period, blackout dates).
  4. 4If valid, it creates the leave event on the shared Google Calendar.
  5. 5It posts a confirmation in Slack with the booked dates and remaining balance; invalid requests get a clear reason and next step.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect Google CalendarEvents, attendees, availability.
  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.