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 Group Attributes operation, the node sends a request to retrieve attributes related to a group within the ScaleFluidly system.

Typical use cases include:

  • Fetching metadata or configuration details about user groups in an administrative context.
  • Automating workflows that require up-to-date group attribute information from ScaleFluidly.
  • Integrating group attribute data into broader business processes or dashboards.

For example, a user might want to automatically pull group attributes to adjust permissions or customize UI elements based on group characteristics.

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). This determines which ScaleFluidly instance the node interacts with.
Request JSON object representing the request body sent to the API. This contains parameters specific to the "Get Group Attributes" operation, such as identifiers or filters needed by the API endpoint.

Output

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

  • The json output field contains the parsed JSON response from the API, typically including the group attributes requested.
  • If the API returns binary data (not indicated here), it would be included accordingly, but this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected environment.
  • Optionally uses an API authentication token passed via the authorization header. The node attempts to extract a bearer token from the first input item's headers or falls back to configured credentials.
  • No explicit external libraries beyond standard n8n workflow helpers 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 the input includes a valid authorization header or proper API credentials are set up in n8n.
  • 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 supported actions.
  • API request failures: Network issues, incorrect environment URLs, or malformed request bodies can cause request errors. Check the environment setting and the structure of the JSON request body.
  • Empty or invalid request_info: The request body must be a valid JSON object matching the API's expected schema for the operation; otherwise, the API may return errors or empty results.

Links and References


If you need further details on other operations or resources, please provide their names.

Discussion