ScaleFluidlyInstall

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 with the Get Data Types operation, the node fetches metadata or data type information from the ScaleFluidly platform. This can be useful in scenarios where you need to dynamically understand or validate the types of data handled by the system, for example, when building integrations that depend on specific data schemas or when automating administrative tasks related to data management.

Practical examples include:

• Retrieving available data types to configure forms or UI elements dynamically.
• Validating incoming data against supported types before processing.
• Automating administrative workflows that require knowledge of data structures.

Properties

Note: The "Environment" property determines which ScaleFluidly API endpoint the node will communicate with.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response received from the ScaleFluidly API for the requested operation. For the Admin - Get Data Types operation, this typically includes structured data describing the available data types or metadata definitions.

No binary data output is indicated in the source code.

Dependencies

• Requires access to the ScaleFluidly API endpoints specified by the selected environment.
• Optionally uses an API authentication token passed via HTTP Authorization header. The token must be provided in the input data's JSON under headers.authorization for the first item or via a parameter for some operations.
• No explicit external npm packages beyond n8n core workflow helpers are required.
• The node supports using an API key credential configured in n8n (referred generically as "an API key credential") if no authorization header is found in the input data.

Troubleshooting

• Bearer token not found error: If the input data does not contain an authorization token in the headers of the first item and no credential is configured, the node will throw an error. Ensure that either the input data includes a valid bearer token or that the node is configured with appropriate API credentials.
• Operation not found error: If the specified operation (intent) does not exist in the internal mapping, the node throws an error indicating the operation was not found. Verify that the operation name matches one of the supported operations for the Admin resource.
• Network or API errors: Since the node makes HTTP requests, network issues or incorrect environment URLs may cause failures. Confirm the environment URL is correct and accessible.
• Invalid request body: Some operations expect a JSON request body. Providing malformed JSON or missing required fields may result in API errors.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (Dev environment)

Note: Replace URLs above with the environment selected in the node properties.