ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

The "Update Room" operation in the Quote resource of the ScaleFluidly node allows users to update details of a room associated with a quote via the ScaleFluidly API. This operation is useful in scenarios where you need to modify room information dynamically within a sales or quoting workflow, such as updating participants, settings, or metadata related to a collaboration space tied to a quote.

Practical examples include:

  • Updating room attributes after changes in a sales deal.
  • Modifying participant lists or permissions in a quote-related room.
  • Synchronizing room data with external systems during quote updates.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). Selects which backend environment the request will be sent to.
Request JSON object representing the request body to send with the update room API call. This contains the specific fields and values to update in the room. It must be provided and formatted according to the ScaleFluidly API specification for updating rooms.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each JSON object represents the updated room data or the result of the update operation returned by the API.

If the API returns binary data (not indicated explicitly here), it would represent associated files or attachments related to the room update, but this node primarily handles JSON responses.

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 or credentials configured in n8n.
  • No explicit internal credential names are exposed; users must configure appropriate API authentication tokens or credentials externally.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no stored authorization header exists, the node will throw an error. Ensure that the input data includes valid authorization headers or that credentials are properly configured.
  • 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 operations.
  • Invalid JSON in Request: The request_info property must be a valid JSON object matching the API's expected schema. Malformed JSON or missing required fields can cause API errors.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the specified environment URL may cause request failures.

Links and References


This summary is based on static analysis of the node's source code and provided property definitions without runtime execution.

Discussion