ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, accounts, pricing, configuration, and administration within the ScaleFluidly platform. Specifically, for the "Quote" resource and the "Get Complete Account Details" operation, it retrieves comprehensive details about an account associated with a quote.

Common scenarios where this node is beneficial include:

  • Fetching detailed account information to enrich sales or CRM workflows.
  • Automating data retrieval for account-related decision-making processes.
  • Integrating ScaleFluidly account data into broader automation pipelines.

For example, a user might use this node to automatically pull all relevant account details when processing a quote, enabling downstream nodes to make informed decisions or update other systems accordingly.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local.
Request JSON object containing the request body parameters specific to the "Get Complete Account Details" operation. This typically includes identifiers or filters needed by the API to fetch the account details.

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 "Get Complete Account Details," the output JSON contains detailed account information as returned by the API, which may include fields such as account name, contact details, related quotes, orders, and other metadata.

If the API returns binary data (not typical for this operation), it would be included in the binary output, but this operation primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the selected Environment property.
  • Optionally uses an API authentication token passed via the input data's headers (authorization bearer token).
  • If no explicit authorization header is provided in the first input item, the node expects an API credential configured in n8n under a generic API key or token authentication method.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization bearer token in its headers and no API credential is configured, the node will throw an error. Ensure that either the input data includes a valid bearer token or configure the API credentials properly.
  • Operation not found: If the operation name does not match any known intent URL mapping, the node throws an error indicating the operation is invalid. Verify the operation parameter is correctly set to "get_complete_account_details" for this use case.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause HTTP errors. Check the environment URL, request JSON structure, and API permissions.
  • Invalid JSON in Request: The request_info property must be valid JSON. Malformed JSON will cause the node to fail.

Links and References

Discussion