ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically, for the Admin resource and the Get Price Book Item Activity Timeline operation, the node fetches the activity timeline related to a specific price book item. This can be useful for tracking changes, updates, or events associated with price book items in a sales or pricing system.

Common scenarios include:

  • Auditing price book item changes over time.
  • Monitoring user activities or system events related to price book items.
  • Integrating price book item activity data into workflows for reporting or alerting.

Example use case:

  • A sales manager wants to review all modifications made to a particular price book item to understand its history before approving a new pricing strategy.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). Determines which backend environment the request is sent to.
Request JSON object containing the request body parameters required by the API for the selected operation. This must be provided according to the API's expected schema for the "Get Price Book Item Activity Timeline" operation.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested operation. For the "Get Price Book Item Activity Timeline" operation, the output JSON contains the timeline data of activities related to the specified price book item. This typically includes details such as timestamps, user actions, changes made, and other relevant metadata describing the item's activity history.

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

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the chosen environment.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use stored credentials configured in n8n under a generic API key credential.
  • No explicit external libraries beyond standard n8n workflow helpers are used.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no stored credentials are available, the node will throw an error. Ensure that either the input data includes a valid authorization token or that the node is configured with appropriate API credentials.
  • Operation not found error: 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 that the operation parameter is correctly set to "get_price_book_item_activity_timeline" or the exact supported operation string.
  • Invalid request body: Since the request body is passed as raw JSON, malformed or incomplete JSON may cause API errors. Validate the JSON structure against the API documentation for the operation.
  • Environment URL issues: Selecting an incorrect or unreachable environment URL will result in network errors. Confirm the environment setting matches your deployment.

Links and References


Note: The exact structure of the request JSON and the response depends on the ScaleFluidly API specification for the "Get Price Book Item Activity Timeline" operation, which should be referenced for detailed field definitions.

Discussion