Connect Openlayer to Simpleen Translation

Both apps 37Openlayer 24Simpleen Translation 13

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

• Action
  Add glossary

  Create a new glossary of word entries/ignored terms for translation. POST /glossaries.

• Action
  Add segment

  Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.

• Action
  Create Translation

  Translates content to selected target language

• Action
  Get file

  Get a specific localization file by id, including its segments and languages. GET /files/{id}.

• Action
  Get glossary

  Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.

• Action
  Get segment

  Get a specific translation segment by id. GET /segments/{id}.

• Action
  List files

  List the localization files known to the account. GET /files.

• Action
  List glossaries

  List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.

• Action
  List languages

  List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.

• Action
  List segments

  List translatable segments (source/translated entry pairs) across the user's files. GET /segments.

• Action
  Run translator

  Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.

• Action
  Update glossary

  Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.

• Action
  Update segment

  Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.