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 Admin, Quote, Configure, Pricing, and MCP. Specifically for the Admin resource and the Get Product Groups operation, it fetches product group data from the ScaleFluidly platform.

Typical use cases include:

  • Retrieving product group information for administrative or reporting purposes.
  • Integrating product group data into workflows for further processing or decision-making.
  • Automating management tasks related to product groups within a sales or inventory system.

For example, a user might want to automatically pull all product groups to update an internal catalog or synchronize product group data with another system.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). This determines which backend instance the request is sent to.
Request A JSON object representing the request body payload sent to the API. Required for many operations including "Get Product Groups". This allows passing any necessary parameters or filters as per the API specification.

Output

The node outputs an array of JSON objects under the json field. Each object corresponds to the response from the ScaleFluidly API for the requested operation.

For the Get Product Groups operation, the output JSON typically contains details about product groups such as their IDs, names, attributes, and possibly associated metadata depending on the API's response structure.

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 specified by the chosen environment.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use configured credentials named generically as an API key credential.
  • No other external dependencies are required beyond standard HTTP request capabilities.

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 includes a valid authorization header or proper API credentials are set up in n8n.
  • Operation not found: If the specified operation (intent) does not match any known operation in the internal mapping, an error will be thrown. Verify that the operation name is correct and supported.
  • Request body issues: Since the request body is a JSON object, malformed JSON or missing required fields may cause API errors. Validate the JSON structure before execution.
  • Environment URL misconfiguration: Selecting an incorrect environment URL can lead to connection failures or unexpected responses. Confirm the environment setting matches the intended backend.

Links and References

Note: For detailed API request/response formats, refer to the official ScaleFluidly API documentation corresponding to your environment.

Discussion