Connect Hub Planner and Wachete

Both apps 22Hub Planner 13Wachete 9

• Trigger
  New Booking

  Triggers when a new booking is created.

• Trigger
  New or Updated Time Entry

  Triggers when a new time entry is created or updated.

• Action
  Create Booking

  Create / Schedule a booking for resource and project or event.

• Action
  Create Event

  Creates a new event.

• Action
  Create Milestone

  Create a Milestone for a Project.

• Action
  Create Project

  Creates a new project.

• Action
  Create Time Entry

  Create timeEntry for resource and project.

• Action
  Find Booking

  Find Booking by id.

• Action
  Find Event

  Find event by name or id.

• Action
  Find Project

  Find project by name, code or id.

• Action
  Find Resource

  Find resource by it's ID, name or email address.

• Action
  Find TimeEntry

  Find timeentry by id.

• Action
  Update Booking

  Updates an existing booking.

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