Overview
This node interacts with the Straker Verify API to manage translation projects and related resources. Specifically, the Project - Get operation retrieves detailed information about a single project by its ID.
Common scenarios for this node include:
- Fetching the current status and details of a translation project.
- Monitoring project progress or retrieving metadata for reporting.
- Integrating project data into automated workflows for translation management.
For example, you might use this node to get the status of a project before triggering further actions like confirming the project or downloading translated files.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project to retrieve. This is required to specify which project’s details to fetch. |
Output
The output is a JSON object containing the full details of the requested project as returned by the Straker Verify API. The structure typically includes fields such as project status, token cost, and other metadata relevant to the project.
Example output structure (simplified):
{
"id": "string",
"status": "string",
"token_cost": number,
"title": "string",
"languages": [ ... ],
"created_at": "string",
"updated_at": "string",
...
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Straker Verify API.
- The node uses HTTP requests to communicate with the Straker Verify environment URL configured in the credentials.
- No additional external dependencies are needed beyond the API access.
Troubleshooting
Error: "The operation 'get' is not supported for resource 'project'"
This indicates a misconfiguration of the operation or resource parameters. Ensure that the Resource is set to "Project" and Operation to "Get".Error: Network or authentication failures
Check that the API key credential is valid and has proper permissions. Also verify the environment URL is correct and reachable.Error: Missing or invalid Project ID
The Project ID property is required. Make sure it is provided and correctly formatted.Unexpected empty or malformed response
This could indicate issues on the API side or incorrect API version. Review API documentation or contact support if persistent.
Links and References
- Straker Verify API Documentation (example link, replace with actual)
- n8n HTTP Request Node documentation for understanding request handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/