Overview
This node interacts with the Straker Verify API to manage translation projects and related resources. Specifically, the Get Segments operation under the Project resource retrieves translation segments for a given file and language within a project.
Typical use cases include:
- Fetching translated text segments from a specific file in a translation project.
- Integrating segment-level translation data into workflows for further processing or validation.
- Automating retrieval of translation progress or content for review or reporting.
For example, after uploading files and creating a translation project, you can use this operation to get all translated segments for a particular language version of a file, enabling downstream automation such as quality checks or publishing.
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 fetched. |
| Language ID | The unique identifier of the language for which the segments should be retrieved. |
Output
The output is a JSON object containing the segments data returned by the Straker Verify API for the specified project, file, and language. The exact structure depends on the API response but typically includes an array or collection of segment objects representing translated text units.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Straker Verify API via an API key credential.
- The node expects the API base URL and authentication token to be configured in the credentials.
- Network access to the Straker Verify service endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Project ID, File ID, or Language ID parameters will cause the API request to fail.
- Authentication errors if the API key is invalid or expired.
- Network connectivity problems preventing access to the Straker Verify API.
- If the specified project, file, or language does not exist or is inaccessible, the API may return errors or empty results.
Error messages:
- Errors thrown by the node typically include HTTP status codes and messages from the API.
- "The operation 'getSegments' is not supported for resource 'project'" indicates a misconfiguration or unsupported operation.
- "Request failed with status code XXX" suggests an HTTP error; verify credentials and parameter correctness.
Resolution tips:
- Double-check that all required IDs are correctly set and correspond to existing entities in your Straker Verify account.
- Ensure the API key credential is valid and has sufficient permissions.
- Test network connectivity to the API endpoint.
- Use the node's debug logs to trace request and response details.
Links and References
- Straker Verify API Documentation (general reference for API endpoints and data structures)
- n8n documentation on HTTP Request Helper (for understanding how HTTP requests are made internally)