Overview
The node interacts with the Straker Verify API to manage translation projects and related resources. Specifically, the Project Confirm operation polls the status of a given project until it reaches a state where token payment is pending, then attempts to confirm the project by submitting a confirmation request.
This operation is useful in workflows where you want to automate the confirmation step of a translation project after its creation and initial processing, ensuring that the project is ready for the next phase without manual intervention.
Practical example:
After creating a translation project via the API, you can use this node operation to wait for the project to reach the "PENDING_TOKEN_PAYMENT" status, verify that sufficient tokens are available, and then confirm the project automatically. This helps streamline project management in translation workflows.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project to confirm. |
| Max Retries | Number of times the node will poll the project status before giving up (minimum 1). |
| Wait Between Retries (Seconds) | Number of seconds to wait between each status check while polling. |
Output
The output JSON contains the response from the project confirmation API call. It includes a message field which holds the confirmation result returned by the Straker Verify API.
Example output structure:
{
"message": {
// Confirmation response details from the API
}
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Straker Verify API.
- The node expects the API base URL (
environment) and API key to be configured in the credentials. - Uses HTTP POST and GET requests to interact with the Straker Verify API endpoints.
Troubleshooting
Common issues:
- Project status never reaches "PENDING_TOKEN_PAYMENT": If the project does not enter the expected status within the maximum retries, the node throws an error indicating the timeout.
- Insufficient token balance: If the user's token balance is less than the required token cost for the project, the node throws an error specifying the required and available tokens.
- Project already completed or failed: If the project status is "COMPLETED" or "FAILED", the node throws an error indicating no confirmation is needed or that the project failed.
Error messages and resolutions:
"Status never reached PENDING_TOKEN_PAYMENT after X retries."
Increase the max retries or wait time, or verify the project lifecycle externally."Insufficient token balance. Required: X, Available: Y"
Ensure the user account has enough tokens before confirming the project."Project status is FAILED."
Check the project details and resolve any issues causing failure before retrying."Project already COMPLETED, no confirmation needed."
No action needed; the project is already confirmed.
Links and References
- Straker Verify API Documentation (example placeholder, replace with actual if known)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- n8n Custom Node Development Guide: https://docs.n8n.io/integrations/creating-nodes/
If you need further details on other operations or resources, feel free to ask!