ScaleFluidly

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 Flows operation, it retrieves flow-related data from the ScaleFluidly platform.

Common scenarios where this node is beneficial include:

• Automating administrative tasks related to flows within ScaleFluidly.
• Fetching flow configurations or statuses for monitoring or reporting.
• Integrating flow data into broader workflows for decision-making or triggering other actions.

For example, a user might use this node to fetch all active flows in a development environment to audit or visualize them in a dashboard.

Properties

• Environment selects which ScaleFluidly API endpoint to interact with:
  • Dev: Development environment URL.
  • QA: Quality Assurance environment URL.
  • Local: Localhost instance URL.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. Each item corresponds to a flow or related administrative data retrieved.

• The output is structured as JSON under the json field.
• No binary data output is indicated by the source code.

Example output structure (conceptual):

[
  {
    "flowId": "string",
    "name": "string",
    "status": "string",
    "createdAt": "string",
    "updatedAt": "string",
    ...
  },
  ...
]

Dependencies

• Requires access to the ScaleFluidly API endpoints specified by the selected environment.
• Optionally uses an API authentication token passed via HTTP headers (authorization header).
• If no explicit authorization header is found in input data, the node attempts to use configured credentials for authentication.
• No internal credential names are exposed; users must provide a valid bearer token or configure API authentication accordingly.

Troubleshooting

• Bearer token not found: If the first input item does not contain an authorization header and no stored authorization exists, the node throws an error. Ensure that either the input includes a valid bearer token in the headers or the node is configured with proper API credentials.
• Operation not found: If the specified operation (intent) does not map to a known URL, the node will throw an error indicating the operation is invalid. Verify the operation name matches one of the supported admin operations.
• Request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request errors. Check environment selection and authentication details.
• Malformed request body: For operations requiring a JSON request body, ensure the provided JSON is valid and matches expected API schema.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (if available)
• n8n documentation on HTTP Request Node for understanding how API calls are made internally.

This summary focuses on the Admin resource's Get Flows operation and its usage within the ScaleFluidly node based on static analysis of the provided source code and properties.