Connect Rocketlane to Wachete

Both apps 26Rocketlane 17Wachete 9

• Trigger
  Account Created

  Triggers when a new account is created.

• Trigger
  Account Updated

  Triggers when a account is updated.

• Trigger
  Project Created

  Triggers when a new project is created.

• Trigger
  Project Updated

  Triggers when a project is updated.

• Trigger
  Task Created

  Triggers when a new task is created.

• Trigger
  Task Updated

  Triggers when a new task is updated.

• Action
  Archive Project

  Archives a project.

• Action
  Create Account

  Creates an account.

• Action
  Create Project

  Creates a project.

• Action
  Create Task

  Creates a Task.

• Action
  Delete Project

  Deletes a project.

• Action
  Post Task Message

  Creates a new Task message.

• Action
  Search Project

  Search Project By Id.

• Action
  Search Task

  Search Task By Id.

• Action
  Update Project

  Updates a project.

• Action
  Update Task

  Updates a Task.

• Action
  User

  Search User By Email Id.

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