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 Add or Update Configuration Rule operation, the node sends a JSON request body to the ScaleFluidly API endpoint corresponding to this operation to add or update configuration rules within the system.

Common scenarios where this node is beneficial include automating administrative tasks related to configuration management in ScaleFluidly, such as programmatically updating business rules or settings without manual intervention. For example, an organization could use this node to dynamically adjust pricing rules or approval workflows based on external triggers or data changes.

Properties

Name Meaning
Environment The target environment for the API call. Options are: Dev (development), QA (quality assurance), Local (local server). This determines the base URL of the API endpoint.
Request The JSON-formatted request body containing the details of the configuration rule to add or update. This must be provided according to the API's expected schema for configuration rules.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the respective request made to add or update a configuration rule.

If the API returns binary data (not indicated explicitly here), it would be included accordingly, but primarily the output is JSON data reflecting the result of the operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided via credentials or authorization headers.
  • The node expects the user to provide a valid JSON request body matching the API specification for adding or updating configuration rules.
  • No explicit environment variables are required beyond what is configured in n8n for API authentication.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no credential-based authentication is set up, the node will throw an error. Ensure that either the authorization header is present in the input data or proper API credentials are configured in n8n.
  • Operation not found error: If the specified operation or intent does not match any known API endpoint mapping, the node will throw an error indicating the operation was not found. Verify that the operation name is correct and supported.
  • Invalid JSON in Request property: Since the request body must be valid JSON, malformed JSON will cause the API call to fail. Validate the JSON structure before execution.
  • API connectivity issues: Network problems or incorrect environment URLs can cause request failures. Confirm the environment selection matches the intended API server and that network access is available.

Links and References

Discussion