ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, and administration within the ScaleFluidly platform. Specifically for the Quote resource and the Get Quote ActivityTimeline operation, it retrieves the activity timeline data associated with a particular quote. This can be useful for tracking changes, approvals, or other events related to a quote over time.

Common scenarios include:

• Monitoring the history of actions taken on a quote.
• Auditing user activities or system events linked to a quote.
• Displaying a timeline of quote-related events in dashboards or reports.

Example use case: A sales manager wants to see all approval steps and participant interactions that occurred on a specific quote to understand its progress and status changes.

Properties

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 Quote ActivityTimeline operation, this typically includes structured data representing the timeline of activities related to the quote, such as events, timestamps, user actions, and statuses.

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.
• Needs an API authentication token (bearer token) provided via input data headers or configured credentials.
• The node supports selecting different environments (Dev, QA, Local) which correspond to different base URLs for the API.
• No additional external dependencies beyond standard HTTP requests and n8n's credential management.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no token is stored in static workflow data, the node will throw an error. Ensure the token is correctly passed in the input or configured in credentials.
• Operation not found error: If the specified operation or intent name does not match any known mapping, the node will report an error. Verify the operation name is correct and supported.
• API request failures: Network issues, incorrect environment URL, or invalid request body may cause API errors. Check the environment setting, request JSON structure, and API token validity.
• Empty or malformed request_info: The request body must be valid JSON matching the expected schema for the operation; otherwise, the API may reject the request.

Links and References

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

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