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 create invoices. It allows users to generate either estimates or official invoices by specifying details such as title, description, client information, amounts, and payment status. This is useful in logistics, transportation, or service businesses where automated invoice generation based on missions or services rendered is needed.
Practical examples include:
- Creating an invoice for completed transport missions with detailed descriptions and client info.
- Generating an estimate before confirming a job.
- Tracking payment status and dates for issued invoices.
Properties
| Name | Meaning |
|---|---|
| Type | Type of invoice: "Estimate" (0) or "Invoice" (1) |
| Title | Title of the invoice, e.g., "Invoice for XXXX" |
| Description | Detailed description of the invoice content |
| Name or Company | Name of the company or individual for whom the invoice is issued |
| Address | Billing address associated with the invoice |
| Amount Excluding Tax | Total amount before taxes |
| Amount Including Tax | Total amount including taxes |
| Created For | Identifier of the entity the invoice is created for (e.g., "client:123") |
| Additional Fields | Optional extra fields: |
| - Created By: who created the invoice (default "platform") | |
| - Validated: whether the invoice is validated ("Yes" or "No") | |
| - Status: payment status ("Paid" or "Unpaid") | |
| - Date Paid: date when the invoice was paid | |
| Mission References | Comma-separated list of mission references related to this invoice |
Output
The node outputs a JSON array where each element corresponds to the result of creating an invoice. The structure typically includes the created invoice's data returned from the Everest API, such as invoice ID, status, and other relevant metadata.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential to authenticate with the Everest TMS API.
- The node uses internal helper functions to make HTTP POST requests to Everest endpoints.
- No additional external dependencies are indicated beyond the configured API authentication.
Troubleshooting
Common issues:
- Missing required fields like title, description, or amounts will likely cause errors.
- Invalid "Created For" identifiers may lead to failures if the referenced client or entity does not exist.
- Incorrect API credentials or network issues can cause authentication or connectivity errors.
Error messages:
- Errors thrown by the Everest API will be surfaced; ensure all required parameters are correctly set.
- If the node is set to continue on fail, errors will be included in the output JSON under an
errorproperty.
Resolution tips:
- Double-check all required input properties.
- Verify API credentials and network access.
- Use valid client or entity identifiers for the "Created For" field.
Links and References
- Everest TMS official documentation (not provided here, but recommended to consult for API details)
- n8n documentation on creating custom nodes and handling API integrations