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, and MCP. Specifically, for the Admin resource and the Get User Permissions operation, it fetches user permission data from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Retrieving user permissions to manage access control within an organization.
  • Auditing user roles and permissions for compliance or security reviews.
  • Integrating permission data into workflows that automate user management or reporting.

For example, a workflow could use this node to automatically fetch and log all user permissions daily, or to verify if a user has the required permissions before proceeding with sensitive operations.

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 User Permissions), 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. For the "Get User Permissions" operation, the output JSON typically contains details about user permissions, such as permission names, scopes, roles, or related metadata.

The exact structure depends on the API response but generally includes fields describing each user's permissions.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the ScaleFluidly API endpoint specified by the selected Environment.
  • Optionally uses an API authentication token (Bearer token) passed via the input data's headers.authorization field or through configured credentials.
  • No explicit internal credential type names are exposed; users must provide valid authorization tokens for API access.
  • The node relies on n8n's HTTP request helper methods to communicate with the ScaleFluidly API.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a Bearer token, and no prior authorization header is stored in static workflow data, the node will throw an error. Ensure that the input data includes a valid authorization token in the headers or configure credentials 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 that the operation parameter matches one of the supported operations.
  • API connectivity issues: Network errors or incorrect environment URLs can cause request failures. Confirm the environment URL is correct and accessible.
  • Invalid request body: Some operations require a JSON request body. Providing malformed JSON or missing required fields may result in API errors.

Links and References


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

Discussion