Skip to content

Integration · Payroll & HR

humanity.com

Connect Claude & ChatGPT to Humanity

Ask your AI who is on shift right now, to create and publish next week's shifts, or to request leave for an employee in Humanity. It can read and manage employees, shifts, leave requests and timeclocks, clock people in and out, pull timesheet reports and send internal messages. Scheduling questions get answered without paging through the calendar.

Connect Humanity free

Free plan, no credit card. Takes about a minute.

Try asking

  • “Who is working right now, and is anyone late?”

    The AI lists who is on now and who is late for work.

  • “Create a shift for the Bar position on Saturday from 18 to 02 with two staff needed.”

    It finds the position and creates the shift. It stays unpublished until you publish it.

  • “Publish next week's shifts and notify the staff.”

    It lists the shifts for the week and publishes them with a notification to the employees.

What your AI can do

Shifts and schedules

List, create, update, publish and delete shifts, see who is on now, list positions and locations, and review shift trades.

Timeclock and timesheets

Clock employees in and out, read timeclock entries and pull timesheet summary, attendance and late reports.

Employees, leave and messages

Read, create and update employees, list and create leave requests, and read or send internal messages.

  • “Request vacation for Lisa from 1 to 5 July.”

    It finds the vacation leave type and creates the leave request for Lisa for those dates.

  • “Give me a timesheet summary for last week.”

    It pulls the timesheet summary report for that date range, per employee.

  • “Clock Jonas in now.”

    It finds Jonas and clocks him in with the current time.

