Connect Cursor and Wachete

Both apps 23Cursor 14Wachete 9

• Trigger
  Agent Pull Request Created

  Triggers when the selected Cursor cloud agent opens a new GitHub pull request.

• Trigger
  Agent Status Equals

  Triggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error.

• Trigger
  New Agent

  Triggered when a new Cursor cloud agent is created.

• Action
  Add Followup Instruction to Agent

  Sends a follow-up instruction to an existing Cursor cloud agent, either starting a new run or steering the run in progress. Returns the new run or how the steer was delivered.

• Action
  Cancel run

  Cancels the active run of a Cursor cloud agent. The run ends in the Cancelled state; start a new run to continue the conversation.

• Action
  Delete Agent

  Permanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent.

• Action
  Find Agent Status

  Looks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link.

• Action
  Get run

  Returns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent.

• Action
  Launch Agent

  Creates a Cursor cloud agent and immediately starts its first run on the task you describe. Returns the new agent and its run.

• Action
  List agents

  Returns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL.

• Action
  List artifacts

  Returns the files a Cursor cloud agent has produced, with each file's path, size and last modified time. Returns at most 100 artifacts.

• Action
  List models

  Returns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants.

• Action
  List repositories

  Returns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation.

• Action
  List runs

  Returns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply.

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