ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, administration, and more. Specifically for the Quote resource and the Get Contact Details operation, it retrieves detailed contact information associated with a quote or related entities.

Common scenarios where this node is beneficial include:

• Fetching contact details linked to a sales quote for CRM updates.
• Automating workflows that require up-to-date contact information from the ScaleFluidly system.
• Integrating contact data retrieval into larger sales or order processing pipelines.

For example, a user might use this node to automatically pull contact details when a new quote is created or updated, enabling personalized communication or further processing in downstream systems.

Properties

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 Contact Details" operation, the output JSON will contain detailed contact information such as names, emails, phone numbers, roles, and other relevant metadata as provided by the API.

If the API supports binary data (e.g., attachments or documents related to contacts), the node would handle it accordingly, but based on the static code analysis, the primary output is JSON data representing contact details.

Dependencies

• Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
• Needs an authorization token (Bearer token) passed via the input data's headers on the first item or through node credentials if configured.
• The node optionally uses an API key credential configured in n8n for authentication fallback.
• No additional external dependencies beyond standard HTTP requests.

Troubleshooting

• Bearer token not found error: This occurs if the first input item does not contain an authorization header with a bearer token and no credential is configured. Ensure the token is provided either in the input data headers or via node credentials.
• Operation not found error: If the specified operation (intent) does not match any known API endpoint mapping, the node throws an error. Verify the operation name is correct and supported.
• API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause errors. Check the environment URL, request JSON structure, and API permissions.
• Empty or malformed request_info: The request body must be valid JSON matching the API expectations; otherwise, the API may return errors or empty results.

Links and References

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

Note: Internal credential names and implementation details have been generalized to comply with guidelines.