RedStage

Overview

This n8n node interacts with the RedStage API to perform various operations on different resources. For the Order resource and specifically the Unhold Order operation, the node allows users to unhold an order by providing its unique identifier. This is useful in scenarios where orders have been previously placed on hold (e.g., due to payment issues or manual review) and now need to be released for further processing.

Practical Example:
A business using RedStage e-commerce platform can automate workflows such as:

• Automatically unholding orders when a payment confirmation is received.
• Integrating with customer service tools to allow agents to unhold orders directly from n8n.

Properties

Output

The output will be a JSON object (or array of objects) representing the response from the RedStage API after attempting to unhold the specified order. The exact structure depends on the API's response, but typically includes fields such as status, message, and possibly updated order details.

If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.

Example output:

[
  {
    "status": "success",
    "orderId": "12345",
    "message": "Order successfully unheld."
  }
]

Or, in case of error (with continue on fail):

[
  {
    "error": "Order not found"
  }
]

Dependencies

• External Service: Requires access to the RedStage API.
• Credentials: Must configure redStageApi credentials in n8n.
• Environment: No special environment variables are required beyond standard n8n credential setup.

Troubleshooting

• Common Issues:

  • Invalid Order Unique ID: If the provided Order Unique ID does not exist, the API may return an error such as "Order not found".
  • Missing Credentials: If the redStageApi credentials are not set up, the node will fail to authenticate.
  • API Connectivity Issues: Network problems or incorrect API endpoint configuration can cause failures.

• Error Messages:

  • "The resource \"order\" is not known!" – This indicates an internal misconfiguration; ensure the resource is set to "Order".
  • Error messages from the API (e.g., "Order not found") will appear in the output if "Continue On Fail" is enabled.

How to resolve:

• Double-check the Order Unique ID.
• Ensure RedStage API credentials are correctly configured in n8n.
• Verify network connectivity and API endpoint settings.

Links and References

• RedStage Official Website
• n8n Documentation: Creating Custom Nodes
• n8n Credentials Setup