ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API to perform various operations across multiple resources, including quotes. Specifically, for the Quote resource and the Get All Emails operation, it retrieves all email-related data associated with quotes from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

• Extracting all email communications or contacts related to quotes for reporting or auditing.
• Automating workflows that require fetching quote-related emails to trigger notifications or updates.
• Integrating quote email data into CRM or other business systems for enhanced customer insights.

For example, a sales automation workflow could use this node to fetch all emails linked to a particular quote and then analyze or forward them as part of a follow-up process.

Properties

The node also requires selecting the Resource (here fixed to "Quote") and the Operation (here "Get All Emails"). Additional parameters like request_info (a JSON object) can be provided to customize the request body if needed, though for "Get All Emails" this may not be mandatory.

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 All Emails" operation on the Quote resource, the output will contain email data related to quotes, such as email addresses, message metadata, or communication logs depending on the API's response structure.

No binary data output is indicated by the source code.

Dependencies

• Requires access to the ScaleFluidly API endpoint specified by the chosen environment (Dev, QA, or Local).
• An authorization token (Bearer token) must be present in the input data headers or provided via credentials to authenticate API requests.
• Optional: A configured API authentication credential within n8n can be used if no explicit bearer token is found in the input.

Troubleshooting

• Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no credential is configured, the node will throw an error. Ensure the token is correctly passed in the input or set up proper API credentials.
• Operation not found error: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify the operation parameter matches supported operations.
• API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request errors. Check environment selection, token validity, and network connectivity.
• Malformed request_info JSON: If the optional request_info parameter is provided but contains invalid JSON, the node may fail. Validate JSON syntax before execution.

Links and References

• ScaleFluidly API Documentation (QA environment)
• n8n HTTP Request Node Documentation — for understanding how API requests are made within n8n nodes.

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