ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

The "Create Room" operation within the Quote resource of this ScaleFluidly node allows users to create a new room entity by sending a structured JSON request to the ScaleFluidly API. This node is useful in scenarios where automation workflows need to programmatically manage collaboration or workspace rooms related to quotes, such as setting up discussion spaces for sales quotes or project rooms linked to quote processes.

Practical examples include:

  • Automatically creating a room when a new sales quote is generated.
  • Integrating with CRM systems to provision collaboration rooms tied to specific customer quotes.
  • Streamlining communication setup in sales pipelines by automating room creation based on quote data.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request The JSON-formatted request body containing details required to create the room. This must be provided and formatted according to the API's expectations for room creation.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the "Create Room" request, typically including details about the newly created room such as its ID, name, status, and other metadata returned by the API.

If the API supports binary data in responses (not indicated here), it would be included accordingly, but this node primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Needs an authorization token (Bearer token) passed via headers; this token is extracted from the first input item's JSON headers or managed internally.
  • Optionally uses an API key credential configured in n8n under a generic API authentication method if no explicit bearer token is found.
  • No additional external dependencies are indicated.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, the node will throw an error. Ensure that the input data includes valid authorization headers or configure the API credentials properly.
  • Operation not found: If the operation name does not map to a known intent URL, an error will occur. Verify that the operation parameter is correctly set to "create_room" for this use case.
  • Invalid JSON in Request: The "Request" property must be valid JSON matching the API schema. Malformed JSON or missing required fields will cause API errors.
  • Environment URL issues: Selecting the wrong environment may lead to connection failures or unexpected responses. Confirm the environment matches the intended API deployment.

Links and References

Discussion