ScaleFluidly

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Configure, MCP, Pricing, and Quote. Specifically, for the Admin resource with the Get Configuration Rules operation, the node fetches configuration rules from the ScaleFluidly backend.

Common scenarios where this node is beneficial include:

• Retrieving administrative configuration rules to dynamically adjust workflows or business logic.
• Automating the management and review of configuration settings in different environments (Dev, QA, Local).
• Integrating ScaleFluidly’s admin data into broader automation pipelines for monitoring or reporting.

For example, a user might use this node to pull the latest configuration rules before running a pricing update workflow, ensuring that all rules are respected.

Properties

Note: The provided input properties JSON only includes the "Environment" property explicitly, but the node also requires selecting Resource and Operation internally.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the Get Configuration Rules operation under the Admin resource, the output JSON will contain the configuration rules data retrieved from the API.

If the API returns binary data (not indicated here), it would be included in the binary output field, but this node primarily deals with JSON responses.

Example output structure (conceptual):

[
  {
    "ruleId": "string",
    "name": "string",
    "description": "string",
    "conditions": [ ... ],
    "actions": [ ... ],
    "active": true
  },
  ...
]

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
• Optionally uses an API authentication token passed via HTTP Authorization header. This token must be available in the input data headers or provided through n8n credentials configured for the ScaleFluidly API.
• No other external dependencies are indicated.

Troubleshooting

• Bearer token not found error: The node expects an authorization token in the input data's headers on the first item. If missing, it throws an error. Ensure your input data includes a valid bearer token in the authorization header or configure the API credentials properly.
• Operation not found error: If the specified operation does not exist in the internal intent-to-URL mapping, the node will throw an error. Verify that the operation name matches one of the supported operations.
• Network or API errors: Standard HTTP errors may occur if the environment URL is incorrect or the API service is unreachable. Check environment selection and network connectivity.
• Invalid request body: Some operations require a JSON request body. Providing malformed JSON or missing required fields can cause API errors.

Links and References

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

This summary focuses on the Admin resource and Get Configuration Rules operation as requested, based on static analysis of the provided source code and input properties.