ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically for the Admin resource and the Save Translation Meta Data operation, the node sends a JSON request body containing translation metadata to the ScaleFluidly backend service in the selected environment (Dev, QA, or Local). This operation is useful for managing and updating translation-related data within an administrative context.

Common scenarios include:

  • Automating the update of translation metadata in a content management or localization system.
  • Integrating translation workflows into broader automation pipelines.
  • Managing multilingual content metadata programmatically.

Example use case:

  • A localization manager wants to automatically push updated translation metadata from a spreadsheet or database into the ScaleFluidly system whenever new translations are ready, ensuring the system stays up-to-date without manual intervention.

Properties

Name Meaning
Environment The target environment URL where the API requests will be sent. Options: Dev, QA, Local.
Request The JSON-formatted request body containing the translation metadata to save. Required field.

Output

The node outputs an array of JSON objects representing the responses received from the ScaleFluidly API for each input item processed. Each response corresponds to the result of the "Save Translation Meta Data" operation and typically contains confirmation or details about the saved translation metadata.

If the API returns binary data (not indicated here), it would represent files or attachments related to the translation metadata, but this node primarily handles JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the chosen environment.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use configured credentials.
  • No explicit external libraries beyond standard n8n workflow helpers and HTTP request utilities.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no credential is configured, the node will throw an error. Ensure that either the input includes a valid authorization token or proper API credentials are set up in n8n.
  • Operation not found error: If the specified operation or intent does not match any known mapping, the node will fail. Verify that the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or malformed JSON in the request body can cause errors. Validate the environment selection and ensure the JSON request body is correctly structured.

Links and References


This summary focuses on the Admin resource's Save Translation Meta Data operation based on the provided source code and property definitions.

Discussion