Connect TidyCal and Wachete

Both apps 25TidyCal 16Wachete 9

• Trigger
  New Team

  Triggers when a new team you have access to appears in your TidyCal account.

• Action
  Add contact

  Creates a new contact in your TidyCal account with a name, email and optional timezone.

• Action
  Add guest to booking

  Adds a guest to an existing upcoming booking. The guest gets their own linked booking at the same time and location and receives a confirmation email.

• Action
  Cancel booking

  Cancels a TidyCal booking, optionally with a reason and without notifying the booker and host. Returns the cancelled booking.

• Action
  Delete booking type

  Deletes a booking type from your TidyCal account. Team-managed copies of a booking type cannot be deleted.

• Action
  Get booking

  Returns a single TidyCal booking by its ID, including its contact, booking-question answers, payment, add-ons, refund status and hosts.

• Action
  Get booking type

  Returns a single booking type, including its title, duration, price, booking URL and availability settings.

• Action
  Get contact

  Returns a single TidyCal contact by its id, including name, email, phone number, timezone and timestamps.

• Action
  List available timeslots

  Returns the open times a client can book for one of your booking types between two dates, with how many bookings each slot can still take.

• Action
  List bookings

  Returns the bookings on your TidyCal account, optionally limited to a date range, to cancelled bookings only, or including team bookings.

• Action
  List booking types

  Returns every booking type (event type) on the connected TidyCal account, including its title, duration, price and booking URL.

• Action
  List contacts

  Returns the contacts in your TidyCal account, optionally only those whose name or email starts with given text.

• Action
  List teams

  Returns the TidyCal teams the connected account has access to, with each team's id, name and created/updated times.

• Action
  Reschedule booking

  Moves an existing TidyCal booking to a new start time, keeping the booking type's duration. Returns the updated booking.

• Action
  Update booking type

  Updates an existing booking type in TidyCal. Only the details you fill in are changed; everything else keeps its current value.

• Action
  Update contact

  Updates an existing TidyCal contact's name, email, phone number or timezone. Only the fields you fill in are changed.

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