RedStage

Overview

The RedStage node for n8n allows you to interact with the Red Stage API. When configured with the Resource: Log and Operation: Write Log, this node enables you to send log entries to the Red Stage system. This is useful for tracking events, errors, or custom messages from your workflow executions.

Common scenarios:

• Logging workflow events (e.g., order processed, shipment sent).
• Recording error or warning messages for later analysis.
• Sending debug information during development or troubleshooting.

Practical example:
You might use this node to write an "Error" severity log entry whenever a payment fails in your e-commerce automation, including details about the failed transaction.

---

Properties

Name	Type	Meaning
Severity	options	The level of the log message. Options: Debug, Info, Warn, Error.
Message	string	The main log message. Maximum length: 255 characters.
Additional Fields	collection	Optional extra fields for the log entry:
Facility	string	Facility or subsystem name. Maximum length: 32 characters.
Entity	string	Entity related to the log entry (e.g., user, order).
Store ID	number	Store identifier associated with the log.
Detail Message	string	Detailed message for the log. Maximum length: 2048 characters.

---

Output

The node returns the response from the Red Stage API after writing the log entry. The structure of the json output field will typically include:

• Confirmation of the log entry creation.
• Any data returned by the API, such as log ID or status.

Example output structure:

[
  {
    "success": true,
    "logId": "12345",
    "message": "Log entry created"
  }
]

Note: The exact fields depend on the Red Stage API's response.

---

Dependencies

• External Service: Requires access to the Red Stage API.
• API Credentials: You must configure the redStageApi credential in n8n.
• Environment: No special environment variables are required beyond standard n8n setup.

---

Troubleshooting

Common issues:

• Invalid credentials: If the redStageApi credential is missing or incorrect, the node will fail to authenticate.
• Field length exceeded: If "Message", "Facility", or "Detail Message" exceed their maximum lengths, the API may reject the request.
• Unknown resource/operation: If the resource or operation is not recognized, you'll see an error like:
  The resource "log" is not known!

How to resolve:

• Double-check your API credentials in n8n.
• Ensure all text fields respect their maximum character limits.
• Make sure you select valid resource and operation combinations.

---

Links and References

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