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 and the Get Flow By ID operation, the node fetches detailed flow information by its identifier from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Retrieving administrative workflow or process flows by their unique IDs for monitoring or auditing.
• Integrating ScaleFluidly's administrative data into automation workflows within n8n.
• Using flow details to trigger conditional logic or further processing in a larger automation pipeline.

For example, a user might want to get the details of a specific approval flow or configuration flow by its ID to display or analyze it in another system.

Properties

Details on Properties:

• Environment: Selects which ScaleFluidly environment to connect to. This affects the base URL used for API requests.
• Request: A JSON input that contains the necessary parameters for the API call. For "Get Flow By ID", this would typically include the flow ID or related identifiers needed by the API endpoint.

Output

The node outputs an array of JSON objects representing the response(s) from the ScaleFluidly API for the requested operation. Each item in the output corresponds to one API response.

• The json field contains the parsed JSON response from the ScaleFluidly API.
• If the API returns binary data (not typical for this operation), it would be included accordingly, but for "Get Flow By ID" the output is expected to be JSON describing the flow details.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• Optionally uses an API authentication token if provided in the input headers; otherwise, it attempts to use configured credentials named generically as an API key credential.
• No explicit external libraries beyond standard HTTP request helpers provided by n8n 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 you provide a valid API token either via input headers or through the node’s credential configuration.
• Operation not found: If the specified operation (intent) does not match any known operation in the internal mapping, the node throws an error indicating the operation is invalid. Verify the operation name is correct.
• Invalid JSON in Request: The request_info property must be valid JSON. Malformed JSON will cause errors.
• Environment URL issues: Selecting an incorrect environment or having network connectivity issues to the chosen environment URL can cause request failures.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (Dev environment)

This summary focuses on the Admin resource's Get Flow By ID operation, describing how to configure and use the node effectively within n8n workflows.