Connect Jitbit Helpdesk to Honeybadger

Both apps 40Jitbit Helpdesk 20Honeybadger 20

• 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 check-in

  create a simple or cron check-in (name, slug, schedule_type, report_period/cron_schedule, grace_period).

• Action
  Add comment

  add a comment (body) to a fault.

• Action
  Add deployment

  report a deployment (environment, repository, revision, local_username) via the Reporting API.

• Action
  Add project

  create a project (name, resolve_errors_on_deploy, disable_public_links, language, user_url, source_url, purge_days).

• Action
  Delete check-in

  delete a check-in.

• Action
  Delete comment

  delete a comment.

• Action
  Delete deployment

  delete a deploy record.

• Action
  Delete fault

  delete a fault.

• Action
  Get check-in

  return a single check-in (simple or cron).

• Action
  Get fault

  return a single fault (error) by id.

• Action
  Get project

  return a single project's details.

• Action
  List check-ins

  list check-ins (simple or cron) for a project.

• Action
  List comments

  list comments on a fault.

• Action
  List deployments

  list deploys for a project, filterable by environment/local_username/created_after/created_before/limit.

• Action
  List faults

  return a project's faults (errors), filterable by q/created_after/occurred_after/occurred_before/order/limit.

• Action
  List projects

  list projects (optionally scoped to an account).

• Action
  Ping check-in

  report that a scheduled task ran (reporting API "ping" for check-ins).

• Action
  Report error

  report an exception/error event to Honeybadger via the Reporting API (auth via project API key).

• Action
  Update check-in

  update an existing check-in's fields.

• Action
  Update comment

  update a comment's body.

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