Connect RepairDesk and Wachete

Both apps 25RepairDesk 16Wachete 9

• Trigger
  Employee Commission

  Triggers when an employee's payroll report row (pay period, commissions and net pay) appears or changes.

• Trigger
  Inventory Updated

  Triggers when an inventory item is added or changed (stock, price, name or other details).

• Trigger
  New Customer

  Triggers when a new customer is added in RepairDesk.

• Trigger
  New Inventory Item

  Triggers when a new inventory item is added in RepairDesk.

• Trigger
  New Invoice

  Triggers when a new invoice is created in RepairDesk.

• Trigger
  New Lead

  Triggers when a new lead (appointment) is created in RepairDesk.

• Trigger
  New Payment Added

  Triggers when a payment is recorded against an invoice in your RepairDesk store today.

• Trigger
  New Ticket

  Triggers when a new repair ticket is created in RepairDesk.

• Trigger
  Ticket Status Change

  Triggers when the repair status of a device on a ticket changes (checks the 1000 most recently created tickets).

• Action
  Add Payment

  Records a payment against an existing RepairDesk invoice.

• Action
  Create a New Invoice

  Creates a new invoice for a customer in RepairDesk with the given line items.

• Action
  Create a New Ticket

  Creates a repair ticket in RepairDesk for a customer, with one or more device line items.

• Action
  Create Customer

  Creates a new customer in RepairDesk with their contact details and address.

• Action
  Create Lead

  Creates a lead (appointment) in RepairDesk with the customer's contact details and the devices they want repaired.

• Action
  Find Customer

  Finds customers whose name, phone, email, postcode, city, organization or driving licence matches a keyword, optionally narrowed by referral source.

• Action
  Update Ticket

  Updates a repair ticket's summary (customer, discount, totals) and its line items (devices), including their parts, conditions and images.

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