ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

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 Layouts By Layout ID operation, it enables retrieving layout information by providing a layout identifier within the request body.

Common scenarios where this node is beneficial include:

  • Fetching UI layout configurations dynamically based on layout IDs.
  • Automating administrative tasks related to layouts in ScaleFluidly.
  • Integrating layout data retrieval into workflows for further processing or decision-making.

For example, a user might want to retrieve the details of a specific page layout configuration to customize or audit the UI presentation dynamically.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). Determines which backend environment the requests are sent to.
Request JSON object containing the request body parameters required by the operation. For "Get Layouts By Layout ID", this should include the layout ID and any other necessary filters or parameters as defined by the API.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. Each item corresponds to the data returned by the API call, typically including layout details when using the "Get Layouts By Layout ID" operation.

If the API returns binary data (not indicated explicitly here), it would be included in the output accordingly, but this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token if provided in the input data headers under authorization.
  • No explicit internal credential names are exposed; users must configure appropriate API authentication externally.
  • The node depends on n8n's HTTP request helper methods to communicate with the ScaleFluidly API.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error. Ensure that the input data includes valid authorization headers or that credentials are properly configured.
  • Operation not found error: If the specified operation or intent name does not match any known mapping, the node will raise an error indicating the operation is not found. Verify the operation name matches one of the supported actions.
  • Invalid request body: Since the request body is user-provided JSON, malformed or incomplete JSON may cause API errors. Validate the JSON structure before execution.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the specified environment URL can cause request failures.

Links and References

Discussion