Resources · Zapier integration

Leave Dates Zapier integrationAutomate Leave Dates with Zapier.

The Leave Dates Zapier integration gives you 4 triggers, 1 action and no search. Every trigger is instant: a new leave request or a changed employee record reaches your calendar or your other tools the moment it is saved.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Leave Dates Zapier integration does for a team calendar

Leave Dates is a leave management system that companies use to plan and track employee holidays and absences. Through Zapier, four of its events (new or changed employees, new or changed leave) can start automations in your other tools, and one Leave Dates action can create an employee from data that arrives elsewhere.

Take the leave your team requests in Leave Dates. Three results come out of the integration. First, absences visible at a glance: New Leave Requested fires and an event appears in your team's calendar. Second, changes that follow: Updated Leave carries any edit to a leave over to the place where your team plans its work. Third, new people set up without retyping: when someone joins and is added to another tool, Create Employee opens their Leave Dates profile with the right company and time zone.

Now what Zapier does not do here. There is a single action: you cannot book, edit or cancel a leave from a Zap, nor update or remove an employee. There is no search step either. And leave requested before the Zap was published is never sent, so the calendar starts from the day you switch it on.

If you are still choosing a platform to sync your team's leave, see our n8n vs Zapier and Make vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Six words come back all over this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that creates, sends or moves something on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
Instant vs polling trigger
An instant trigger is reported by the app as soon as it happens. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Cost

What a Leave Dates Zap really costs

Leave Dates is not a premium app on Zapier, so it works from the free plan.

  • Premium appNo
  • Free plan100 tasks a month
  • Free plan Zap sizeTrigger + 1 action

The trigger never costs a task, and neither does waiting for the next request. Each action that succeeds counts as one task; one that fails counts nothing. The free plan gives 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. A second action or a filter turns it into a multi-step Zap, which needs a paid plan. The interval grid below concerns polling triggers only: all four Leave Dates triggers are instant.

Connect

Connect Leave Dates to Zapier in three steps

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. Check first that you have a Leave Dates account with access to the company and the employees the Zap will touch.

  2. 02

    Pick Leave Dates

    Type Leave Dates in the search box of the dialog, select it from the results, then click Add connection. A new browser tab opens on the Leave Dates side, ready for you to sign in.

  3. 03

    Sign in and grant access

    Log in to Leave Dates in that tab and allow Zapier to use the account. The connection is saved once, then reused by every Leave Dates step in every Zap you build.

First Zap

Your first Zap: put every leave request in the team calendar

GoalEach time someone requests leave in Leave Dates, add an event to your calendar, but only for the leave that meets your condition.

  1. 01

    Create the Zap

    In Zapier, start a new Zap. You build it top to bottom: the app and event that start it, then what follows, then you map the fields between the steps.

  2. 02

    Set the trigger

    Pick Leave Dates and New Leave Requested, choose your connection and the company. It is an instant trigger, so the editor shows a lightning bolt.

  3. 03

    Test it on a real request

    Run the test. Zapier brings back the three most recent items from your account: pick one and read what came back before building the rest.

  4. 04

    Add the filter

    Click the plus icon, add Filter, then fill the three boxes: the field to look at, the rule, and the value to compare with. Use a text rule on a text field.

  5. 05

    Add the calendar event

    Add your calendar app and its create event action, map the employee name and the leave dates from the trigger, then test the step and check the event.

  6. 06

    Publish

    Click Publish to switch the Zap on. The filter makes it a multi-step Zap, so it needs a paid plan; drop the filter to stay on the free one.

Triggers

The 4 Leave Dates triggers

4 events start a Zap when something happens in Leave Dates, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Employee

Instant trigger

In Zapier“Triggers when a new employee is created.”

Starts the Zap each time an employee is added in Leave Dates. Whatever the rest of your setup needs to know about a newcomer can start from that moment.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to add the new colleague to a staff list or a contact list kept in another tool.
Watch out
you pick a company in the trigger, so one Zap follows one company; a Zap that also runs Create Employee can set itself off again.
2

Updated Employee

Instant trigger

In Zapier“Triggers when an employee is updated.”

Fires whenever an employee record changes in Leave Dates. Every edit counts, so small corrections show up as well as real changes.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to keep the employee details held in another tool matched with what Leave Dates shows today.
Watch out
the company is a required choice here too, and there is no action to send edits back into Leave Dates.
3

New Leave Requested

Instant trigger

