Overview
This node interacts with the Straker Verify API to perform various operations related to translation projects, files, keys, languages, users, and workflows. Specifically, for the File - Get operation, it retrieves a file by its ID from the Straker Verify service.
A common use case for this node is when you want to download or access a specific file stored in the Straker Verify system, for example, to process translated content or review translation files programmatically within an n8n workflow.
Practical example:
- You have a translation project and want to fetch a particular translated file by its ID to store it locally or pass it to another system.
- Automate retrieval of translation files after a project completes, enabling further automated processing or quality checks.
Properties
| Name | Meaning |
|---|---|
| File ID | The unique identifier of the file to retrieve from Straker Verify. |
Output
The output contains both JSON metadata and binary data representing the file:
json:fileId: The ID of the retrieved file.fileName: The name of the file as returned by the API (extracted from headers if available).contentType: The MIME type of the file.
binary:data: The actual binary content of the file, prepared for further use in n8n workflows (e.g., saving to disk, sending via email).
This allows downstream nodes to access both the file's metadata and its raw content.
Dependencies
- Requires an API key credential for authenticating with the Straker Verify API.
- The node makes HTTP requests to the configured Straker Verify environment URL.
- No additional external dependencies beyond standard n8n helpers and HTTP request capabilities.
Troubleshooting
Common issues:
- Invalid or missing File ID: The node requires a valid file ID; ensure the correct ID is provided.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network or API errors: Check connectivity and that the Straker Verify API endpoint is reachable.
Error messages:
"Request failed with status code XXX": Indicates the HTTP request to get the file failed. Verify the file ID and API credentials."Item X is missing binary property ...": Not applicable here but may appear in other operations if binary data is expected but missing.- Other errors are logged with details; enabling debug logging can help diagnose issues.
Links and References
- Straker Verify API Documentation (example link, replace with actual)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- n8n Binary Data Handling: https://docs.n8n.io/nodes/advanced/binary-data/
This summary focuses on the File - Get operation of the Straker Verify node based on the provided source code and input properties.