Connect Humanity and Wachete

Both apps 31Humanity 22Wachete 9

• 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.

• Trigger
  Any new notification

  Fires when there is a new change notification from any monitor in your Wachete account.

• Trigger
  New notification for monitor

  Fires when there is a new change notification from the specified Wachete monitor (taskId).

• Action
  Create monitor

  Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

• Action
  Delete monitor

  Delete a Wachete monitor by its ID.

• Action
  Get monitor

  Get information about a specific Wachete monitor by its ID.

• Action
  Get monitor data

  Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

• Action
  List folders

  List folder contents, optionally under a parent folder.

• Action
  List notifications

  List change notifications, optionally filtered by monitor (taskId) and date range.

• Action
  Update monitor

  Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.

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