ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various administrative and operational tasks related to ScaleFluidly's platform. Specifically, for the Admin - Get Permission operation, it retrieves permission details from the ScaleFluidly system. This can be useful in scenarios where you need to verify or audit user permissions programmatically within your workflows.

Practical examples include:

  • Automatically fetching permission settings before performing sensitive operations.
  • Auditing user roles and permissions as part of compliance checks.
  • Integrating permission data into dashboards or reports.

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).
Request JSON object containing the request body parameters required by the "Get Permission" API endpoint. This is a flexible JSON input where you specify the exact request payload expected by the API.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Permission" operation, the output JSON will contain the permission details retrieved from the API.

  • 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 endpoints.
  • Needs an API authentication token (bearer token) provided via HTTP headers in the input data or configured credentials.
  • The node supports selecting different environments (Dev, QA, Local) by specifying the base URL.
  • No internal credential names are exposed; users must provide valid authorization tokens.

Troubleshooting

  • Bearer token not found error: This occurs if the authorization header with a bearer token is missing in the first input item and no stored authorization header exists. Ensure that the input JSON includes a valid authorization header or configure the API credentials properly.
  • Operation not found error: If the specified operation or intent does not match any known API endpoint, the node throws an error. Verify that the operation name is correct and supported.
  • Invalid JSON in Request property: Since the request body is a JSON input, malformed JSON will cause errors. Validate the JSON structure before running the node.
  • Network or environment URL issues: Make sure the selected environment URL is reachable and correct.

Links and References


This summary focuses on the Admin resource and the Get Permission operation as requested, based on static analysis of the provided source code and properties.

Discussion