Connect Buildkite and Wachete

Both apps 23Buildkite 14Wachete 9

• Trigger
  Build finished

  Triggers when a Buildkite build finishes (passed, failed, canceled or otherwise completed).

• Trigger
  New build

  Triggers when a new build is scheduled in a Buildkite pipeline.

• Action
  Add annotation

  Creates an annotation (a Markdown or HTML note) on a Buildkite build, optionally appending to an existing annotation with the same context.

• Action
  Add build

  Creates (triggers) a new build on a Buildkite pipeline for a given commit and branch, and returns the new build.

• Action
  Add pipeline

  Creates a new pipeline in a Buildkite organization from a repository and YAML steps configuration.

• Action
  Cancel build

  Cancels a running or scheduled build in a Buildkite pipeline and returns the updated build.

• Action
  Delete pipeline

  Permanently deletes a pipeline from your Buildkite organization.

• Action
  Get build

  Returns a single build of a Buildkite pipeline by its build number, including its state, commit, jobs and pipeline details.

• Action
  Get pipeline

  Returns a Buildkite pipeline's full details, including its repository, default branch, steps and build counts.

• Action
  List agents

  Returns the connected and stopping agents in a Buildkite organization, optionally filtered by name, hostname, version or queue.

• Action
  List builds

  Returns the builds of a Buildkite pipeline, newest first, optionally filtered by branch, commit, state, creator or date range.

• Action
  List pipelines

  Returns the pipelines in a Buildkite organization, optionally filtered by pipeline name or repository URL.

• Action
  Rebuild build

  Starts a new build that re-runs an existing build of a pipeline, and returns the new build.

• Action
  Update pipeline

  Updates one or more settings of an existing Buildkite pipeline, such as its name, repository, YAML steps or branch filters.

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