Actions55
- Client Actions
- General Actions
- Mission Actions
- Agent Actions
- Invoice Actions
- Contact Actions
- Alert Actions
- Walter Actions
- Notification Actions
- Webhook Actions
- Route Actions
- Export Actions
Overview
This node integrates with the Everest Transport Management System (TMS) to update invoice records. It allows users to modify various fields of an existing invoice by specifying its ID and the fields to update. This is useful in scenarios where invoice details need correction or updating after creation, such as changing payment status, adjusting amounts, or updating descriptive information.
Practical examples include:
- Marking an invoice as paid and setting the payment date.
- Updating the invoice title or description to reflect changes.
- Adjusting amounts excluding or including tax after a revision.
- Changing the invoice type from estimate to final invoice.
Properties
| Name | Meaning |
|---|---|
| Invoice ID | The unique numeric identifier of the invoice to update. |
| Update Fields | A collection of fields that can be updated on the invoice: |
| - Type | Type of invoice; options: Estimate, Invoice |
| - Title | Title of the invoice |
| - Description | Description text for the invoice |
| - Name or Company | Company name associated with the invoice |
| - Address | Address related to the invoice |
| - Amount Excluding Tax | Numeric amount before taxes |
| - Amount Including Tax | Numeric amount including taxes |
| - Created For | Identifier or name of the entity the invoice was created for |
| - Created By | Identifier or name of the creator of the invoice |
| - Validated | Whether the invoice is validated; options: Yes, No |
| - Status | Payment status; options: Paid, Unpaid |
| - Date Paid | Date and time when the invoice was paid |
| - Mission References | Comma-separated string of mission references related to the invoice |
Output
The node outputs a JSON array containing the updated invoice data returned from the Everest TMS API. Each item in the output corresponds to one processed input item and includes the updated invoice fields reflecting the changes made.
If binary data were involved (not indicated here), it would typically represent files or attachments related to invoices, but this node focuses on JSON data updates only.
Dependencies
- Requires an active connection to the Everest TMS API via an API key credential configured in n8n.
- The node depends on the Everest API endpoints to perform update operations on invoices.
- Proper permissions on the Everest account are necessary to update invoice records.
Troubleshooting
Common Issues:
- Invalid or missing Invoice ID will cause the update to fail.
- Providing invalid field values (e.g., non-numeric amounts) may result in API errors.
- Network or authentication issues with the Everest API can prevent successful updates.
Error Messages:
- Errors returned from the Everest API will be propagated, often indicating the reason (e.g., "Invoice not found", "Invalid field value").
- If the node is set to continue on failure, errors will appear in the output as error messages per item.
Resolutions:
- Verify the Invoice ID exists and is correct.
- Ensure all field values conform to expected types and formats.
- Check API credentials and network connectivity.
- Use the node's "continue on fail" option to handle partial failures gracefully.
Links and References
- Everest TMS official documentation (for API details and invoice management)
- n8n documentation on creating and using custom nodes
- General REST API best practices for updating resources