ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various administrative and operational tasks related to ScaleFluidly's platform. Specifically for the Admin resource with the Get Properties operation, it enables retrieval of configuration or metadata properties from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Fetching system or user properties for administrative oversight.
  • Retrieving configuration details needed for further automation or decision-making workflows.
  • Integrating ScaleFluidly administrative data into broader business processes within n8n.

For example, an admin might use this node to get current property settings before updating configurations or to audit system parameters regularly.

Properties

Name Meaning
Environment The target environment for the API call. Options:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)
Request JSON object representing the request body sent to the API. This contains the specific parameters or filters for the "Get Properties" operation.

Output

The node outputs a JSON array where each element corresponds to the response from the ScaleFluidly API for each input item processed. The json output field contains the parsed JSON response from the API, which includes the requested properties data.

If the API returns binary data (not typical for this operation), it would be included in the binary output fields, but this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token if provided via credentials or headers.
  • No explicit external libraries beyond standard HTTP request helpers bundled with n8n are required.

Troubleshooting

  • Bearer token not found error: If multiple items are processed and the authorization header is missing on subsequent items, the node throws an error. Ensure that the first input item includes proper authorization headers or credentials.
  • Operation not found error: If the specified operation or intent does not match any known API endpoint, the node will throw an error indicating the operation is not found. Verify the operation name matches supported actions.
  • Request body issues: Invalid or malformed JSON in the "Request" property can cause API errors. Validate JSON syntax and required fields before execution.
  • Environment URL misconfiguration: Selecting an incorrect environment URL may lead to connection failures. Confirm the environment setting matches your deployment.

Links and References


This summary focuses on the Admin resource and Get Properties operation as requested, based on static analysis of the provided source code and property definitions.

Discussion