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 with the Import Data operation, the node sends a custom JSON request body to the ScaleFluidly API endpoint corresponding to the import data functionality.

Typical use cases include automating administrative tasks like importing bulk data into the system, managing user or configuration data, or syncing external datasets with ScaleFluidly. For example, an admin might use this node to import a batch of user records or configuration settings from another system by providing the appropriate JSON payload.

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). This determines which ScaleFluidly instance the request is sent to.
Request A JSON object representing the request body to be sent with the API call. This contains the data to import or other parameters required by the specific Admin operation.

Output

The node outputs an array of JSON objects under the json output field. Each element corresponds to the response from the ScaleFluidly API for each input item processed. The structure of the JSON depends on the API response but generally includes the result of the import operation or any relevant status information returned by the server.

The node does not explicitly handle binary data output.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers (specifically a bearer token in the authorization header).
  • The node can also use n8n credentials configured for ScaleFluidly API authentication if no explicit bearer token is found in the input.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization bearer token in its headers and no API credential is configured, the node will throw an error. Ensure that either the input data includes a valid bearer token or the node has proper API credentials set up.
  • Operation not found error: If the specified operation (intent) does not match any known API endpoint mapping, the node will throw an error indicating the operation was not found. Verify the operation name is correct and supported.
  • Invalid JSON in Request property: Since the request body is user-provided JSON, malformed JSON will cause the API call to fail. Validate the JSON format before running the node.
  • API endpoint unreachable: Selecting the wrong environment URL or network issues may cause request failures. Confirm the environment setting matches your intended ScaleFluidly instance and that it is accessible.

Links and References


This summary focuses on the Admin resource's Import Data operation based on the provided properties and source code analysis.

Discussion