Coordinate time-off requests with an AI agent and Slack
Time-off requests arrive in every channel and get lost in most. An Orkeste agent reads the requests sent to your HR inbox, checks who else on the team is away, and posts a summary to the managers' Slack channel. Once a person approves, it records the absence in Airtable and adds it to the calendar.
The problem
Requests are buried in messages and email threads, overlaps are noticed too late, and HR rebuilds the absence calendar by hand.
How the workflow runs
Runs: Every hour, or every day at the hour you set.
Read the requests: The agent reads new emails in the HR inbox, in Gmail or Outlook.
Extract the details: It notes the person, the dates and the type of leave.
Check overlaps: It reads your Airtable absence table for the same team and dates.
Post to Slack: It posts a summary with any overlap to the managers' channel.
A person approves: The Airtable entry and the calendar event wait in Validations until the manager or HR approves them.
Record: Approved absences are added to Airtable and to Google Calendar.
The agent never approves or declines a request. Records and calendar events are created only once a person approves them.
Who does what
Time-off agent: Collects requests, checks overlaps and records approved absences.
Manager (human): Approves or declines every request.
What this workflow does not do
Reads requests sent by email, not Slack messages: agents post to Slack but do not read it.
Knows leave balances only if you keep them in Airtable.
Does not reply to the employee unless you add that step.