ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically for the Admin resource and the Add or Update Approval operation, the node sends a custom JSON request body to the ScaleFluidly API endpoint responsible for managing approvals. This enables automation of approval workflows within an organization’s sales or operational processes.

Common scenarios include:

• Adding or updating approval rules or approvers on quotes or other entities.
• Automating administrative tasks related to user permissions or workflow approvals.
• Integrating approval management into broader automation workflows in n8n.

Practical example:

• Automatically add an approver to a quote when certain conditions are met, by sending the appropriate approval data in the request body.

Properties

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 contains the API response data for the respective request made.

If the API returns binary data (not indicated in the provided code), it would be included accordingly, but based on the static analysis, the output is JSON only.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• Optionally uses an API authentication token passed via an authorization header. If the first input item includes an authorization bearer token in its headers, that token is reused for subsequent requests.
• No explicit internal credential type names are exposed; users must provide valid authorization tokens or configure credentials externally.
• The node depends on n8n's HTTP request helper methods to make authenticated API calls.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization bearer token in its headers, and no other token is provided, the node will throw an error. Ensure the first input item includes a valid authorization token or configure credentials properly.
• Operation not found error: If the specified operation (intent) does not match any known API endpoint mapping, the node throws an error indicating the operation was not found. Verify the operation name is correct and supported.
• Invalid JSON in Request property: Since the request body is user-provided JSON, malformed JSON will cause the API call to fail. Validate the JSON structure before running the node.
• Environment URL issues: Selecting an incorrect environment may lead to connection errors. Confirm the environment matches the intended API server.

Links and References

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

This summary is based solely on static analysis of the provided source code and property definitions.