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 and Save Configuration operation, it enables saving or updating configuration settings within the ScaleFluidly system.

Typical use cases include automating configuration management workflows, such as updating system settings, rules, or preferences programmatically without manual intervention. This is beneficial in environments where configurations need to be dynamically adjusted based on external triggers or data flows.

For example, a user might automate saving updated pricing rules or approval workflows after changes are made in another system, ensuring consistency across platforms.

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 to send with the save configuration operation. This contains the configuration details to be saved or updated. It must be provided and formatted according to the ScaleFluidly API requirements for this operation.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed.

  • The json output field contains the parsed JSON response from the API call reflecting the result of the save configuration operation.
  • No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token if configured; otherwise, it expects a bearer token in the input data headers.
  • No explicit external libraries beyond standard n8n helpers and request utilities are required.

Troubleshooting

  • Bearer token not found: 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 an API key credential is set up in n8n or the input data includes a valid bearer token in the headers.
  • Operation not found: 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.
  • Invalid JSON in Request: The request_info property must be valid JSON. Malformed JSON will cause the API call to fail.
  • API Endpoint Issues: Selecting the wrong environment URL or network issues may cause connection failures. Confirm the environment setting matches your deployment.

Links and References


This summary focuses on the Admin resource's Save Configuration operation, describing its inputs, outputs, and usage context based on static analysis of the provided source code and property definitions.

Discussion