ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, and more. Specifically, for the Quote resource and the operation Get QuoteId And Type From SfExternalId, it retrieves the quote ID and type based on a Salesforce external ID provided in the request.

Common scenarios where this node is beneficial include:

  • Synchronizing quote data between Salesforce and ScaleFluidly systems.
  • Automating workflows that require fetching quote identifiers and types from external IDs.
  • Integrating quote-related data retrieval into broader automation pipelines.

For example, a user might input a Salesforce external ID in the request JSON, and the node will return the corresponding quote ID and type from ScaleFluidly, enabling further processing or decision-making downstream.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local (with respective URLs).
Request JSON object containing the request body specific to the operation. For this operation, it should include the Salesforce external ID details needed to fetch the quote ID and type.

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 given request. For the "Get QuoteId And Type From SfExternalId" operation, the output JSON will contain fields representing the quote ID and quote type retrieved from the API.

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

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the selected environment.
  • Optionally uses an API key credential configured in n8n for authenticated requests.
  • The node expects the authorization token to be present in the input data headers or uses the configured credential for authentication.
  • No other external dependencies are required.

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 includes a valid authorization header or the node is configured with appropriate API credentials.
  • Operation not found: If the operation name does not match any known intent URL mapping, the node will throw an error indicating the operation is not found. Verify the operation parameter is correctly set.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause API errors. Check the environment URL and the structure of the JSON request body.
  • Invalid JSON in Request: The request_info property must be valid JSON. Malformed JSON will cause the node to fail.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions.

Discussion