Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Order → Get Transactions
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 Transactions operation, it retrieves transaction data related to orders from Haravan. This is useful for workflows that need to process or analyze order payment transactions, track financial activity, or synchronize transaction records with other systems.
Practical examples include:
- Automatically fetching all transactions for a specific order to update accounting software.
- Monitoring payment statuses and triggering follow-up actions based on transaction results.
- Aggregating transaction data for reporting or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional fields. Currently supports: - Logging Request: Enable or disable logging of each API request sent to Haravan for debugging and monitoring purposes (boolean). |
Output
The node outputs an array of JSON objects representing the transaction data retrieved from Haravan for the specified order(s). Each item in the output corresponds to a transaction record with details such as transaction ID, amount, status, timestamps, and other relevant metadata.
If enabled, the node can also output logs related to the API requests made during execution, which helps in debugging but does not alter the main transaction data output.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate with the Haravan platform.
- The node depends on the Haravan API being accessible and properly configured.
- No additional external services are required beyond the Haravan API.
- n8n must have the appropriate credentials set up to allow authenticated API calls.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Network connectivity problems preventing access to the Haravan API.
- Rate limiting or API quota exceeded errors from Haravan.
- Incorrect resource or operation parameters leading to empty or error responses.
Error messages:
- Errors thrown by the node will indicate the item index causing the failure if multiple inputs are processed.
- Enabling "Logging Request" can help identify issues by providing detailed request/response logs.
- To resolve authentication errors, verify the API key and permissions.
- For network or rate limit errors, check connectivity and consider retry strategies or contact Haravan support.
Links and References
- Haravan API Documentation (for detailed API endpoints and data structures)
- n8n documentation on creating custom nodes