ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API
Join our community

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, rooms, products, pricing, configuration, and administration within the ScaleFluidly platform. Specifically, for the Quote resource and the Delete Participants For Room operation, it allows users to remove participants from a specified room associated with a quote.

Common scenarios where this node is beneficial include:

  • Managing collaboration on quote-related rooms by dynamically adding or removing participants.
  • Automating participant management in sales or project rooms based on workflow triggers.
  • Keeping room membership up-to-date when roles or responsibilities change.

For example, if a team member leaves a project or no longer needs access to a quote room, this node can be used to programmatically remove them, ensuring proper access control and communication flow.

Properties

Name Meaning
Environment The target environment for the API call. Options are:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)
Request JSON object containing the request body required by the API to delete participants from a room. This typically includes identifiers such as room ID and participant details to specify which participants to remove.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each response corresponds to the result of the delete participants request for a room.

  • The json output field contains the parsed JSON response from the API, which may include success confirmation, error messages, or details about the deleted participants.
  • There is no binary data output from this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token if provided in the input data headers under authorization.
  • No explicit external npm packages beyond n8n's standard helpers are required.
  • The node expects the user to configure the environment URL correctly and provide valid request JSON for the operation.

Troubleshooting

  • Bearer token not found: 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 authorization token is included in the input or configured 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 operations.
  • Invalid request JSON: Malformed or incomplete JSON in the Request property may cause API errors. Validate the JSON structure before execution.
  • API connectivity issues: Network problems or incorrect environment URLs can lead to request failures. Confirm the environment URL is reachable and correct.

Links and References

Discussion