Humanity Integration with Zapier

An overview of Humanity’s integration with Zapier.

Igor Pavlovic avatar
Written by Igor Pavlovic
Updated over a week ago

Introduction to Zapier

Zapier is a workflow automation platform targeted towards everyday consumers and small businesses who want to automate repetitive processes without having to invest in a massive IT infrastructure to do so.

How does Zapier Work

Zapier works by allowing users to connect “Zapier Apps” together with simple or complex workflows. It simplifies this process by using the concept of Triggers and Actions, along with other more advanced features, if necessary. Under the hood, each Zapier App is a simplified implementation of a company’s API within Zapier’s platform. The Zapier platform allows those apps to authenticate users, collect user input, run workflows on demand or on schedule, and provides error handling and logging. This is the part that makes Zapier so appealing to small companies or consumers because without it, building all those platform features to make APIs interact would take way too much time, effort, and money.

What’s a Zapier App

Zapier’s platform allows companies to make their application available as Zapier Apps. Humanity is listed among those apps now. If a 3rd party service is supported by Zapier, it will work with Humanity’s Zapier App.

What is a Zap

A Zap is Zapier’s name for an automation workflow. An automation workflow consists of one Trigger and one or many Actions. A Zap also keeps a running history of every execution and any errors. Lastly, the Zap also stores special deduplication ids from Triggers to ensure every time a Trigger is activated, the Zap does not act on a record that was already processed previously. This type of behavior only occurs with application Triggers that let Zapier know about duplicate records.

What are Triggers & Actions

Triggers and Actions can be explained in a simple sentence:

“When this happens, then do this.”

“When a new employee is added in Humanity, then add that employee to an Excel spreadsheet.”

In this example, the Trigger is when a new employee is being added to Humanity. Once this trigger event is detected, the action of adding that employee to a spreadsheet can commence.

Triggers can be behaviour in an application, like new employees being added to Humanity, or a new row being added to a spreadsheet; however, a Trigger can also be a scheduled date and time. For example, 12:00 PM Eastern Time Every Monday.

Actions are CREATE, UDPATE, or DELETE behaviours in an application. Once a Trigger is activated, any actions the user wants to perform will run within the Zap.

First-party Triggers provided by Humanity

  • Approved Leave Requests

  • New/Updated Employees

  • New/Updated Time Entries

  • Published Shifts

  • Published Shifts by Employee

First-party Actions provided by Humanity

  • Assign Leave Type to Employee

  • Assign Positions to Employee

  • Create/Update Driver Data Point

  • Create/Update Employee

  • Create/Update Leave Request

  • Create/Update Leave Type

  • Create/Update Location

  • Create/Update Position

  • Create Shift

  • Create/Update Skill

  • Create/Update Time Entry

  • Create Unavailability Slot

  • Manage Employee Conflict Settings

  • Manage Scheduler Permissions

  • Find Employee

  • Find Position

Creating Zaps

The basic setup for creating Zaps is simple. You always start with 1 Trigger and 1 Action. You can configure your Trigger or your Action in any order. Depending which apps, you want to use, you will be prompted to go through that app’s login process. For Humanity, you only need to sign in with your desired username and password.

When setting up your action, you will always have to complete at least the required fields. For example, in the Create/Update Employee action, you will only be required to fill out the Employee ID; however, if you know you’re creating a new employee, you will need to also fill out the First and Last Name, otherwise it will cause an error. The reason the First and Last name fields are not also marked as required is that when you update an employee, those fields are not required. Since this action does both (create and update), we had to use a lower requirement.


Zapier will recognise if you’re already logged into Humanity when you try to add a new account or when you try to reconnect an already connected account. If you want to add a different account, make sure to log out before attempting to add or reconnect an account in Zapier.

What are Templates

Premade popular workflows that help you save time and are even more user-friendly.

First-party Templates provided by Humanity

  • Add rows in Google Sheets for new or updated Humanity employees

  • Create or update profiles in Humanity from new Jotform submissions

  • Create or update employees in Humanity from new Google Sheets rows

  • Submit leave requests in Humanity from new or updated Google Sheets rows

  • Add new Humanity employees from new Typeform entries

  • Add or update employees in Humanity for new Google Forms submissions

  • Add Microsoft Excel rows for new Humanity employees

  • Create/update driver data points in Humanity for new Square orders

  • Update demand-driven scheduling data points in Humanity with all new merchant transactions in PayPal

  • Add new BambooHR employees to Humanity

  • Add new starters in People HR to Humanity

  • Add new or updated employees in Humanity to Xero

  • Create or update leave requests in Humanity from new time off requests in BambooHR

If you have any further queries, please don't hesitate to reach us at Happy Scheduling!

Did this answer your question?