HR & RECRUITING
PTO Request Pre-Approval Conflict Check
When an employee submits a leave request via a form webhook, checks it against the team's existing Outlook leave and posts an approve/deny recommendation to the manager…
How it runs
The automated pipeline, trigger to output.
- TriggerLeave request submitted via form webhookHTTP webhook
- ActionQuery approved Outlook leave for requested windowOutlook
- LogicOverlap below coverage minimum?
- ActionGenerate approve/hold recommendationOpenAI
- OutputSend decision card to manager in SlackSlack
What it does
Intercepts a leave request the moment it is submitted, compares the requested dates against everyone else's approved Outlook leave on the same team, and gives the manager a one-tap decision: a clear recommendation to approve or hold, backed by exactly who else would be out on those days.
When to use it
Use this when leave is approved by a human but you want the conflict math done for them. It moves the overlap check to the request stage, so managers approve with full context instead of discovering a double-booking after the fact.
How it works
- 1A leave-request form posts to the webhook trigger with employee, dates, and team.
- 2The flow queries the team's approved Outlook calendar for the requested window.
- 3A branch evaluates overlap depth against the team's coverage minimum.
- 4An agent writes a recommendation — approve, or hold with reason and the conflicting names.
- 5The recommendation is sent to the manager as an interactive Slack message with Approve / Hold buttons.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OutlookMail, calendar, contacts.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More HR & Recruiting workflows
Route interview feedback by score the moment it is submitted
Receives each interviewer's scorecard via webhook, normalizes the rating, and routes strong-yes feedback to fast-track and any flagged concern to the recruiter.
Loom intake to recruiter handoff email
Transcribes a hiring manager's Loom intake, summarizes the role, and emails a recruiter handoff brief via Outlook with clarifying questions when details are missing.
New-hire equipment order email to IT and vendor
On a scheduled lead-time before each start date, drafts and sends an equipment order email (laptop, monitor.
Compile interview scorecards into a hire-decision packet
When every interviewer has submitted their scorecard in Notion, automatically aggregates the scores, builds a one-page decision packet in Google Drive.
Assemble and send the debrief packet after the final interview
Triggered when a candidate's final interview ends on the calendar, it waits a short window for scorecards, compiles the aggregated packet to Google Drive.
New-Hire Credential Intake to Renewal Calendar Holds
When a new credential is added to the tracker, it validates the record, files the document.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.