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 Get Data Values operation, the node sends a custom JSON request body to the ScaleFluidly API endpoint corresponding to this operation and returns the response data.

Typical use cases include:

  • Retrieving specific administrative data values from the ScaleFluidly platform.
  • Automating data retrieval workflows that require dynamic query parameters or filters passed in JSON format.
  • Integrating ScaleFluidly admin data into broader automation pipelines within n8n.

For example, a user might want to fetch configuration or metadata values related to their ScaleFluidly account by providing a tailored JSON request body, enabling flexible querying of the admin data.

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 A JSON object representing the request body sent to the API. This allows passing any required parameters or filters for the "Get Data Values" operation.

Output

The node outputs an array of JSON objects under the json field. Each element corresponds to the response from the ScaleFluidly API for each input item processed. The structure of the output JSON depends on the API response for the "Get Data Values" operation and typically contains the requested administrative data values.

If the API returns binary data, it would be included accordingly, but based on the static code and operation context, the output is primarily JSON data representing the retrieved admin data values.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected 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 are needed.
  • The node expects proper API authentication setup either via input headers or n8n credentials configuration.

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 the node credentials are properly set.
  • Operation not found error: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify the operation parameter matches one of the supported operations.
  • API request failures: Network issues, incorrect environment URLs, or malformed JSON request bodies can cause API errors. Check the environment URL, ensure the JSON request body is correctly formatted, and verify API access permissions.
  • Empty or unexpected responses: Confirm that the request body parameters align with the API's expected schema for the "Get Data Values" operation.

Links and References


This summary focuses on the Admin resource's Get Data Values operation as requested, based solely on static analysis of the provided source code and property definitions.

Discussion