ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, rooms, users, contacts, and other resources within the ScaleFluidly platform. Specifically, for the "Quote" resource and the operation "Get All Users And Contacts For Room," it retrieves all user and contact information associated with a particular room.

Common scenarios where this node is beneficial include:

• Fetching comprehensive participant lists (users and contacts) involved in a specific room for collaboration or review.
• Automating workflows that require up-to-date user and contact data linked to rooms in sales or project management contexts.
• Integrating ScaleFluidly data into other systems by extracting detailed room participant information.

Practical example:

• A sales automation workflow that triggers when a new room is created and needs to notify all participants. This node can fetch all users and contacts for that room to send notifications or update CRM records.

Properties

The "Request" property must be provided as a JSON object tailored to the "Get All Users And Contacts For Room" operation's API requirements.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response from the ScaleFluidly API for the requested operation.

For the "Get All Users And Contacts For Room" operation, the output JSON typically includes details about all users and contacts associated with the specified room, such as their identifiers, names, roles, and contact information.

No binary data output is indicated for this operation.

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the selected environment (Dev, QA, or Local).
• Optionally uses an API authentication token if provided via credentials or authorization headers.
• No explicit internal credential names are exposed; users must configure appropriate API authentication in n8n.

Troubleshooting

• Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no prior authorization header is stored, the node will throw an error. Ensure that the API token is correctly set either in the input headers or via configured credentials.
• Operation not found: If the specified operation name does not match any known operation in the intent-to-URL mapping, the node throws an error indicating the operation is not found. Verify the operation name is correct and supported.
• Invalid request body: Providing malformed or incomplete JSON in the "Request" property may cause API errors. Validate the JSON structure against the ScaleFluidly API documentation for the operation.
• Environment URL issues: Selecting an incorrect or unreachable environment URL will result in network errors. Confirm the environment setting matches your deployment.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (Dev environment)

Note: Replace URLs with actual API docs relevant to your environment.