Connect Jitbit Helpdesk to Hibob

Both apps 29Jitbit Helpdesk 20Hibob 9

• Trigger
  New Ticket

  Triggers when a new ticket is created in Jitbit Helpdesk, optionally limited to a category, section, status, submitter, company, technician or tag.

• Action
  Add article

  Creates a new knowledge base article in a category.

• Action
  Add asset

  Creates a new asset in Jitbit Helpdesk with its model, manufacturer, type and supplier.

• Action
  Add company

  Creates a new company in Jitbit Helpdesk, or returns the existing company's id if the name is taken.

• Action
  Add tag to ticket

  Adds a tag to a ticket. The tag is created if it does not already exist.

• Action
  Add time spent

  Logs a time spent entry on a ticket under the connected user. Requires technician permissions.

• Action
  Create New Reply

  Posts a new reply (comment) to an existing helpdesk ticket.

• Action
  Create Ticket

  Creates a new helpdesk ticket in a category, with a subject, body and priority.

• Action
  Create User

  Creates a new helpdesk user. Requires administrator permissions.

• Action
  Find Ticket

  Searches tickets by text, optionally narrowed by submitter, category, status, assignee and creation date, and returns the matching tickets.

• Action
  Find User

  Finds a helpdesk user by their email address and returns their profile.

• Action
  Get Article

  Returns a knowledge base article with its full content, category, tags and attachments.

• Action
  Get ticket

  Returns a helpdesk ticket's details, including its status, category, submitter, assignee, tags, attachments and custom field values.

• Action
  List Companies

  Returns every company in your Jitbit helpdesk with its name, email domain and notes. Requires an administrator account.

• Action
  List Ticket Comments

  Returns all comments (replies) posted on a Jitbit Helpdesk ticket.

• Action
  List tickets

  Returns the helpdesk tickets the connected user can see, optionally filtered by mode, category, status, submitter, company, assignee, tag and dates.

• Action
  List Time Spent Entries

  Returns every time spent entry logged against a ticket, including who logged it, the seconds spent and when. Requires technician permissions.

• Action
  Update company

  Updates a company's name, notes and email domains in Jitbit Helpdesk.

• Action
  Update ticket

  Updates one or more properties of an existing helpdesk ticket, such as its status, priority, category, assignee, due date, tags, subject or body.

• Action
  Update user

  Updates an existing helpdesk user's profile, such as name, email, contact details, company, department, password and account status. Requires administrator permissions.

• Action
  Add employee

  Creates a new employee in Bob with their name, email, site and start date, and optionally their department and job title.

• Action
  Add time off request

  Submits a new time off request for an employee in Bob, in days, hours or a per-day schedule.

• Action
  Find employees

  Finds employees in Bob by email or employee ID, or returns all accessible employees when both are blank.

• Action
  Get employee

  Returns one employee's record from Bob, looked up by employee ID or email, including any requested custom fields.

• Action
  Get time off balance

  Returns an employee's time off balance for a policy type as of a given date, including taken days, adjustments and annual allowance.

• Action
  List company lists

  Returns all company lists in Bob (such as departments, sites and job titles) with their items.

• Action
  List employee fields

  Returns the metadata of every employee field defined in Bob, including the company's custom fields.

• Action
  List employee work history

  Returns an employee's work history: every entry in their Work table, such as job title, department, site and reporting line changes with effective dates.

• Action
  Terminate employee

  Terminates an employee in Bob, setting their status to Terminated as of the termination date you specify.

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