CloudBlue Commerce SimpleAPI

Overview

This node interacts with a cloud commerce platform to manage various resources, including service plans. Specifically, the "Plan" resource with the "Get" operation allows users to retrieve detailed information about a specific service plan by its unique identifier. This is useful in scenarios where you need to fetch plan details for reporting, validation, or further processing within an automation workflow.

For example, you might use this node to:

• Retrieve pricing and feature details of a particular service plan before provisioning.
• Validate that a given plan ID exists and obtain its metadata.
• Integrate plan data into customer onboarding workflows.

Properties

Output

The output contains a JSON object representing the details of the requested service plan. This typically includes all relevant attributes of the plan such as its name, description, pricing, features, and status. The exact structure depends on the API response but will be a single JSON object per execution item.

No binary data output is indicated by the source code.

Dependencies

• Requires an initialized API service connection to the cloud commerce platform. This involves providing appropriate API credentials (e.g., an API key or authentication token) configured in n8n.
• The node relies on a resource registry system internally to map resource names to their implementations.
• No additional external dependencies are explicitly required beyond the API access.

Troubleshooting

• Resource Not Found Error: If the specified resource ("plan") is not recognized or not migrated, the node throws an error indicating the resource is unavailable. Ensure the node version supports the "plan" resource.
• Unexpected Error: If the resource instance cannot be retrieved despite existing, it indicates an internal inconsistency; updating the node or reinstalling may help.
• API Errors: If the plan ID is invalid or the API call fails, the node will throw an error with the message returned from the API. Verify the plan ID correctness and API connectivity.
• Continue On Fail: If enabled, errors for individual items will be captured in the output JSON under an error field instead of stopping execution.

Links and References

• Refer to your cloud commerce platform's API documentation for the exact schema and fields returned by the "Get Plan" endpoint.
• n8n documentation on creating custom nodes for more details on node development and error handling.