ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as quotes, configuration, pricing, admin, and MCP (a custom module). Specifically for the Configure resource and the Search Objects operation, the node sends a search request to the ScaleFluidly API to retrieve objects based on criteria defined in the request body.

Typical use cases include:

  • Searching configuration objects within ScaleFluidly to dynamically fetch data for automation workflows.
  • Querying specific configuration settings or metadata that influence business logic or UI layouts.
  • Integrating ScaleFluidly configuration data into broader automation pipelines for sales, pricing, or product management.

Example: A user wants to search for configuration rules or product groups matching certain filters to update or analyze them downstream in an n8n workflow.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local
Request JSON object representing the request body sent to the API for searching objects. This contains the search parameters and filters relevant to the "search_objects" operation.

Output

The node outputs an array of JSON objects under the json output field. Each element corresponds to a response from the ScaleFluidly API for the search query executed. The structure depends on the API's response format for searched objects but generally includes details about the matched configuration objects.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to authenticate using configured credentials in n8n.
  • No additional external dependencies beyond standard HTTP requests.

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 the input data includes a valid bearer token in headers or proper API credentials are set up in n8n.
  • Operation not found: If the specified operation (intent) does not map to a known API endpoint, the node throws an error indicating the operation is invalid. Verify the operation name matches supported actions.
  • API request failures: Network issues, incorrect environment URLs, or malformed request bodies can cause request errors. Check the environment selection and validate the JSON request body syntax.
  • Empty or unexpected responses: Confirm that the search criteria in the request body are correct and that the API returns data for those filters.

Links and References


This summary focuses on the Configure resource's Search Objects operation as requested, describing its inputs, outputs, and usage context based on static analysis of the provided source code and property definitions.

Discussion