195 tools for Humanity

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

  • approve_availabilityDeletesApprove a availability. Destructive action; may require approval. API summary: Approve availability.
  • approve_availability_approveDeletesApprove a availability (user). Destructive action; may require approval. API summary: PUT Availability Approve.
  • approve_availability_post_availability_approveVisible to othersApprove a availability (user). Has effects visible outside this system. API summary: POST Availability Approve.
  • approve_rejectVisible to othersApprove a reject (series id). Has effects visible outside this system. API summary: Reject series.
  • approve_shiftVisible to othersApprove a shift (shift id). Has effects visible outside this system. API summary: GET Shift Approve.
  • approve_shift_approveVisible to othersApprove a shift (shift id). Has effects visible outside this system. API summary: PUT Shift Approve.
  • approve_shift_post_shifts_approveVisible to othersApprove a shift (shift id). Has effects visible outside this system. API summary: POST Shift Approve.
  • clock_inChanges dataClock an employee in by `employee_id`, optionally at a given `clock_in_time` and `location`.
  • clock_outVisible to othersClock an employee out by `employee_id`, optionally at a given `clock_out_time`, with notes or tips.
  • create_addclocktimeChanges dataCreate a new addclocktime. Required: datein or employee. API summary: POST Add clock time.
  • create_addressChanges dataCreate a new address. Required: name. Search addresses first to avoid duplicates. API summary: POST Timeclock location.
  • create_address_post_locationChanges dataCreate a new address. Required: name or type. Search addresses first to avoid duplicates. API summary: POST Location.
  • create_availabilityChanges dataCreate a new availability. Required: start date, end date or employee ids. API summary: Get availability in date period.
  • create_breakruleChanges dataCreate a new breakrule. Required: id, break or paid. API summary: POST Position break rules.
  • create_budgetChanges dataCreate a new budget. API summary: POST Budget.
  • create_createChanges dataCreate a new create. Required: start datetime, end datetime or employee id. API summary: Create single availability.
  • create_customfieldChanges dataCreate a new customfield. Required: name or type. API summary: POST Custom Fields.
  • create_data_pointChanges dataCreate a new data point. API summary: CREATE Data Points.
  • create_datapointChanges dataCreate a new datapoint. API summary: CREATE Datapoints.
  • create_datapoint_post_datapointChanges dataCreate a new datapoint. Required: value, data type id or period. API summary: POST Datapoint.
  • create_datatypeChanges dataCreate a new datatype. Required: name. API summary: POST Forecast(Datatype).
  • create_employeeChanges dataAdd an employee: in `body` pass name (or fname and lname), email, and optionally positions, group (5 = Employee, 2 = Manager), wage and address; set `send_activation` to email them an invite.
  • create_employee_expirationChanges dataCreate a new expiration for a employee.
  • create_employee_preclockinChanges dataCreate a new preclockin for a employee. API summary: POST Employees Preclockin.
  • create_employee_task_taskChanges dataCreate a new task for a employee task.
  • create_futureChanges dataCreate a new future. Required: start date. API summary: POST Future Availability.
  • create_leave_requestChanges dataRequest leave for an `employee`: `leavetype` ID, `start_date` and `end_date`, and for hourly leave set `is_hourly` with `start_time` and `end_time`.
  • create_leave_typeChanges dataCreate a new leave type. API summary: POST Leave type.
  • create_manage_positionChanges dataCreate a new manage position. API summary: POST Employee Manage Positions.
  • create_message_post_noteChanges dataCreate a new message. Required: date or note. API summary: POST Note.
  • create_metricChanges dataCreate a new metric. API summary: CREATE Metric.
  • create_moduleChanges dataCreate a new module. Required: title. API summary: POST Training Modules.
  • create_multipleChanges dataCreate a new multiple. Required: ids. API summary: Get multiple.
  • create_noticeChanges dataCreate a new notice. Required: subject or message. API summary: POST Notice.
  • create_positionChanges dataCreate a new position. Required: name. API summary: POST Position.
  • create_ratecardChanges dataCreate a new ratecard. Required: name. API summary: POST Ratecard.
  • create_savenoteChanges dataCreate a new savenote. Required: id. API summary: POST Save Note.
  • create_sectionChanges dataCreate a new section. Required: title. API summary: POST Training Section.
  • create_seriesChanges dataCreate a new series. Required: start datetime, end datetime, employee id or rrule. API summary: Create availability series.
  • create_shiftChanges dataCreate a shift: `schedule` (position ID), `start_date`, `start_time`, `end_date`, `end_time`, with optional `employee_id` list, title, notes and how many staff are `needed`. It stays unpublished until you publish it.
  • create_shift_shiftbreakChanges dataCreate a new shiftbreak for a shift. Required: breaks. API summary: POST Shift Breaks.
  • create_shift_swapChanges dataCreate a new swap for a shift. Required: swap or reason. API summary: POST Swap.
  • create_skillChanges dataCreate a new skill. Required: name. API summary: POST Skills.
  • create_terminalChanges dataCreate a new terminal. Required: name or location. API summary: POST Timeclock terminal.
  • create_timeclockChanges dataCreate a new timeclock. Required: start date, start time or employee. API summary: POST Timeclock.
  • create_tradeChanges dataCreate a new trade. Required: tradewith, reason or shift. API summary: POST Trade.
  • create_wallVisible to othersCreate a new wall. Required: post. Has effects visible outside this system. API summary: POST Wall Message.
  • delete_addressDeletesPermanently delete a address by address id. Destructive action; may require approval. API summary: DELETE Location.
  • delete_breakruleDeletesPermanently delete a breakrule by breakrule id. Destructive action; may require approval. API summary: DELETE Position break rules.
  • delete_customfieldDeletesPermanently delete a customfield by customfield id. Destructive action; may require approval. API summary: DELETE Custom Field.
  • delete_datapointDeletesPermanently delete a datapoint by datapoint id. Destructive action; may require approval. API summary: DELETE Datapoint.
  • delete_datatypeDeletesPermanently delete a datatype by datatype id. Destructive action; may require approval. API summary: DELETE Forecast(Datatype).
  • delete_employeeDeletesPermanently delete a employee by employee id. Destructive action; may require approval. API summary: DELETE Employee.
  • delete_employee_positionDeletesPermanently delete a position by position id. Destructive action; may require approval. API summary: DELETE Employee position.
  • delete_eventDeletesPermanently delete a event by timeclock. Destructive action; may require approval. API summary: DELETE Timeclock event.
  • delete_futureDeletesPermanently delete a future by future id. Destructive action; may require approval. API summary: DELETE Future Availability.
  • delete_leafDeletesPermanently delete a leaf by leaf id. Destructive action; may require approval. API summary: DELETE Leave.
  • delete_messageDeletesPermanently delete a message by message id. Destructive action; may require approval. API summary: DELETE Note.
  • delete_messagesMoves moneyPermanently delete a message. Financial or irreversible action; may require approval. API summary: DELETE Message.
  • delete_metricsMoves moneyPermanently delete a metric. Financial or irreversible action; may require approval. API summary: DELETE Metric.
  • delete_moduleDeletesPermanently delete a module by module id. Destructive action; may require approval. API summary: DELETE Training Module.
  • delete_noticeDeletesPermanently delete a notice by notice id. Destructive action; may require approval. API summary: DELETE Notice.
  • delete_positionDeletesPermanently delete a position by position id. Destructive action; may require approval. API summary: DELETE Position.
  • delete_ratecardDeletesPermanently delete a ratecard by ratecard id. Destructive action; may require approval. API summary: DELETE Ratecard.
  • delete_sectionDeletesPermanently delete a section by section id. Destructive action; may require approval. API summary: DELETE Training Section.
  • delete_seriesDeletesPermanently delete a series by series id. Destructive action; may require approval. API summary: Delete series.
  • delete_shiftDeletesPermanently delete a shift by `shift_id`. This cannot be undone.
  • delete_shift_approveDeletesApprove a shift (shift id). Destructive action; may require approval. API summary: DELETE Shift Approve.
  • delete_shift_shiftbreaksMoves moneyPermanently delete a shiftbreak by shift id. Financial or irreversible action; may require approval. API summary: DELETE Shift Breaks.
  • delete_skillDeletesPermanently delete a skill by skill id. Destructive action; may require approval. API summary: DELETE Skill.
  • delete_taskDeletesPermanently delete a task by task id. Destructive action; may require approval.
  • delete_terminalDeletesPermanently delete a terminal by terminal id. Destructive action; may require approval. API summary: DELETE Timeclock terminal.
  • delete_timeclockDeletesPermanently delete a timeclock by timeclock id. Destructive action; may require approval. API summary: DELETE Timeclock.
  • delete_timeclock_locationDeletesPermanently delete a address by address id. Destructive action; may require approval. API summary: DELETE Timeclock location.
  • delete_wallDeletesPermanently delete a wall by wall id. Destructive action; may require approval. API summary: DELETE Wall Message.
  • delete_weekliesMoves moneyPermanently delete a weekly by user. Financial or irreversible action; may require approval. API summary: DELETE Weekly Availability.
  • get_addressGet one address by address id. API summary: GET Location.
  • get_availabilityGet one availability by availability id. API summary: Get single availability slot.
  • get_availability_approveVisible to othersApprove a availability (user). Has effects visible outside this system. API summary: GET Availability Approve.
  • get_companyGet the company's Humanity account details.
  • get_company_2Get one company by company id. API summary: GET Company.
  • get_current_userGet the Humanity employee the connection signs in as, including employee ID and permissions.
  • get_customfieldGet one customfield by customfield id. API summary: GET Custom Field.
  • get_datapointGet one datapoint by datapoint id. API summary: GET Datapoint.
  • get_datapointsGet one datapoint by datatype id. API summary: GET Datapoints.
  • get_datatypeGet one datatype by datatype id. API summary: GET Forecast(Datatype) by ID.
  • get_eidGet one eid by employee id. API summary: GET Employee by Employee ID.
  • get_employeeGet one employee by `employee_id`, including contact details, positions, skills and wage.
  • get_employee_by_unique_idGet one unique id by unique id. API summary: GET Employee by Unique ID.
  • get_employee_positionGet one position for a employee by position id. API summary: GET Employee position.
  • get_employee_reportList employees. Optional filters: start date, end date, type, location, schedule or employee. API summary: GET Employee Report.
  • get_eventGet one event by timeclock. API summary: GET Timeclock event.
  • get_leave_requestGet one leave request by `leaf_id` (the leave ID).
  • get_messageGet one message by message id. API summary: GET Note.
  • get_message_get_messageGet one message by message id. API summary: GET Message.
  • get_metrics_from_companyList metrics. API summary: GET Metrics from Company.
  • get_moduleGet one module by module id. API summary: GET Training Module.
  • get_notesList messages. API summary: GET Notes.
  • get_noticeGet one notice by notice id. API summary: GET Notice.
  • get_payroll_reportList reports. Optional filters: start date, end date, type, location, schedule or employee. API summary: GET Payroll report.
  • get_positionGet one position by position id. API summary: GET Position.
  • get_ratecardGet one ratecard by ratecard id. API summary: GET Ratecard.
  • get_sectionGet one section by section id. API summary: GET Training Section.
  • get_shiftGet one shift by `shift_id`, including time, position and assigned employees.
  • get_skillGet one skill by skill id. API summary: GET Skill.
  • get_statusGet one status by details. API summary: GET Timeclock status.
  • get_terminalGet one terminal by terminal id. API summary: GET Timeclock terminal.
  • get_timeclockGet one timeclock entry by `timeclock_id`, including clock in and out times and breaks.
  • get_timesheet_reportGet a timesheet report between `start_date` and `end_date`; `type` is timesheetssummary, timesheetsattendance or timesheetslatesummary. Filter by `employee` IDs, `schedule` IDs or `approval_status`.
  • list_addressesList addresses. API summary: GET Timeclock location.
  • list_budgetsList budgets. Optional filters: start date or end date. API summary: GET Budget.
  • list_clearsList clears. Optional filters: start date, end date, schedule, shifts, restore or restoredate. API summary: GET Clear.
  • list_companiesList companies. API summary: GET Business.
  • list_customsList customs. Optional filters: start date, end date, type, fields, schedule or employee. API summary: GET Custom Report.
  • list_daily_peak_hoursList daily peak hours. Optional filters: start date, end date, location, schedule, skill or remote site. API summary: GET Daily Peak Hours Report.
  • list_data_pointsList data points. Optional filters: metric id, start or end. API summary: GET Data Points.
  • list_datatypesList datatypes. API summary: GET Forecast(Datatypes).
  • list_employee_leave_typesList leave types for a employee. Optional filters: emp id 2. API summary: GET Leave types for a specific employee.
  • list_employee_positionsList positions for a employee. API summary: GET Employee positions.
  • list_employeesList employees, optionally including `disabled` or `inactive` ones, or only those in a `location` or `schedule` (position). Use this to get an employee ID.
  • list_futuresList futures. Optional filters: approved, start date or end date. API summary: GET Future Availability.
  • list_group_permsList group perms. API summary: PUT Group permissions.
  • list_leave_requestsList leave requests, optionally by `user_id`, date range, `location` or `position`, with paging.
  • list_leave_typesList the leave types (vacation, sick and so on). A leave type ID is needed to request leave.
  • list_locationsList the company's locations and remote sites.
  • list_manage_positionsList manage positions. Optional filters: employee id. API summary: GET Employee Manage Positions.
  • list_messagesList messages in your Humanity inbox, with `limit` and `offset`.
  • list_metricsList metrics. Optional filters: metric id. API summary: GET Metric.
  • list_module_digital_signaturesList digital signatures for a module. API summary: GET Training Module Signature.
  • list_module_messagesList messages for a module. Optional filters: type. API summary: GET Training Module Comments.
  • list_modulesList modules. API summary: GET Training Modules.
  • list_noticesList notices. Optional filters: current. API summary: GET Notices.
  • list_number_of_requestsList number of requests. API summary: GET Number of requests.
  • list_on_nowList who is working right now, optionally only those `lateforwork`.
  • list_position_breakrulesList breakrules for a position. Optional filters: schedule id 2. API summary: GET Position break rules.
  • list_positionsList positions (schedules). A position ID is required when creating shifts.
  • list_preclockinsList preclockins. API summary: GET Preclockins.
  • list_progressList progress. API summary: GET Training Progress.
  • list_ratecardsList ratecards. API summary: GET Ratecards.
  • list_reportsList reports. Optional filters: start date, end date, type, schedule, employee or account. API summary: GET Group Reports.
  • list_schedulesList schedules. Optional filters: start date, end date, type, location, schedule or employee. API summary: GET Schedule Report.
  • list_sectionsList sections. API summary: GET Training Sections.
  • list_series_slotsList slots for a series. Optional filters: start datetime or end datetime. API summary: Get availability by series.
  • list_settingsList settings. API summary: GET Company Settings.
  • list_shift_shiftbreaksList shiftbreaks for a shift. Optional filters: updated at or deleted. API summary: GET Shift Breaks.
  • list_shift_tradesList shift trade requests by `mode`: manage, requested or available.
  • list_shiftsList shifts between `start_date` and `end_date`, optionally for a `schedule` (position), `location` or `employees`, and by `mode` (e.g. open, overview, employee).
  • list_skillsList skills. API summary: GET Skills.
  • list_terminalsList terminals. API summary: GET Timeclocks terminal.
  • list_timeclocksList timeclock entries, filtered by `employee`, `schedule`, `status` and date range, with paging.
  • list_wallsList walls. API summary: GET Wall Messages.
  • list_weekliesList weeklies. Optional filters: approved, day or timeframe. API summary: GET Weekly Availability.
  • list_wu_daily_reportsList wu daily reports. Optional filters: start date, end date, employee, schedule, task or location. API summary: GET Workunits Daily Report.
  • publish_shiftsVisible to othersPublish shifts by comma-separated `shifts` IDs so employees can see them; `notify` 0 sends nothing, 1 notifies employees, 2 notifies employees and managers, with an optional `message`.
  • reject_availabilityDeletesReject a availability. Destructive action; may require approval. API summary: Reject availability.
  • send_messageVisible to othersSend an internal message with `subject` and `message` to a position (`group_receivers`) and an employee (`individual_receivers`); pass `conversation` to reply. Recipients are notified.
  • submit_moduleVisible to othersComplete a module (module id). Has effects visible outside this system. API summary: PUT Training Module Complete.
  • submit_sectionVisible to othersSync a section (section id). Has effects visible outside this system. API summary: PUT Training Section Sync.
  • update_addressChanges dataUpdate an existing address identified by address id. API summary: PUT Location.
  • update_bulkVisible to othersUpdate an existing bulk identified by metric id. Has effects visible outside this system. API summary: PUT Update imported historical data.
  • update_clockinChanges dataUpdate an existing clockin identified by terminal key. API summary: POST Terminal clockin.
  • update_clockoutChanges dataUpdate an existing clockout identified by terminal key. API summary: POST Terminal clockout.
  • update_copyChanges dataUpdate an existing copy identified by datatype id. API summary: POST COPY Datapoints.
  • update_customfieldChanges dataUpdate an existing customfield identified by customfield id. API summary: PUT Custom Fields.
  • update_data_pointsVisible to othersUpdate an existing data point. Has effects visible outside this system. API summary: UPDATE Data Points.
  • update_datapointChanges dataUpdate an existing datapoint identified by datapoint id. API summary: PUT Datapoint.
  • update_datatypeChanges dataUpdate an existing datatype identified by datatype id. API summary: PUT Forecast(Datatypes) by id.
  • update_employeeChanges dataUpdate an employee by `employee_id`: in `body` change contact details, job title, wage, group, location or status. Only the fields you pass change.
  • update_employee_leave_typesVisible to othersUpdate an existing leave type identified by emp id. Has effects visible outside this system. API summary: PUT Enabling/Disabling leave types for employees.
  • update_employee_positionChanges dataUpdate an existing position identified by position id. API summary: PUT Employee position.
  • update_employee_task_tasksVisible to othersUpdate an existing task identified by employee task id. Has effects visible outside this system.
  • update_eventChanges dataUpdate an existing event identified by timeclock. API summary: PUT Timeclock event.
  • update_forceclockoutsVisible to othersUpdate an existing forceclockout. Has effects visible outside this system. API summary: PUT Force Clock Out.
  • update_futureChanges dataUpdate an existing future identified by future id. API summary: PUT Future Availability.
  • update_loginChanges dataUpdate an existing login identified by terminal key. API summary: POST Terminal login.
  • update_managesVisible to othersUpdate an existing manage. Has effects visible outside this system. API summary: PUT Manage time clock.
  • update_messageChanges dataUpdate an existing message identified by message id. API summary: PUT Note.
  • update_module_messagesVisible to othersUpdate an existing message identified by module id. Has effects visible outside this system. API summary: PUT Training Module Comments.
  • update_modulesVisible to othersUpdate an existing module. Has effects visible outside this system. API summary: PUT Training Module.
  • update_noticeChanges dataUpdate an existing notice identified by notice id. API summary: PUT Notice.
  • update_positionChanges dataUpdate an existing position identified by position id. API summary: PUT Position.
  • update_ratecardChanges dataUpdate an existing ratecard identified by ratecard id. API summary: PUT Ratecard.
  • update_sectionChanges dataUpdate an existing section identified by section id. API summary: PUT Training Section.
  • update_settingsVisible to othersUpdate an existing setting. Has effects visible outside this system. API summary: PUT Company Settings.
  • update_shiftChanges dataUpdate a shift by `shift_id`: change times, position, notes, or `add`/`remove` employees. Only the fields you pass change.
  • update_shift_shiftbreaksVisible to othersUpdate an existing shiftbreak identified by shift id. Has effects visible outside this system. API summary: PUT Shift Breaks.
  • update_shift_tasksVisible to othersUpdate an existing task identified by shift id. Has effects visible outside this system.
  • update_skillChanges dataUpdate an existing skill identified by skill id. API summary: PUT Skill.
  • update_swapChanges dataUpdate an existing swap identified by trade. API summary: PUT Swap.
  • update_taskChanges dataUpdate an existing task identified by task id. Only the fields you pass are changed.
  • update_terminalChanges dataUpdate an existing terminal identified by terminal id. API summary: PUT Timeclock terminal.
  • update_timeclockChanges dataUpdate an existing timeclock identified by timeclock id. API summary: PUT Timeclock.
  • update_tradeChanges dataUpdate an existing trade identified by trade. API summary: PUT Trade.
  • update_wallVisible to othersUpdate an existing wall identified by wall id. Has effects visible outside this system. API summary: PUT Wall Message.
  • update_weekliesVisible to othersUpdate an existing weekly identified by user. Has effects visible outside this system. API summary: PUT Weekly Availability.

