ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, administration, and more. Specifically, for the Quote resource and the Get Room Layout by Type operation, it retrieves layout information about a room based on its type from the ScaleFluidly system.

Typical use cases include:

  • Fetching room layout details dynamically during quote creation or modification workflows.
  • Automating retrieval of room configurations to assist in sales or project planning.
  • Integrating room layout data into broader automation pipelines that manage quotes and related resources.

For example, a user might configure this node to get the layout of a conference room type when preparing a quote for an event space rental.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local.

The node also requires selecting the Resource (Quote) and Operation (Get Room Layout by Type), but these are fixed by your input context.

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 "Get Room Layout by Type" endpoint, typically including details about the room layout structure, fields, and configuration relevant to the specified room type.

If the API returns binary data (not indicated here), it would be included accordingly, but this operation appears to return JSON data only.

Dependencies

  • Requires access to the ScaleFluidly API endpoints corresponding to the selected 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 provide appropriate API tokens or credentials as configured in n8n.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no prior token is stored, the node will throw an error. Ensure the input data includes valid authorization headers or configure credentials properly.
  • Operation not found: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify the operation parameter matches supported values.
  • API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request errors. Check environment selection and credentials.
  • Empty or malformed request_info: The node expects a JSON object for the request body; ensure this is correctly formatted.

Links and References


This summary focuses on the Quote resource's Get Room Layout by Type operation as requested, based on static analysis of the provided source code and property definitions.

Discussion