Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Order → Get All Checkouts
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 All Checkouts" operation, it retrieves all checkout records from Haravan. This is useful for workflows that need to process or analyze customer checkout data, track sales, or synchronize order information with other systems.
Practical examples include:
- Automatically fetching all recent checkouts to update a CRM or ERP system.
- Monitoring checkout activity to trigger marketing campaigns or notifications.
- Aggregating checkout data for reporting or analytics purposes.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional settings: |
| - Logging Request | Boolean flag to enable logging of each API request sent to Haravan for debugging purposes. |
Output
The node outputs an array of JSON objects representing the retrieved checkout data. Each item in the output corresponds to a checkout record fetched from Haravan.
- The
jsonfield contains the checkout details. - If enabled, the node logs request details internally for debugging but does not output binary data.
Dependencies
- Requires an API key credential to authenticate with the Haravan platform.
- The node depends on the external Haravan API service to fetch checkout data.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Network errors or timeouts when connecting to the Haravan API.
- API rate limits being exceeded if too many requests are made in a short period.
Error messages:
- Errors thrown by the node will indicate the item index where the failure occurred.
- Enabling the "Logging Request" option can help diagnose issues by providing detailed request logs.
Resolutions:
- Verify that the API key credential is correctly configured and has necessary permissions.
- Ensure network connectivity to the Haravan API endpoint.
- Use the logging option to inspect request/response details and adjust workflow logic accordingly.
- Implement error handling in the workflow to manage rate limits or transient errors gracefully.
Links and References
- Haravan Official API Documentation
- n8n Documentation on Creating Custom Nodes