Actions8
Overview
This node integrates with the Straker Verify API to create translation projects by uploading files and specifying project details. It is particularly useful for automating the creation of translation projects where multiple files need to be sent for processing in specified target languages, optionally using a predefined workflow and requiring confirmation.
Typical use cases include:
- Automatically creating translation projects from binary file data stored in previous nodes.
- Managing multilingual content by specifying target language UUIDs.
- Controlling project workflows and confirmation requirements programmatically.
For example, you can feed this node an array of files (e.g., documents or localization files) in binary form, specify the project title and target languages, and have it create a new translation project on Straker Verify with those files attached.
Properties
| Name | Meaning |
|---|---|
| Title | The title of the project to be created. |
| Languages | UUID(s) of the target language(s) for the project (e.g., "917FF728-0725-A033-1278-33025F49CA40"). |
| Workflow ID | Optional UUID of the workflow to apply to the project. |
| Confirmation Required | Boolean flag indicating whether confirmation is required for the project (true or false). |
| Binary Property | The name of the property within the input item's binary data that holds the array of file objects. For example, "binary" if files are located at item.binary.binary. |
Output
The node outputs JSON data representing the response from the Straker Verify API after creating the project. This typically includes information about the newly created project such as its ID, status, and other metadata returned by the API.
If the operation succeeds, the output JSON will contain the project details as returned by the API. If no response body is returned, the node outputs { success: true }.
The node expects the input files to be provided as an array of binary file objects under the specified binary property. Each file object must include:
data: Base64-encoded file content.fileName: The name of the file.mimeType: The MIME type of the file.
No binary data is output by this node; it only returns JSON metadata about the created project.
Dependencies
- Requires an API key credential for authenticating requests to the Straker Verify API.
- Uses HTTP POST requests with multipart/form-data encoding to upload files and project details.
- The base URL for the API is configurable via credentials; defaults to
http://localhost:11001if not set. - Relies on the
form-datanpm package internally to construct multipart requests.
Troubleshooting
- Missing binary data: If the input item does not contain a top-level binary object or the specified binary property is missing or empty, the node will throw an error. Ensure that the input items have properly structured binary data arrays.
- Invalid binary file objects: Files in the binary array must have valid
data,fileName, andmimeTypeproperties. Invalid entries are skipped with warnings. - API errors: If the API request fails (e.g., due to invalid API key, network issues, or server errors), the node throws an error with the HTTP status code and message. Check your API key and network connectivity.
- Incorrect property names: Make sure the "Binary Property" matches exactly the property name in the input binary data holding the file array.
- Empty file array: An empty array in the binary property will cause an error; ensure files are correctly passed.
Links and References
- Straker Verify API Documentation (example link, replace with actual if available)
- n8n documentation on working with binary data
- n8n documentation on HTTP Request node (for understanding underlying HTTP calls)