ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

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 operation Get All Users And Contacts For Quote, it retrieves comprehensive user and contact information associated with a particular quote. This can be useful in scenarios where you need to gather all stakeholders involved in a quote for communication, reporting, or further processing.

Practical examples include:

  • Fetching all users and contacts linked to a quote before sending notifications.
  • Aggregating participant data for audit or approval workflows.
  • Integrating with CRM or sales tools to synchronize quote-related user/contact data.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request JSON object containing the request body parameters specific to the operation. This is required and must be provided by the user.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get All Users And Contacts For Quote" operation, the output JSON will contain detailed information about all users and contacts associated with the specified quote.

The exact structure depends on the API response but typically includes user identifiers, contact details, roles, and other metadata relevant to the quote participants.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • An authorization token (Bearer token) must be present in the input data headers under authorization for the first item; subsequent requests reuse this token.
  • Optionally supports n8n credentials for authentication if configured.
  • 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, the node will throw an error. Ensure that the input JSON includes valid authorization headers.
  • Operation not found: If the specified operation or intent does not match any known API endpoint mapping, an error will be thrown. Verify that the operation name is correct and supported.
  • API request failures: Network issues, invalid tokens, or incorrect request bodies may cause API errors. Check the request JSON and environment URL.
  • Empty or malformed request_info: The request body must be a valid JSON object as expected by the API. Invalid JSON or missing required fields will result in errors.

Links and References


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

Discussion