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 Insert or Update Templates operation, the node sends a JSON request body to the ScaleFluidly API endpoint responsible for inserting or updating templates in the system.

Typical use cases include automating template management within an organization's workflow, such as adding new document templates or updating existing ones programmatically. This can be beneficial in scenarios where templates need to be dynamically maintained based on external data or business logic, reducing manual effort and ensuring consistency.

Example: Automatically update email or document templates used in sales quotes or contracts whenever there is a change in branding or legal requirements.

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 related to the insert or update template operation.

If the API supports binary data output for this operation, it is not indicated in the provided code or properties; thus, only JSON output is expected.

Dependencies

• Requires access to the ScaleFluidly API endpoints.
• Optionally uses an API authentication token if configured; otherwise, it attempts unauthenticated requests.
• The node expects the user to provide a valid JSON request body matching the API specification for inserting or updating templates.
• No explicit environment variables are required beyond selecting the environment URL.

Troubleshooting

• Bearer token not found error: If processing multiple items, the first item's authorization header is extracted and reused. If missing, the node throws an error. Ensure that the input data includes a valid authorization token in the headers for the first item or configure credentials properly.
• Operation not found error: If the specified operation or intent does not match any known API endpoint, the node will throw an error indicating the operation was not found. Verify the operation name and resource selection.
• Invalid JSON request body: Since the request body is user-provided JSON, malformed or incorrect schema may cause API errors. Validate the JSON structure before execution.
• Network or environment URL issues: Selecting the wrong environment or having network connectivity problems to the chosen URL will result in request failures.

Links and References

• ScaleFluidly API Documentation (QA environment URL)
• Refer to your organization's ScaleFluidly API schema documentation for the exact structure of the "Request" JSON body for template insertion or updates.