RedStage

Overview

This node integrates with the Red Stage API to perform various operations on resources such as orders, shipments, deliveries, inventory, and logs.
For the Order resource with the Hold Order operation, the node allows you to place a hold on a specific order by its unique identifier.
Typical use cases include pausing order processing due to payment issues, customer requests, or inventory problems.

Example scenario:

• An e-commerce workflow where an order needs to be held automatically if a fraud check fails.

Properties

Output

The output is a JSON object (or array of objects) representing the response from the Red Stage API after attempting to hold the specified order.
The structure of the output depends on the API's response, but typically includes fields indicating the status of the operation and any relevant order details.

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

Dependencies

• Red Stage API: Requires valid credentials configured in n8n under the name redStageApi.
• No additional 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.
• Missing Credentials: If the redStageApi credentials are not set up, the node will fail to authenticate.
• Unknown Resource/Operation: If the resource or operation is misspelled or unsupported, the node will throw an error like:
  "The resource \"<resource>\" is not known!"

Error Handling:

• If "Continue On Fail" is enabled, errors are returned in the output as { "error": "<message>" }.
• Otherwise, execution stops and the error is thrown.

Links and References

• n8n Documentation
• Red Stage API documentation (contact your Red Stage representative for access)