ScaleFluidly

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 Get Rule Activity Timeline operation, the node fetches the activity timeline related to configuration rules within the ScaleFluidly system.

Typical use cases include:

• Tracking changes or events related to configuration rules in an administrative context.
• Auditing rule modifications or activities over time.
• Integrating rule activity data into workflows for monitoring or reporting purposes.

For example, a user might want to retrieve the timeline of all activities performed on pricing or product configuration rules to analyze recent changes or troubleshoot issues.

Properties

Details:

• Environment: Selects which ScaleFluidly environment to target (development, quality assurance, or local).
• Request: A JSON input where you specify any required parameters for the "Get Rule Activity Timeline" operation. This is mandatory and must be structured according to the API's expectations for this endpoint.

Output

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

• For the "Get Rule Activity Timeline" operation, the output JSON will contain details about the timeline of activities related to configuration rules. This may include timestamps, action types, user information, and other metadata describing each event in the timeline.

• The node does not explicitly handle binary data output.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• Optionally uses an API authentication token if provided; otherwise, it attempts unauthenticated requests.
• The node expects an API key or bearer token to be set either in the input headers or via n8n credentials configured externally.
• No additional external libraries beyond those bundled with n8n are required.

Troubleshooting

• Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no token has been previously stored in static workflow data, the node will throw an error. Ensure that the authorization token is correctly passed in the input or configured in credentials.
• Operation not found: If the specified operation (intent) does not match any known operation in the internal intent-to-URL mapping, the node will throw an error indicating the operation was not found. Verify the operation name is correct and supported.
• Invalid JSON in Request: Since the request body is a JSON object, malformed JSON will cause errors. Validate the JSON structure before execution.
• API Endpoint Unreachable: Selecting the wrong environment or having network issues can cause request failures. Confirm the environment URL is accessible and correct.

Links and References

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

This summary focuses on the Admin resource's Get Rule Activity Timeline operation based on the provided source code and property definitions.