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 - Get Tables operation, it fetches administrative data tables from the selected ScaleFluidly environment.

Common scenarios include:

• Retrieving user or system tables for administrative oversight.
• Accessing configuration or metadata tables relevant to ScaleFluidly's platform.
• Automating administrative data retrieval in workflows for reporting or further processing.

For example, a user might select the "Admin" resource and "Get Tables" operation to pull a list of all users or roles from the ScaleFluidly system in their QA environment, then use that data downstream in an automation.

Properties

The Environment property lets you choose which ScaleFluidly instance to query:

• Dev: Development environment URL.
• QA: Quality Assurance environment URL.
• Local: Localhost instance URL (for local testing).

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested admin tables. Each item corresponds to one table or dataset retrieved by the operation.

• The output is accessible via the json field.
• 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 endpoint corresponding to the chosen environment.
• Optionally uses an API authentication token passed in the HTTP Authorization header. This token must be provided in the input data headers on the first item or via credentials configured in n8n.
• No other external dependencies are required.

Troubleshooting

• Bearer token not found: The node expects an authorization token either in the first input item's JSON headers under authorization or via configured credentials. Ensure the token is correctly supplied; otherwise, the node will throw an error.
• Operation not found: If the specified operation does not exist in the internal intent-to-URL mapping, the node will error out. Verify the operation name matches supported actions.
• Connection issues: Confirm the selected environment URL is reachable and the API service is running.
• Invalid request body: For operations requiring a request body, ensure the JSON is well-formed and contains all required fields.

Links and References

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

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