ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, rooms, users, and contacts within the ScaleFluidly platform. Specifically, for the "Quote" resource and the operation "Get Available Users And Contacts For Room," it retrieves a list of users and contacts that are available in a particular room context.

Common scenarios where this node is beneficial include:

• Fetching participants who can be added or assigned to a room associated with a quote.
• Managing collaboration by identifying all potential users and contacts linked to a room.
• Automating workflows that require knowledge of room membership or availability of users/contacts.

Practical example:

• A sales automation workflow where before sending a quote for approval, the system fetches all available users and contacts in the quote’s room to assign tasks or notify relevant stakeholders.

Properties

The Request property expects a JSON input that defines the details required by the API endpoint for fetching available users and contacts for a room. This may include identifiers like room ID or filters as per the API specification.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Available Users And Contacts For Room" operation, the output JSON typically includes:

• Lists of user objects and contact objects available in the specified room.
• Each user/contact object may contain fields such as ID, name, email, role, status, and other metadata relevant to their participation in the room.

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

Dependencies

• Requires access to the ScaleFluidly API endpoints corresponding to the selected environment.
• An API authentication token (bearer token) must be provided via HTTP headers in the input data or configured credentials.
• No internal credential names are exposed; users must supply valid authorization tokens.
• The node uses standard HTTP requests with JSON payloads.

Troubleshooting

• Bearer token not found error: Occurs if the authorization header with a bearer token is missing in the first input item and not stored in static workflow data. Ensure the first input item contains proper authorization headers or configure credentials correctly.
• Operation not found error: If the specified operation or intent does not match any known API endpoint, verify the operation name and spelling.
• API request failures: Check network connectivity, environment URL correctness, and validity of the request JSON body.
• Invalid JSON in Request property: Ensure the JSON input is well-formed and matches the expected schema for the API call.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (Dev environment)
• n8n HTTP Request Node documentation for understanding request configuration: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/

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