ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, MCP (a custom action), and admin tasks. Specifically for the Quote resource and the Participants For Quote operation, it allows users to retrieve or manage participants associated with a particular quote in the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Automating workflows that require fetching or updating participant information on quotes.
  • Integrating ScaleFluidly quote participant data into other systems or processes.
  • Managing collaboration or approval workflows by programmatically accessing quote participants.

For example, you might use this node to fetch all participants involved in a quote to notify them of updates or to audit who has access to a quote.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). This determines which ScaleFluidly instance the node interacts with.
Request JSON object representing the request body sent to the API. This contains parameters specific to the "Participants For Quote" operation, such as quote identifiers or filters.

Output

The node outputs an array of JSON objects corresponding to the API response from ScaleFluidly for the requested operation. The json output field contains the data returned by the ScaleFluidly API endpoint related to quote participants. This typically includes participant details such as user IDs, roles, contact information, and their association with the quote.

If the API returns binary data (not typical for this operation), it would be included accordingly, but based on the static code and operation context, the output is primarily JSON data representing participants.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use configured credentials named generically as an API key credential.
  • No explicit external libraries beyond standard n8n workflow helpers are required.
  • The node expects the user to configure the correct environment URL and provide appropriate authorization (bearer token) either via input data headers or stored credentials.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no credentials are configured, the node will throw an error. Ensure that either the input JSON includes an authorization header or that the node credentials are properly set.
  • Operation not found error: If the specified operation or intent name does not match any known mappings, the node will throw an error indicating the operation was not found. Verify the operation name matches one of the supported operations.
  • API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request failures. Check connectivity and authentication details.
  • Malformed JSON in Request property: Since the request body is user-provided JSON, ensure it is correctly formatted and contains all required fields for the operation.

Links and References


This summary focuses on the "Quote" resource and the "Participants For Quote" operation as requested, based on the provided source code and properties.

Discussion