In Zapier“Triggers when a new leave is requested.”

Goes off as soon as someone requests leave. It is the earliest point at which the rest of the team can learn that a person will be away.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to drop each request into the team calendar, or to post it where the people who plan the work will see it.
Watch out
a request is not a decision yet, so label calendar entries accordingly and pick the company in the trigger.
4

Updated Leave

Instant trigger

In Zapier“Triggers when leave is updated.”

Reacts when an existing leave changes in Leave Dates. Anything that moves a leave after it was requested comes through here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to update the calendar entry or the record that New Leave Requested created, so the team never plans on old dates.
Watch out
each change is a separate run, so a leave edited several times sends several updates.
Actions

The Leave Dates action

Leave Dates gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Employee

Action

In Zapier“Creates an employee in your company.”

Adds an employee to your company in Leave Dates. First name, last name, company and time zone are required; options let you make the person an admin or an approver, and count their allowance in days.

When to use it
when new hires are first entered in another tool and should get a Leave Dates profile straight away.
Watch out
it sets off New Employee, so do not pair the two in the same Zap.
When it breaks

When a Leave Dates Zap breaks

Zapier lists no help article for Leave Dates, so the traps below are the ones every Zap shares, applied to leave tracking.

None of them raises an alarm on its own: the Zap simply does less, or more, than you planned. When a run goes wrong, start with the Zapier troubleshooting page.

  • Past leave never shows up

    A Zap only reacts to what happens after it is switched on. Leave booked before that stays out of the calendar, and moving it is a separate job.

  • The Zap that feeds itself

    New Employee as trigger and Create Employee as action in one Zap can set the Zap off again and again, and burn through your task count fast.

  • A bulk import floods the triggers

    After a migration or a mass import of employees, a sudden wave of events can be held back by Zapier's flood protection instead of running one by one.
Need help

Need help automating Leave Dates with Zapier?

A person reads every message.

FAQ

Leave Dates Zapier integration: your questions

01Is the Leave Dates Zapier integration free?
Yes, on the Zapier side: Leave Dates is not a premium app, so the free plan can use it. That plan includes 100 tasks a month and unlimited Zaps, but each Zap is capped at two steps, one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Your Leave Dates subscription is a separate matter that this page does not cover, so check it with Leave Dates.
02How many tasks does a Leave Dates Zap use?
One per successful action, nothing more. The trigger is free, however many leave requests come in. A Zap that adds a calendar event and then posts a message uses two tasks per request, because each action that works is counted on its own. A failed action is not billed. Updated Leave deserves care: every change to a leave is a new run, so a leave edited three times costs the actions three times.
03Do Leave Dates triggers work in real time?
Yes, all four of them. Every Leave Dates trigger is instant: the app tells Zapier as soon as the event happens, and the Zap starts right away. That holds on every plan, the free one included, because the polling interval only applies to triggers Zapier has to check on a timer. In the editor these Zaps carry a lightning bolt. The type is set by Leave Dates and cannot be changed from the Zapier side.
04What do you need to connect Leave Dates to Zapier?
A Leave Dates account, plus access to anything you do not own yourself and want the Zap to touch. Then it is short: open the Apps page of your Zapier account, click + Add connection, search for Leave Dates, click Add connection, sign in to Leave Dates in the new tab and grant access. The connection is stored once and reused by every Leave Dates step afterwards, in every Zap you build.
05Why does every Leave Dates step ask for a company?
Because the company is a required field on all four triggers and on Create Employee. Each Zap is tied to one company: it only hears the employees and leave of that company, and only creates employees there. If you manage several companies in Leave Dates, plan one Zap per company. And if the company list stays empty when you set up the step, check that the connected account has access to it.
06What if the Leave Dates operation you need is not available?
Then Zapier cannot do it directly with this app. The integration has four triggers, on new or updated employees and leave, and a single action, Create Employee. Nothing books, edits or cancels a leave, nothing updates or removes an employee, and there is no search step. If the operation is really absent, the job needs another route outside this integration, or the process has to start from these four events.
07Zapier, Make or n8n for Leave Dates?
It depends on your criteria, not on a single winner. If your team already works in Zapier, the four instant triggers cover the common needs of sharing leave with the rest of the company, on the free plan. If you need operations the integration does not expose, or many steps per run at a lower cost, compare what each platform offers for Leave Dates and how it counts executions. Weigh volume, budget and who maintains the flows.
Same platform

Other docs you might need on this stack.

Browse all integrations