Connect Humanity to Nango

Both apps 33Humanity 22Nango 11

• Trigger
  Approved Leave Requests

  Triggers when a leave request is approved or an approved leave request changes.

• Trigger
  New/Updated Employees

  Triggers when an employee is added or an existing employee is updated.

• Trigger
  New/Updated Time Entries

  Triggers when a time entry is created or updated in the last day.

• Trigger
  Published Shifts

  Triggers when a shift in the next 30 days is published or a published shift changes.

• Trigger
  Published Shifts by Employee

  Triggers when a published shift in the next 30 days that has employees assigned is created or changes.

• Action
  Assign Leave Type to Employee

  Enables a leave type for an employee, optionally setting how many days they are entitled to.

• Action
  Assign Positions to Employee

  Assigns positions to an employee, and optionally removes positions from them.

• Action
  Assign Skills to Employee

  Assigns a skill to an employee in Humanity, optionally with an expiration date and reminder.

• Action
  Create Shift

  Creates a new shift in a Humanity schedule (position), optionally assigning an employee to it.

• Action
  Create/Update Employee

  Creates a new employee, or updates an existing employee when their ID is given.

• Action
  Create/Update Location

  Creates a new location, or updates an existing location when its ID is given.

• Action
  Create/Update Position

  Creates a new position, or updates an existing position when its ID is given.

• Action
  Create/Update Skill

  Creates a new skill, or renames an existing skill when its ID is given.

• Action
  Create/Update Time Entry

  Creates a new time entry (timeclock record), or updates an existing one when its ID is given.

• Action
  Delete shift

  Deletes a shift from the Humanity schedule, optionally including the rest of its repeating series.

• Action
  Find Employee

  Finds a employee by its Humanity ID and returns its details.

• Action
  Find leave requests

  Returns leave requests in a date range, optionally filtered by status and employee.

• Action
  Find locations

  Finds locations and remote sites in Humanity, optionally by name, ID, type or last update time.

• Action
  Find Position

  Finds a position by its Humanity ID and returns its details.

• Action
  Find shifts

  Returns the shifts scheduled within a date range, optionally narrowed to specific employees, positions, locations or skills.

• Action
  Find timeclocks

  Returns timeclock records, optionally filtered by date range, employee, position, status or last update.

• Action
  Update shift

  Updates an existing shift's times, position, title, notes, location or staffing needs.

• Action
  Add connection

  Imports (upserts) a connection into a Nango integration using credentials you already hold. If a connection with the same connection ID and integration already exists, its credentials are updated.

• Action
  Add connect session

  Creates a short-lived (30 minute) Nango connect session and returns its token and connect link, which your end user can use to connect an integration through Nango Connect UI.

• Action
  Add integration

  Creates a new integration in the Nango environment for a given provider.

• Action
  Delete connection

  Deletes a Nango connection for the given integration.

• Action
  Delete integration

  Deletes an integration from the Nango environment.

• Action
  Get connection

  Returns a specific Nango connection, including its current credentials (Nango refreshes an expired access token before returning it).

• Action
  Get connect session

  Get a Connect session by token.

• Action
  Get integration

  Returns a specific Nango integration by its unique key.

• Action
  List integrations

  Returns every integration configured in the connected Nango environment.

• Action
  Update connection

  Edits a Nango connection's tags or its webhook URL override.

• Action
  Update integration

  Edits an existing Nango integration: rename its ID, change its display name, toggle webhook forwarding, or replace its credentials or provider-specific configuration. Only the fields you fill in are changed.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.