ScaleFluidly

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various administrative and operational tasks by specifying a resource and operation. Specifically for the Admin resource with the Save Translation Data operation, it enables saving or updating translation-related data within the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Automating the management of translation metadata or content in ScaleFluidly.
• Integrating translation updates into broader workflows, such as localization pipelines or content management systems.
• Programmatically maintaining translation consistency across environments (Dev, QA, Local).

For example, a user might use this node to push updated translation strings from a localization tool directly into ScaleFluidly, ensuring that all translations are up-to-date without manual intervention.

Properties

Output

The node outputs an array of JSON objects corresponding to the responses received from the ScaleFluidly API for each input item processed. Each JSON object contains the response data returned by the API after attempting to save the translation data.

If the API supports binary data output, it is not explicitly handled or indicated in this node's code; thus, the output is purely JSON-based.

Dependencies

• Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
• Optionally uses an API authentication token if provided in the input data headers under authorization.
• No explicit external libraries beyond standard n8n workflow helpers and request utilities are required.
• If authentication is needed, the node expects a bearer token either from the first input item's JSON headers or via configured credentials.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no other token is set in static workflow data, the node will throw an error. Ensure that the first input item includes a valid bearer token in json.headers.authorization or configure authentication properly.
• Operation not found error: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify that the operation name matches one of the supported operations.
• API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause API errors. Check the environment URL, ensure the request JSON is correctly structured, and verify API credentials.
• Empty or malformed request body: Since the request body is required, providing an empty or invalid JSON may result in API errors. Validate the JSON structure before execution.

Links and References

• ScaleFluidly API Documentation (QA environment)
• n8n Documentation on HTTP Request Node for understanding how API calls are made
• General REST API best practices for constructing request bodies and handling authentication tokens

This summary focuses on the Admin resource's Save Translation Data operation, describing its inputs, outputs, and usage context based on the provided source code and property definitions.