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 with the Get Attribute Groups operation, it fetches attribute group data from the ScaleFluidly backend.

Common scenarios include:

  • Retrieving metadata or configuration groups related to administrative settings.
  • Automating workflows that require fetching grouped attributes for further processing or decision-making.
  • Integrating ScaleFluidly's admin data into other systems or dashboards.

For example, a user might use this node to get all attribute groups in an environment (Dev, QA, or Local) to dynamically build UI filters or validate configurations.

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)

Note: The node also requires selecting the Resource (Admin) and Operation (Get Attribute Groups), but these are fixed by your input context.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. Each item corresponds to an attribute group retrieved from the Admin resource.

  • The json output field contains the parsed JSON response from the API.
  • If the API returns binary data (not typical for this operation), it would be included accordingly, but this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an authorization bearer token extracted from the first input item's JSON headers if present; otherwise, it attempts to authenticate using configured credentials.
  • No explicit external libraries beyond n8n core helpers and request utilities are required.

Troubleshooting

  • Bearer token not found error: 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 you provide a valid bearer token either via input headers or configure API authentication properly.
  • Operation not found error: If the specified operation or intent is incorrect or missing in the internal mapping, the node will fail. Verify the operation name matches one of the supported actions.
  • Network or environment URL issues: Make sure the selected environment URL is reachable and correct. Local environments must be accessible from the n8n instance.
  • Invalid request body: For operations requiring a request body, ensure the JSON is well-formed and matches expected API schema.

Links and References


If you need details on other operations or resources, feel free to ask!

Discussion