Overview
The node facilitates creating a new project in the Straker Verify system by uploading files for translation verification. It bundles multiple input binary files, associates them with selected languages and a workflow, and sends this data to the Straker Verify API to initiate a project. The node also supports specifying a callback URL to receive notifications once the project is completed.
This node is beneficial when automating translation quality assurance workflows, especially when you want to programmatically submit files for verification across multiple languages and track their progress via callbacks.
Practical example:
You have a set of documents that need translation verification in several languages. Using this node, you can upload all relevant files at once, specify target languages and a workflow, and provide a callback URL to get notified when the verification completes, enabling seamless integration into your automation pipeline.
Properties
| Name | Meaning |
|---|---|
| Project Title | The title or name of the project being created. |
| Language Names or IDs | Select one or more target languages for the project from a list or specify language IDs using expressions. |
| Workflow Name or ID | Choose the workflow to apply to the project from a list or specify its ID using expressions. |
| Binary Property | The property name within each input item's binary data that contains the files to upload (e.g., "data" if files are in item.binary.data). |
| Callback URL | The URL where the system will send a callback notification once the project is completed. |
Output
The node outputs a JSON array containing the response from the initial project creation API call. The output structure includes:
creation: An object holding the full API response data related to the newly created project.
No binary data is output by this operation.
Example output JSON snippet:
[
{
"json": {
"creation": {
/* API response details about the created project */
}
}
}
]
Dependencies
- Requires an API key credential for authenticating with the Straker Verify API.
- Needs network access to the configured Straker Verify environment endpoint.
- Uses multipart/form-data HTTP POST requests to upload files.
- Input items must contain binary data under the specified binary property.
Troubleshooting
Missing binary property error: If any input item lacks the specified binary property, the node throws an error indicating which item is missing it. Ensure all input items include the correct binary data property.
No languages selected: The node requires at least one language to be selected; otherwise, it throws an error.
API request failures: Errors during the HTTP request to create the project will be surfaced. Check API credentials, endpoint URLs, and network connectivity.
Incorrect callback URL: If the callback URL is invalid or unreachable, the project completion notification may fail. Verify the URL correctness.
File size or format issues: Large files or unsupported formats might cause upload failures. Confirm file sizes and types comply with Straker Verify API requirements.
Links and References
- Straker Verify API Documentation (hypothetical link as no direct link provided)
- n8n Expressions Documentation - For specifying dynamic values in properties like languages and workflow IDs.