Connect Jitbit Helpdesk and Wachete

Both apps 29Jitbit Helpdesk 20Wachete 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.

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