ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

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 Layouts operation, it fetches layout-related data from the ScaleFluidly platform.

Typical use cases include:

  • Retrieving administrative layout configurations to dynamically adjust UI or workflows.
  • Automating the management of layouts in different environments (Dev, QA, Local).
  • Integrating ScaleFluidly admin data into broader automation pipelines within n8n.

For example, a user might want to pull the current layout settings from the Dev environment to verify or audit them before deploying changes to production.

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)

Output

The node outputs an array of JSON objects representing the response(s) from the ScaleFluidly API for the requested operation. Each item corresponds to one API response, typically containing layout data when using the Admin resource's Get Layouts operation.

If the API returns binary data (not indicated here), it would be included accordingly, but this node primarily handles JSON responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token passed via the authorization header in input data; if not present, it attempts to use configured credentials.
  • No explicit external npm packages beyond standard n8n workflow helpers 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 that either the input includes a valid authorization token or proper API credentials are set up in n8n.
  • Operation not found: If the specified operation is not mapped in the internal intent-to-URL map, the node throws an error indicating the operation is unknown. Verify the operation name matches supported actions.
  • API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request errors. Check connectivity and credentials.
  • Invalid JSON in Request Body: If the request_info parameter contains malformed JSON, the node may fail. Validate JSON syntax before execution.

Links and References

Discussion