HR & Recruiting·Beginner· Saves 2-3 hours/week

PTO Request → Manager Approval → Calendar Block

Automate time-off requests with manager approval workflows and automatic calendar blocking.

Steps

10-15 minutes

Setup Time

2-3 hours/week

Saved / Week

Before You Start

PTO request form or HR system that captures time-off requests (Google Form, BambooHR, or Typeform)
Slack workspace with manager DM access for approval workflows
Google Calendar access for the team calendar or individual calendars
Google Sheets for PTO balance tracking and team absence calendars

Step-by-Step Workflow

Trigger

PTO request submitted by employee

How to configureSet the trigger to "New Form Submission" on your PTO request form. The form should collect: employee name, email, manager, start date, end date, PTO type (vacation, sick, personal), number of days, and reason (optional). Use a dropdown for manager selection to ensure accurate routing.

Field Mapping

employee_name

employee_email

manager_name

manager_email

start_date

end_date

pto_type

num_days

reason

Step 1

Send approval request to manager via Slack

Free plan availableRead review

Try Free

How to configureSend a Slack message to the manager with an approval request. Include the employee name, dates requested, number of days, PTO type, and reason. Use Slack's interactive message buttons for "Approve" and "Deny" — the manager can respond without leaving Slack.

Field Mapping

Slack User→{{trigger.manager_email}}

Message→"PTO Request from {{trigger.employee_name}} →

Type→{{trigger.pto_type}}

Dates→{{trigger.start_date}} — {{trigger.end_date}} ({{trigger.num_days}} days)

Reason→{{trigger.reason || 'Not provided'}}"

Buttons→"Approve"

"Deny"

Show the team's existing PTO schedule for those dates in the approval message — managers often approve without checking, then realize half the team is out the same week

Step 2

Block calendar dates upon approval

How to configureUpon approval (Slack button click), create a Google Calendar event on the team absence calendar. Set it as an all-day event spanning the PTO dates. Mark the employee as "Out of Office." Set the event visibility to "Public" so team members can see who is out.

Field Mapping

Calendar→Team Absence Calendar

Event Title→"{{trigger.employee_name}} — PTO ({{trigger.pto_type}})"

Start→{{trigger.start_date}}

End→{{trigger.end_date}}

All Day→true

Status→"Out of Office"

Also set the employee's own Google Calendar "Out of Office" automatic reply for those dates — this prevents others from booking meetings with them during their PTO

Step 3

Update PTO tracking spreadsheet

How to configureUpdate the PTO tracking Google Sheet. Find the employee's row and deduct the approved days from their remaining balance. Add an entry to the "PTO Log" tab with dates, type, and approval date. This sheet serves as the system of record for PTO balances.

Field Mapping

Sheet→"PTO Tracker"

Employee→{{trigger.employee_name}}

Days Used→{{trigger.num_days}}

PTO Type→{{trigger.pto_type}}

Dates→{{trigger.start_date}} — {{trigger.end_date}}

Approved By→{{trigger.manager_name}}

Approved On→{{current_date}}

Add a formula that highlights employees with less than 3 PTO days remaining in red — managers can proactively encourage these employees to take time off to avoid burnout or year-end scrambles

Step 4

Notify team members of upcoming absence

Free plan availableRead review

Try Free

How to configureNotify the team in the department Slack channel that the employee will be out on the specified dates. Keep it simple: who, when, and who to contact for coverage. Don't share the reason unless the employee opted in.

Field Mapping

Channel→#{{trigger.department}}

Message→" → palm_tree → {{trigger.employee_name}} will be out of office {{trigger.start_date}} — {{trigger.end_date}}.

For coverage

please reach out to {{backup_person}}."

Send Date→1 business day before {{trigger.start_date}}

