ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API to perform various operations across multiple resources, including Admin, Quote, Configure, Pricing, and MCP. Specifically for the Admin resource with the Get Approvals operation, it retrieves approval-related data from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Automating retrieval of approval lists or statuses within an administrative workflow.
  • Integrating approval data into larger automation pipelines for reporting or decision-making.
  • Fetching approvals dynamically based on environment (Dev, QA, Local) for testing or production use.

For example, a user might configure this node to fetch all pending approvals in the QA environment to trigger notifications or update dashboards automatically.

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). Determines which backend instance the request is sent to.

Note: The node also requires selecting the Resource as "Admin" and Operation as "Get Approvals" (or related admin operations), but these are fixed by your provided context.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the Get Approvals operation under Admin, the output JSON typically contains approval details such as approval IDs, statuses, approver information, timestamps, and related metadata.

The output structure depends on the API response but generally includes fields relevant to approval workflows.

No binary data output is indicated for this operation.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token passed via an authorization header extracted from input data headers or credentials configured in n8n.
  • No explicit internal credential names are exposed; users must provide a valid bearer token either through input data or configured credentials.
  • The node relies on standard HTTP requests with JSON payloads.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no token is stored in static workflow data, the node will throw an error. Ensure that the input data includes a valid authorization header or that credentials are properly configured.
  • Operation not found error: If the specified operation (intent) does not match any known mapping, the node throws an error indicating the operation is not found. Verify the operation name matches one of the supported admin operations.
  • API connectivity issues: Check that the selected environment URL is reachable and correct. For local environments, ensure the local server is running.
  • Invalid request body: If the request_info JSON parameter is malformed or missing required fields, the API may return errors. Validate the JSON structure before execution.

Links and References


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

Discussion