Straker Verify icon

Straker Verify

Interact with Straker Verify API

Actions8

Overview

This node interacts with the Straker Verify API to manage translation projects and related resources. Specifically, the Project - Get Segments operation retrieves translation segments for a given file within a project in a specified language.

Typical use cases include:

  • Fetching translated text segments from a specific file in a translation project.
  • Integrating translation segment retrieval into automated workflows for review, processing, or further translation steps.
  • Synchronizing translation data between Straker Verify and other systems.

For example, you might use this node to get all translated segments of a document file in French (language ID) within a particular project, then process or analyze those segments downstream in your workflow.

Properties

Name Meaning
Project ID The unique identifier of the project from which to retrieve segments.
File ID The unique identifier of the file within the project whose segments are to be retrieved.
Language ID The unique identifier of the language for which the segments should be fetched.

Output

The output is a JSON object representing the segments retrieved from the specified file and language within the project. The exact structure depends on the API response but typically includes details such as segment text, segment IDs, status, and possibly metadata about each segment.

No binary data output is produced by this operation.

Example output structure (conceptual):

{
  "segments": [
    {
      "segmentId": "123",
      "sourceText": "Hello world",
      "translatedText": "Bonjour le monde",
      "status": "translated"
    },
    ...
  ]
}

Dependencies

  • Requires an active connection to the Straker Verify API.
  • Needs an API key credential configured in n8n for authentication.
  • The base URL for the API is configurable via credentials; defaults to http://localhost:11001 if not set.
  • Network access to the Straker Verify service endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing Project ID, File ID, or Language ID parameters will cause the API request to fail.
    • Incorrect or expired API key will result in authorization errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • "The operation "getSegments" is not supported for resource "project"!" — indicates a misconfiguration of the operation parameter.
    • HTTP errors returned from the API (e.g., 401 Unauthorized, 404 Not Found) will be surfaced as node errors.
    • If the node receives unexpected input data types or missing required parameters, it may throw parameter validation errors.

  • Resolution tips:

    • Double-check that all required IDs are correctly provided and valid.
    • Ensure the API key credential is properly set up and has necessary permissions.
    • Verify network connectivity and API endpoint availability.

Links and References

Discussion