Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Order → Get Refund
AI-generatedOverview
This node integrates with the Haravan platform to interact with various resources such as orders, products, and accounts. Specifically, for the Order resource and the Get Refund operation, it retrieves refund information related to an order from Haravan. This is useful in e-commerce workflows where you want to automate refund tracking, update order statuses, or trigger follow-up actions based on refund data.
Practical examples include:
- Automatically fetching refund details when an order is updated.
- Integrating refund data into customer service dashboards.
- Triggering notifications or workflow steps when a refund is processed.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional fields to customize the request behavior. |
| - Logging Request | Boolean option to enable logging of each API request sent to Haravan for debugging purposes. |
Output
The node outputs an array of JSON objects representing the result of the requested operation. For the "Get Refund" operation under the "Order" resource, the output JSON contains refund-related data retrieved from Haravan.
The structure of the output JSON includes at least these fields:
executionId: The unique identifier of the current execution.resource: The resource type, here "Order".operation: The operation performed, here "Get Refund".status: The status of the operation (e.g., "completed").timestamp: The ISO timestamp when the operation was executed.
If the operation returns multiple items, they are all included in the output array.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Haravan platform.
- Depends on the external Haravan API accessible via network.
- The node uses internal helper libraries bundled with the node implementation for API communication and data handling.
Troubleshooting
Common issues:
- API authentication failures due to invalid or missing credentials.
- Network connectivity problems preventing access to Haravan API.
- Unexpected response formats if Haravan API changes.
Error messages:
- Errors thrown during execution will include the item index causing the failure.
- If "Continue On Fail" is disabled, the node stops on first error; enabling it allows processing remaining items.
- Debugging can be facilitated by enabling the "Logging Request" option to see detailed API request logs.
Links and References
- Haravan Official API Documentation (for detailed API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes