Connect Humanity to Customer.io

Both apps 32Humanity 22Customer.io 10

• 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
  Create Anonymous Event

  Records an event that isn't tied to a known person yet, such as a page view or an action by a visitor. Include an anonymous id to link the event to a person later.

• Action
  Create Event

  Records an event for a person in Customer.io, which can trigger campaigns or update segments.

• Action
  Delete person

  Deletes a person from your Customer.io workspace, identified by their id, email address or Customer.io id.

• Action
  Get person

  Look up a customer's attributes by customer_id.

• Action
  List segments

  List all manual and data-driven segments in the workspace.

• Action
  Merge people

  Merges a duplicate person into a primary person. The secondary person's attributes and activity move to the primary person, and the secondary person is deleted.

• Action
  Remove people from segment

  Removes people from a manual segment in Customer.io. Data-driven segments can't be changed this way.

• Action
  Send API-triggered broadcast

  Trigger an API-triggered broadcast campaign to send immediately.

• Action
  Send transactional email

  Send a one-off transactional email via a transactional message template.

• Action
  Suppress person

  Deletes a person from your Customer.io workspace and suppresses their identifiers so nobody can be added again with the same id, email or phone. Activity attributed to them is redacted.

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