Straker Verify icon

Straker Verify

Interact with Straker Verify API

Actions8

Overview

The node interacts with the Straker Verify API to manage translation projects and related resources. Specifically, the Project - Confirm operation sends a confirmation request for a given project ID to the Straker Verify service. This is useful in workflows where you want to programmatically confirm that a translation project is complete or approved.

Common scenarios include:

  • Automating the confirmation step after translation files have been reviewed.
  • Integrating project confirmation into larger automation pipelines involving translation management.
  • Triggering downstream processes only after a project has been confirmed.

Example: After uploading and processing translation files, use this node operation to confirm the project so that it can move to the next stage in your workflow.

Properties

Name Meaning
Project ID The unique identifier of the project to confirm. This is required to specify which project should be confirmed by the API.

Output

The output JSON contains the response from the Straker Verify API after sending the confirmation request for the specified project. Typically, this will include success status or any relevant metadata returned by the API about the confirmation action.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "success": true,
  "message": "Project confirmed successfully"
}

Dependencies

  • Requires an active connection to the Straker Verify API.
  • Needs an API key credential configured in n8n for authentication.
  • The base URL for the API defaults to http://localhost:11001 but can be overridden via credentials.

Troubleshooting

  • Missing or invalid Project ID: Ensure the "Project ID" property is set correctly; otherwise, the API call will fail.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • API endpoint unreachable: Check network connectivity and that the base URL is correct.
  • Unexpected API errors: The node throws detailed errors if the API responds with failure status codes. Review error messages for HTTP status codes and messages to diagnose issues.

If the node is set to continue on failure, errors will be returned as JSON objects with an error field instead of stopping execution.

Links and References

Discussion