Set up in three steps

  1. 1

    Pick the app

    Create a free HeyMyApps account and choose Humanity from the app list.

  2. 2

    Paste your key

    In Humanity go to Settings > API v2, give the application a name and click Save. No redirect URI is needed. Copy the App ID and App Secret, and enter them together with your Humanity username and password.

  3. 3

    Add the link to your AI

    You get a personal MCP link. Add it to Claude, ChatGPT or Cursor:

    1. Click your name, then Settings › Connectors › Add custom connector.
    2. Paste your link as the Remote MCP server URL.
    3. Switch it on from the + menu in a chat.

Questions

What can the AI do in Humanity?

It can read your company, employees, positions, locations, shifts, shift trades, who is on now, leave types, leave requests, timeclocks, timesheet reports and messages. It can create and update employees, shifts and leave requests, publish shifts, clock employees in and out and send internal messages. It can also delete a shift if you switch that tool on.

Does the AI see my Humanity login details?

No. Your Humanity login details are encrypted at rest and never shown to the AI. After you save them, they are not shown again, not even to you. The AI only sees the results of the tools it calls.

Can I control what the AI is allowed to do?

Yes. You choose which tools are switched on, so you can start read-only. Publishing shifts and sending messages notify employees, and deleting a shift is permanent. Those tools can require your approval before they run. Every tool call is logged.

Does it work with ChatGPT?

Yes. In ChatGPT go to Settings › Apps & Connectors › Advanced and turn on Developer mode, then add your HeyMyApps link. Developer mode needs a paid ChatGPT plan: Plus, Pro, Business or Enterprise. The same link also works in Claude (Settings › Connectors › Add custom connector), Cursor and other MCP clients.

What does it cost?

HeyMyApps has a free plan with no credit card required. Paid plans bill per completed task. You also need your own Humanity account.

Why does Humanity need my username and password?

Humanity's API v2 signs in with an application's App ID and App Secret together with a Humanity user's username and password. HeyMyApps uses them to get an access token, and the AI works as that user, with that user's permissions.

Let your AI work in Humanity today.

Start free. Your key stays encrypted, and you decide what the AI may do.

Connect Humanity free

HeyMyApps is not affiliated with Humanity. Product names are trademarks of their owners.