Send the team notification 1 business day before the PTO starts (not when it's approved) — sending it weeks early means people will forget, and the day-before reminder is most actionable

Workflow Complete

Test with sample data before turning on for production.

Estimated Monthly Cost

ZapierFree plan available

Many tools offer free plans that cover basic automation needs. Costs scale with usage volume.

Build This Workflow

Zapier

Free plan available

Start Building Review

Make

Free plan available

Start Building Review

Import to n8n (One Click)

Ready-to-import n8n workflow

Download this workflow as a JSON file and import it directly into n8n. Open n8n → Workflows → Import from File → select the downloaded JSON. You will need to connect your credentials for each node.

Works with n8n Cloud and self-hosted. After importing, configure your API credentials for each node.Read our n8n review →

Customization Ideas

Add a PTO balance check before sending to the manager — auto-reject if the employee doesn't have enough days
Include a team coverage check that warns the manager if the request overlaps with other team members' PTO
Branch by PTO type — sick days get auto-approved with just a notification, vacation requires manager approval
Add a BambooHR step to deduct the approved days from the employee's PTO balance automatically

How to Set Up This Automation

1
Choose your automation platformSign up for Zapier. Free plans are available to get started.
2
Connect your accountsAuthenticate each tool used in the workflow. You will need active accounts for .
3
Set up the triggerSet the trigger to "New Form Submission" on your PTO request form. The form should collect: employee name, email, manager, start date, end date, PTO type (vacation, sick, personal), number of days, and reason (optional). Use a dropdown for manager selection to ensure accurate routing.
4
Add action steps and map fieldsAdd each step in order. The key is mapping data correctly between steps — make sure fields like email, name, and IDs pass through from the trigger to each action.
5
Test with sample dataRun the workflow with a test record before turning it on for production. Verify each step executes and data appears correctly in each tool.
6
Turn it on and monitorActivate the workflow and check the first 5-10 runs. Set up error notifications so you know immediately if something breaks.

Common Pitfalls to Avoid

•Missing field mappings — Double-check that every required field in each action step has data mapped from the trigger or a previous step.
•Rate limits — If you process high volume, check each tool's API rate limits. Add delays between steps if needed.
•Error handling — Add error notification steps so failed runs don't go unnoticed. Most platforms support email or Slack alerts on failure.
•Duplicate handling — Add a "search before create" step to avoid creating duplicate records in your CRM or database.

Frequently Asked Questions

How do I set up this hr & recruiting automation?

This workflow has 5 steps. Start by connecting your trigger (PTO request submitted by employee) to an automation platform like Zapier, then add each action step. Most users complete the setup in 15-30 minutes.

Which automation platform should I use for this workflow?

We recommend Zapier, Make for this workflow. Zapier is easiest for beginners, while n8n is best for developers who want full control.

How much time will this automation save?

This automation typically saves 2-3 hours/week. The exact savings depend on your current volume and how much manual work each step currently requires.

Related Templates

Employee Anniversary → Team Celebration → Gift Card

Never miss an employee anniversary with automatic team notifications and gift card delivery.

1-2 hours/weekbeginner

Job Application → ATS Entry → Recruiter Notification

Streamline your hiring pipeline by automatically logging applications and notifying recruiters.

3-5 hours/weekbeginner

New Hire → Account Creation → Welcome Email

Set up new employees with all their accounts and a warm welcome on their first day.

3-5 hours/weekintermediate

Offer Accepted → Onboarding Checklist → IT Setup Request

Kick off employee onboarding automatically when an offer is accepted with checklists and IT requests.

4-6 hours/weekintermediate

Not sure which automation platform to use?

Find Your Software

Loading...

Please wait while we load your content

Step-by-Step Workflow

Trigger

PTO request submitted by employee

Field Mapping

employee_name

employee_email

manager_name

manager_email

start_date

end_date

pto_type

num_days

reason

Step 1

Send approval request to manager via Slack

Free plan availableRead review

Try Free

Field Mapping

Slack User→{{trigger.manager_email}}

Message→"PTO Request from {{trigger.employee_name}} →

Type→{{trigger.pto_type}}

Dates→{{trigger.start_date}} — {{trigger.end_date}} ({{trigger.num_days}} days)

Reason→{{trigger.reason || 'Not provided'}}"

Buttons→"Approve"

"Deny"

Show the team's existing PTO schedule for those dates in the approval message — managers often approve without checking, then realize half the team is out the same week

Step 2

Block calendar dates upon approval

Field Mapping

Calendar→Team Absence Calendar

Event Title→"{{trigger.employee_name}} — PTO ({{trigger.pto_type}})"

Start→{{trigger.start_date}}

End→{{trigger.end_date}}

All Day→true

Status→"Out of Office"

Also set the employee's own Google Calendar "Out of Office" automatic reply for those dates — this prevents others from booking meetings with them during their PTO

Step 3

Update PTO tracking spreadsheet

Field Mapping

Sheet→"PTO Tracker"

Employee→{{trigger.employee_name}}

Days Used→{{trigger.num_days}}

PTO Type→{{trigger.pto_type}}

Dates→{{trigger.start_date}} — {{trigger.end_date}}

Approved By→{{trigger.manager_name}}

Approved On→{{current_date}}

Add a formula that highlights employees with less than 3 PTO days remaining in red — managers can proactively encourage these employees to take time off to avoid burnout or year-end scrambles

Step 4

Notify team members of upcoming absence

Free plan availableRead review

Try Free

Field Mapping

Channel→#{{trigger.department}}

Message→" → palm_tree → {{trigger.employee_name}} will be out of office {{trigger.start_date}} — {{trigger.end_date}}.

For coverage

please reach out to {{backup_person}}."

Send Date→1 business day before {{trigger.start_date}}

Send the team notification 1 business day before the PTO starts (not when it's approved) — sending it weeks early means people will forget, and the day-before reminder is most actionable

Workflow Complete

Test with sample data before turning on for production.

Import to n8n (One Click)

Ready-to-import n8n workflow

Works with n8n Cloud and self-hosted. After importing, configure your API credentials for each node.Read our n8n review →

Customization Ideas

Add a PTO balance check before sending to the manager — auto-reject if the employee doesn't have enough days

Include a team coverage check that warns the manager if the request overlaps with other team members' PTO

Branch by PTO type — sick days get auto-approved with just a notification, vacation requires manager approval

Add a BambooHR step to deduct the approved days from the employee's PTO balance automatically

How to Set Up This Automation

Choose your automation platformSign up for Zapier. Free plans are available to get started.

Connect your accountsAuthenticate each tool used in the workflow. You will need active accounts for .

Set up the triggerSet the trigger to "New Form Submission" on your PTO request form. The form should collect: employee name, email, manager, start date, end date, PTO type (vacation, sick, personal), number of days, and reason (optional). Use a dropdown for manager selection to ensure accurate routing.

Add action steps and map fieldsAdd each step in order. The key is mapping data correctly between steps — make sure fields like email, name, and IDs pass through from the trigger to each action.

Test with sample dataRun the workflow with a test record before turning it on for production. Verify each step executes and data appears correctly in each tool.

Turn it on and monitorActivate the workflow and check the first 5-10 runs. Set up error notifications so you know immediately if something breaks.

Common Pitfalls to Avoid

•Missing field mappings — Double-check that every required field in each action step has data mapped from the trigger or a previous step.

•Rate limits — If you process high volume, check each tool's API rate limits. Add delays between steps if needed.

•Error handling — Add error notification steps so failed runs don't go unnoticed. Most platforms support email or Slack alerts on failure.

•Duplicate handling — Add a "search before create" step to avoid creating duplicate records in your CRM or database.

Frequently Asked Questions

How do I set up this hr & recruiting automation?

Which automation platform should I use for this workflow?

We recommend Zapier, Make for this workflow. Zapier is easiest for beginners, while n8n is best for developers who want full control.

How much time will this automation save?

This automation typically saves 2-3 hours/week. The exact savings depend on your current volume and how much manual work each step currently requires.