Connect Openlayer to Wachete

Both apps 33Openlayer 24Wachete 9

• Trigger
  New Project

  Triggers when a new project is created in your Openlayer workspace.

• Trigger
  New Test Result

  Triggers when a new test result is available for a data source. Useful for alerting on passing or failing model tests.

• Action
  Create Data Source

  Creates a new data source in a project for streaming production data to Openlayer.

• Action
  Create Project

  Creates a new AI or ML project in your Openlayer workspace.

• Action
  Create Test

  Creates a data quality test in a project. Checks for duplicate rows, null values, or row counts.

• Action
  Delete Inference Pipeline

  Delete an inference pipeline by its ID. DELETE /inference-pipelines/{id}

• Action
  Delete Project

  Delete a project by its ID. DELETE /projects/{id}

• Action
  Delete Test

  Delete a test by its ID. DELETE /tests/{testId}

• Action
  Evaluate Test

  Evaluates a test for a specific time range. Use after publishing records to get immediate results.

• Action
  Find Data Source

  Finds a data source (inference pipeline) by name in a project.

• Action
  Find Project

  Finds a project by name in your Openlayer workspace.

• Action
  Find Test Result

  Finds test results for a data source, including whether each test passed or failed. Filter by outcome or test type to branch an automation on the result.

• Action
  Get Inference Pipeline

  Retrieve the details around a specific inference pipeline. GET /inference-pipelines/{id}

• Action
  Get Project

  Retrieves one project by its id. Openlayer has no single-project endpoint, so this reads the workspace's first 100 projects and returns the one matching the id.

• Action
  Get Test

  Retrieve a test by ID. GET /tests/{testId}

• Action
  Get Test Result

  Retrieves one test result by its id. Openlayer has no single-result endpoint, so this reads the data source's 100 most recent results and returns the matching one.

• Action
  List Inference Pipelines

  List the authenticated user's inference pipelines under a project. GET /projects/{id}/inference-pipelines

• Action
  List Projects

  Lists the projects in your Openlayer workspace, optionally narrowed to one kind of project. Returns up to 100 projects.

• Action
  List Test Results

  List all results for a test/goal under an inference pipeline. GET /inference-pipelines/{id}/results or GET /tests/{id}/results

• Action
  List Tests

  Lists the tests in a project, optionally narrowed by kind, archived state or monitoring mode. Returns up to 100 tests.

• Action
  Publish Record

  Publishes an LLM inference record to a data source for monitoring. Streams the model input, output, and metadata to Openlayer.

• Action
  Update Inference Pipeline

  Update an inference pipeline. PUT /inference-pipelines/{id}

• Action
  Update Project

  Update a project. PUT /projects/{id}

• Action
  Update Test

  Update a test (partial updates allowed). PUT /tests/{testId}

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