BambooHR

Runs on its own 10

Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.

• List or find employees Tier 0 · Read Outside content

  List employees with optional filters, for example everyone in a department, a manager's direct reports, or a name or work email match. Always returns id, first, last and preferred name, job title and status (Active or Inactive); ask for more with fields. Values the connected user may not read come back null and are named in _restrictedFields, and employees are left out when a filter or sort uses a field the user cannot read, so an empty result does not prove nobody matches.

• Read an employee Tier 0 · Read Outside content

  Read one employee's record. Only the fields named are returned (up to 400), and fields the connected user may not see are silently left out. Use employee id 0 for the connected user.

• Add an employee Tier 2 · Reversible Outside content

  Add a new employee record, for example a new hire. List-type values (job title, department, division, location, employment status) must match an option that already exists in BambooHR. Creating the record does not invite the person to BambooHR or send onboarding packets.

• Update contact and personal details Tier 2 · Reversible Outside content

  Change an employee's name, Employee #, work or personal contact details, or home address. Job title, department, division, location and manager changes go through record_job_change so they keep an effective date. Pay, employment status and termination cannot be changed here.

• Record a job change Tier 2 · Reversible Outside content

  Add a row to the employee's job information history with an effective date: a new job title, department, division, location or manager. Give every value the row should hold, including those that stay the same, and use option values that already exist in BambooHR.

• List time off requests Tier 0 · Read Outside content

  List time off requests, newest first by default, with dates, amount and unit, category id, status (REQUESTED, APPROVED, DENIED, CANCELED) and notes. Names are not included: look employees up with list_employees (employee_ids). Requests the connected user may not see are silently left out. For who is out on a day use status eq 'approved' and startDate le 'DAY' and endDate ge 'DAY'.

• Check time off balances Tier 0 · Read Outside content

  Show an employee's balance and amount used this year for each assigned time off type, as of today or a future date to project accruals. The timeOffType ids here are the category ids that create_time_off_request takes. A 403 means the connected user may not view this employee's time off, not that the balance is zero. policyType tells accruing types from discretionary ones (such as bereavement), which show 0 but can still be requested. Does not accept employee id 0.

• See who's out Tier 0 · Read Outside content

  List approved time off overlapping a date range (up to 366 days) with each person's name and job title, sorted by start date. Company holidays are not included.

• Request time off for an employee Tier 2 · Reversible Outside content

  File a time off request on an employee's behalf. It starts as REQUESTED and goes to the employee's approvers, who are notified. Give exactly one of amount or daily_amounts.

• List job applications Tier 0 · Read Outside content

  List applications in BambooHR Hiring with the applicant's name, email and source, the job, status and rating. Filter by job, status group, a search phrase or arrival time. Needs a user with access to the hiring settings.