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, MCP, and Product. Specifically, for the Admin resource and the Get Rule Product Groups operation, it fetches product group data related to configuration rules within the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Retrieving product groups associated with specific configuration rules for administrative or reporting purposes.
  • Automating workflows that require up-to-date product grouping information from ScaleFluidly.
  • Integrating ScaleFluidly's admin-level data into broader automation pipelines for sales, pricing, or product management.

Example use case:

  • An automation that periodically fetches rule product groups to synchronize them with an internal database or CRM system.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local.
  • Environment selects which ScaleFluidly API endpoint to interact with:
    • Dev: Development environment URL.
    • QA: Quality assurance environment URL.
    • Local: Localhost URL for local testing.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Rule Product Groups" operation under the Admin resource, the output JSON typically contains details about product groups linked to configuration rules, such as group identifiers, names, and associated metadata.

If the API returns binary data (not indicated in this operation), the node would handle it accordingly, but for this operation, the output is purely JSON.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected environment.
  • May require an API authentication token (bearer token) passed via HTTP headers for authorized requests.
  • No explicit credential type is mandated, but the node expects an authorization header either from input data or configured credentials.
  • The node uses n8n's HTTP request helper methods to communicate with the API.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no other authorization is set in static workflow data, the node will throw an error. Ensure that the authorization token is provided either in the input data headers or configured properly.
  • 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 connectivity issues: Check the selected environment URL and network connectivity. Also verify that the API token is valid and has sufficient permissions.
  • Malformed request body: If the request_info JSON parameter is incorrect or missing required fields, the API may reject the request. Validate the JSON structure before execution.

Links and References

Discussion