ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, MCP (a custom module), and admin tasks. Specifically for the Quote resource and the Participants For Room operation, it retrieves participant information associated with a particular room in the quoting system.

Common scenarios where this node is beneficial include:

  • Fetching all users or contacts involved in a specific quote room to display or process participant data.
  • Managing collaboration by identifying participants in a room before sending notifications or updates.
  • Integrating participant data into workflows that automate quote approvals or reviews.

Example use case: Automatically retrieve all participants of a quote room to send them an update email when the quote status changes.

Properties

Name Meaning
Environment The target environment for the API call. Options are:
- Dev (development server)
- QA (quality assurance server)
- Local (local server instance)
Request JSON object containing the request body parameters required by the API endpoint for the operation. This typically includes identifiers like room ID or filters relevant to fetching participants.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Participants For Room" operation, the output JSON contains details about the participants associated with the specified room. This may include user IDs, contact information, roles, and other metadata as provided by the API.

If the API returns binary data (not typical for this operation), it would be included accordingly, but primarily the output is structured JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoints corresponding to the selected environment.
  • Optionally uses an API authentication token if configured; otherwise, it expects a bearer token in the input data headers.
  • No explicit external libraries beyond n8n's standard HTTP request helpers are needed.

Troubleshooting

  • Bearer token not found error: 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 API key credential is set up in n8n or the input data includes a valid authorization header.
  • Operation not found error: If the operation name does not map to a known API endpoint, the node will fail. Verify that the operation parameter is correctly set to "get_participants_for_room".
  • API connectivity issues: Check the selected environment URL and network accessibility. Also verify that the API token or credentials are valid and have sufficient permissions.
  • Malformed request body: The request_info JSON must conform to the expected structure for the API call. Invalid or missing fields can cause API errors.

Links and References


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

Discussion