Straker Verify icon

Straker Verify

Interact with Straker Verify API

Actions8

Overview

The node interacts with the Straker Verify API to perform operations related to various resources such as projects, files, keys, languages, users, and workflows. Specifically, for the File - Get operation, it retrieves a file from the Straker Verify service by its unique file ID.

This operation is useful when you need to download or access the contents of a specific file stored in the Straker Verify system. For example, after a translation project completes, you might want to fetch the translated file for further processing or storage.

Properties

Name Meaning
File ID The unique identifier of the file to retrieve from the Straker Verify API

Output

The output contains both JSON metadata and binary data representing the downloaded file:

  • json:

    • fileId: The ID of the retrieved file.
    • fileName: The name of the file as returned by the API (extracted from HTTP headers if available).
    • contentType: The MIME type of the file content.

  • binary:

    • data: The actual binary content of the file, prepared for n8n binary data handling.

This allows downstream nodes to access the file's metadata and use the binary content directly, for example, to save it locally, upload it elsewhere, or process it further.

Dependencies

  • Requires an API key credential for authenticating requests to the Straker Verify API.
  • The base URL for the API is configurable via credentials; defaults to http://localhost:11001 if not set.
  • Uses HTTP GET requests to fetch file data.
  • Relies on n8n's helper methods for HTTP requests and binary data preparation.

Troubleshooting

  • Common issues:

    • Invalid or missing File ID parameter will cause the request to fail.
    • Authentication errors if the API key is incorrect or missing.
    • Network or connectivity issues to the Straker Verify API endpoint.
    • Non-200 HTTP responses indicate failure to retrieve the file.

  • Error messages:

    • "Request failed with status code XXX": The API responded with an error status. Check the file ID validity and API permissions.
    • Errors related to binary data decoding or preparation are unlikely here since the node handles raw response buffers, but any unexpected format could cause issues.

  • Resolutions:

    • Verify the File ID is correct and exists in the Straker Verify system.
    • Ensure the API key credential is valid and has necessary permissions.
    • Confirm network connectivity and correct API base URL configuration.
    • Enable "Continue On Fail" option in the node settings to handle errors gracefully during batch executions.

Links and References

Discussion