ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configurations, pricing, and administrative tasks. Specifically, for the Quote resource and the Add Participants For Room operation, it allows users to add participants to a collaboration room associated with a quote. This is useful in scenarios where multiple stakeholders need to be involved in reviewing or approving a quote within a shared workspace.

Practical examples include:

  • Adding sales team members or approvers to a quote discussion room.
  • Collaborating with external contacts by adding them as participants to the room.
  • Managing access and involvement dynamically during the quote lifecycle.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request JSON object representing the request body sent to the API. This contains details such as participant information to add to the room.

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 result of the "Add Participants For Room" operation, typically including confirmation of added participants or error details if the operation failed.

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

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the selected environment.
  • Optionally uses an API authentication token passed via the Authorization header. This token must be provided in the input data headers or managed through n8n credentials configured for the ScaleFluidly API.
  • No other external dependencies are required.

Troubleshooting

  • Bearer token not found: If the authorization token is missing in the first input item's headers and not stored statically, the node will throw an error. Ensure that the input JSON includes a valid bearer token in the headers or configure the API 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 actions.
  • API errors: Errors returned by the ScaleFluidly API (e.g., invalid request body, unauthorized access) will be included in the output JSON. Check the request body format and authentication details.
  • Environment URL issues: Selecting an incorrect environment may lead to connection failures. Confirm the environment URL is reachable and correct.

Links and References


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

Discussion