Actions39
- Account Actions
- Client Actions
- Document Actions
- Product Actions
- Receipt Actions
- Store Actions
- Supplier Actions
Receipt → Update Receipt
AI-generatedOverview
This node integrates with the Vendus API to update an existing receipt in your invoicing and business management system. It allows you to modify details such as the amount, date, description, and status of a receipt by specifying its unique identifier.
Common scenarios where this node is beneficial include:
- Correcting or updating receipt information after a transaction.
- Changing the status of a receipt (e.g., marking it as paid or canceled).
- Adding or modifying descriptions or dates for bookkeeping accuracy.
For example, you might use this node in an automation workflow that updates receipts based on payment confirmations received from another system.
Properties
| Name | Meaning |
|---|---|
| Receipt Name or ID | The unique identifier or name of the receipt you want to update. Can be set via expression. |
| Update Fields | Collection of fields to update on the receipt: |
| - Amount | The new amount value for the receipt. |
| - Date | The new date for the receipt in YYYY-MM-DD format. |
| - Description | A textual description or note about the receipt. |
| - Status | The current status of the receipt. Options: Active, Canceled, Paid. |
| Custom JSON | A JSON object allowing custom data to be sent with the update request for advanced use cases. |
| Options | Additional options for the operation: |
| - Enable Debug Logging | Boolean flag to enable detailed debug logs for troubleshooting API calls. |
Output
The node outputs the updated receipt data returned by the Vendus API in the json field of the output item. This typically includes all receipt properties after the update, reflecting the new state of the receipt.
If the API returns any errors or issues, those will be included in the output as error objects if "Continue On Fail" is enabled.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Vendus API using an API key credential configured in n8n.
- The node uses the base URL and authentication credentials provided in the Vendus API credential configuration.
- Network access to the Vendus API endpoint is necessary.
Troubleshooting
- Missing or invalid Receipt ID: If the receipt identifier is not provided or incorrect, the node will throw an error indicating the required parameter is missing or invalid.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Invalid Field Values: Providing incorrectly formatted dates or unsupported status values may cause the API to reject the request.
- Debug Logging: Enabling debug logging can help trace request URLs, payloads, and responses to diagnose issues.
- Network Issues: Connectivity problems to the Vendus API will result in request failures; verify network access and API availability.
Links and References
- Vendus API Documentation (official site referenced in node description)
- n8n Expressions Documentation (for using expressions in parameters)