ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, accounts, contacts, and other resources. Specifically, for the Quote resource and the Get Contacts For Account operation, it retrieves contact information associated with a given account. This is useful in scenarios where you need to fetch all contacts linked to an account for further processing, such as sending notifications, generating reports, or syncing data with other systems.

Practical examples include:

• Automatically retrieving all contacts for an account before sending a quote.
• Fetching contact details to update CRM records or trigger workflows.
• Integrating with external systems that require contact lists per account.

Properties

The Request property must be provided as a JSON object and contains the necessary parameters for the "Get Contacts For Account" operation, such as the account identifier or filters.

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 Contacts For Account" operation, this typically includes:

• Contact details such as names, emails, phone numbers, roles, and any other metadata returned by the API.
• The structure depends on the API response but generally represents a list of contacts associated with the specified account.

No binary data output is indicated for this operation.

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
• Optionally uses an API authentication token passed via HTTP headers (Bearer token).
• If no explicit authorization header is found in the input data, the node attempts to use configured credentials for authentication.
• No additional external dependencies beyond standard HTTP requests.

Troubleshooting

• Bearer token not found: 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 that either the input data includes a valid authorization header or that the node is configured with appropriate API credentials.
• Operation not found: 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 request bodies can cause request errors. Check the environment setting and the JSON request body for correctness.
• Malformed JSON in Request: The request_info property must be valid JSON. Invalid JSON will cause parsing errors.

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.