Vacation Tracker Docs
Zapier Integration

Triggers

The 7 leave request events that Vacation Tracker sends to Zapier.

Vacation Tracker supports 7 trigger events. Each Zap subscribes to exactly one event type. To handle multiple events, create separate Zaps.

New Leave Request Created

Event name: LEAVE_REQUEST_CREATED

Triggers when an employee submits a new leave request.

  • Status: OPEN (pending approval)
  • Approver fields: Not included — the request has not been assigned to an approver yet
  • wasApprovedBeforeAction: Always false

New Leave Added

Event name: LEAVE_REQUEST_ADDED

Triggers when a manager (administrator or approver) adds leave for an employee. The leave is automatically approved.

  • Status: APPROVED
  • autoApproved: true
  • Approver fields: Not included — no manual approval occurred
  • wasApprovedBeforeAction: Always false

Leave Request Approved

Event name: LEAVE_REQUEST_APPROVED

Triggers when a leave request is approved, either by a manager (administrator or approver) or automatically.

  • Status: APPROVED
  • Approver fields: Included (approverId, approverName, approverEmail)
  • wasApprovedBeforeAction: false (the request was pending before this action)

Leave Request Denied

Event name: LEAVE_REQUEST_DENIED

Triggers when a leave request is denied by a manager (administrator or approver).

  • Status: DENIED
  • Approver fields: Included (approverId, approverName, approverEmail)
  • wasApprovedBeforeAction: false

Leave Updated

Event name: LEAVE_REQUEST_UPDATED

Triggers when a leave or leave request is updated. Updates can be made by the employee or a manager (administrator or approver), and may trigger re-approval depending on the leave status.

  • Status: APPROVED (if the update was to an approved request)
  • Approver fields: Included
  • wasApprovedBeforeAction: true if the request was approved before the edit, false otherwise. When an employee edits an approved request and it goes back to OPEN status, this field is still true because the original version was approved.

Leave Cancelled

Event name: LEAVE_REQUEST_CANCELLED

Triggers when a leave or leave request is cancelled by the employee, or a manager (administrator or approver).

  • Status: CANCELLED
  • Approver fields: Included (if an approver was assigned)
  • wasApprovedBeforeAction: true if the request was approved before cancellation, false if it was still pending

Leave Deleted

Event name: LEAVE_REQUEST_DELETED

Triggers when a leave or leave request is permanently deleted by a manager (administrator or approver).

  • Status: DELETED
  • Approver fields: Not included
  • wasApprovedBeforeAction: false

Event delivery

  • Webhooks are delivered as POST requests with Content-Type: application/json
  • If multiple Zaps subscribe to the same event, all webhook URLs receive the payload in parallel
  • Failed deliveries are retried up to 3 times via an SQS queue
  • If a webhook URL returns 410 Gone, the subscription is automatically cleaned up

On this page