Actions39
- Account Actions
- Client Actions
- Document Actions
- Product Actions
- Receipt Actions
- Store Actions
- Supplier Actions
Receipt → Get Receipt by ID
AI-generatedOverview
This node integrates with the Vendus API, specifically enabling users to retrieve detailed information about receipts by their ID. It is useful in scenarios where you need to fetch a specific receipt's data for review, processing, or further automation within your workflows. For example, you might use this node to pull receipt details after a sale to update accounting records, trigger notifications, or generate reports.
Properties
| Name | Meaning |
|---|---|
| Receipt Name or ID | The unique identifier or name of the receipt you want to retrieve. You can select from a list or specify an ID using an expression. |
| Options | Additional optional settings: - Enable Debug Logging: Toggle detailed debug logs for troubleshooting API calls. |
Output
The node outputs JSON data representing the receipt retrieved from the Vendus API. This JSON contains all the receipt's details as provided by the API, such as receipt metadata, line items, totals, dates, and related client or store information.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Vendus API via an API key credential.
- The node expects the base URL and authentication credentials to be configured in n8n credentials for Vendus.
- Optional debug logging can be enabled to assist with troubleshooting API requests.
Troubleshooting
- Missing or invalid Receipt ID: If the receipt ID parameter is not provided or incorrect, the node will throw an error indicating the required parameter is missing or invalid.
- API connectivity issues: Network problems or incorrect API credentials will cause request failures. Enabling debug logging can help identify these issues by providing detailed request and response logs.
- No routing configuration found: This internal error indicates that the requested resource-operation combination is not supported or misconfigured.
- Unexpected API responses: If the API returns unexpected data or errors, verify the receipt ID exists and the API service is operational.
To resolve common errors:
- Ensure the receipt ID is correctly specified.
- Verify API credentials and base URL are correct.
- Use the "Enable Debug Logging" option to get detailed logs for diagnosing issues.
Links and References
- Vendus API Documentation (as referenced in the node description)
- n8n Expressions Documentation – for using expressions in parameters