On mention
Answer policy questions
Staff ask in Slack and get an answer from your written policies.
Leave request agentTime off, sorted in a day.
When someone asks for time off, the agent checks the team calendar for clashes and the balance sheet for days left. It sends a short summary to the manager, who decides.
Your first signup includes $50 in free credits.
New request
Handle time-off requests
- Reads
- Request form, calendar, balances
- Grows
- A summary for the manager
- Lands in
- Slack, Google Sheets
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
When someone submits the leave form, check the team calendar for clashes and the Balances sheet for days left. Send the manager a short summary in Slack, and log the request in the Leave sheet.
TulipFarm
I made an agent called Leave checker and a workflow that starts on each form response. It reads the calendar and the Balances sheet. Posting to the manager and logging the request asks you first. Activate it?
ActivateEdit first
One request, checked.
Every run is saved as an agent task you can open, check and rerun.
- Form response
A new leave request in Google Forms
Run startedStarted - Reads
Team events on those dates in Google Calendar
1 clash, 2 people off - Reads
Days left in the Balances sheet
9 days left, 5 asked - Writes
A summary for the manager
1 summary - Asks first
Send to the manager in Slack and log the request
Approved - Posts
Message in Slack, row in Google Sheets
DeliveredCompleted
The log in your Leave sheet.
The manager gets the same facts, with the decision left to them.
Leave requests| Employee | Dates | Days | Cover and balance |
|---|---|---|---|
| Employee 1 | Nov 18 to 22 | 5 | 1 clash. Balance covers it. |
| Employee 2 | Dec 2 | 1 | No clash. Balance covers it. |
| Employee 3 | Dec 23 to 31 | 5 | 3 people off. Balance short by 1. |
What gets planted.
Three parts you own and can change at any time.
- Agent
Leave checker
Its instructions, and the calendar and sheets it may read.
- Skill
Leave rules
Notice, cover limits and blackout dates.
- Workflow
On each request
Starts when a form response arrives.
Uses
- Google FormsGoogle Forms
- Google Calendar
- Google Sheets
- Slack
Add if you use it
Gmail
Google Docs
It reads quietly. It asks before it acts.
Reads without asking
- The leave request
- The team calendar
- The Balances sheet
Asks you first
- Posting to the manager in Slack
- Adding rows to Google Sheets
- Adding or changing calendar events
It uses your own connections, so it never sees more than you can.
Grow it your way.
Add the event
After the manager approves, add the time off to the team calendar.
Tell the employee
Draft a short reply email with the decision.
Cover plan
Ask it to name who is free to cover the work.
Questions, answered.
Does it approve leave?
No. The manager approves or declines. The agent only gathers the facts.
Where do balances come from?
From a sheet you keep. If your balances live in an HR system with an MCP server, add it as a Custom MCP connection.
Who sees the request?
The manager it is sent to, and anyone with access to the Leave sheet. Limit the sheet to HR and managers.
Start date
A first week that runs itself
Accounts, intros, docs and check-ins, on the right day.
TablesOn request
Find a time that works
Checks your calendar and drafts an email with times you can offer.
Fewer chats about who is off.
Public beta, open to everyone. Your first signup includes $50 in free credits.