ScaleFluidly

Overview

This node integrates with the ScaleFluidly API to perform various operations across multiple resources, including Admin, Quote, Configure, Pricing, and MCP. Specifically for the Admin resource and the Delete Layouts operation, it allows users to delete layout configurations within the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Automating the cleanup or removal of outdated or unused page layouts in an administrative environment.
• Managing UI configurations programmatically as part of a larger workflow that maintains or updates system settings.
• Integrating with other systems to synchronize layout changes or deletions based on external triggers.

For example, a user might use this node to delete specific admin page layouts after a reorganization of the UI or when deprecating certain features.

Properties

• Environment selects which ScaleFluidly environment the request will be sent to.
• Request is a JSON input that must contain the necessary data for the delete layouts operation (e.g., layout IDs or criteria).

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the delete layouts request.

If the API returns binary data (not indicated here), it would be included accordingly, but this operation primarily deals with JSON responses confirming deletion status or errors.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• Optionally uses an API key credential configured in n8n for authenticated requests.
• The node dynamically constructs the request URL based on the selected environment and operation.
• No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

• Bearer token not found: If the first input item does not contain an authorization header with a bearer token, subsequent requests will fail. Ensure the first input includes valid authentication headers or configure the API credentials properly.
• Operation not found error: This occurs if the specified operation name does not match any known operation in the internal intent-to-URL mapping. Verify the operation name is correct and supported.
• Invalid JSON in Request property: The request_info property must be valid JSON matching the API's expected schema. Malformed JSON or missing required fields will cause API errors.
• Network or environment URL issues: Confirm the selected environment URL is reachable and correct. Local or dev URLs may require VPN or local network access.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (Dev environment)
• n8n HTTP Request Node documentation for understanding request options and authentication handling.

This summary focuses on the Admin resource's Delete Layouts operation as requested, based on static analysis of the provided source code and properties.