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
The node integrates with Everest TMS (Transport Management System) to perform various operations on different resources. Specifically, for the Invoice - Delete operation, it deletes an invoice identified by its ID from the Everest system.
This node is useful in scenarios where you need to automate invoice management within your transport management workflows, such as removing outdated or incorrect invoices programmatically.
Example use case: Automatically deleting invoices that are canceled or no longer valid after certain business rules are met, helping keep your accounting data clean and up-to-date.
Properties
| Name | Meaning |
|---|---|
| Invoice ID | The ID of the invoice to delete |
Output
The output is a JSON array containing the result of the delete operation for each input item. Typically, this will include confirmation of deletion or relevant status information returned by the Everest API.
If multiple items are processed, the output will be an array of such results.
No binary data output is expected for this operation.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node uses the Everest API endpoints internally to perform operations.
- No additional external dependencies beyond the configured Everest API credentials.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Invoice ID will likely cause an error from the API indicating the invoice was not found.
- Network or authentication errors if the API key is missing, expired, or incorrect.
Error messages:
"Invoice not found"or similar indicates the specified Invoice ID does not exist.- Authentication errors suggest checking the API key credential configuration.
- General API errors may require inspecting the response message for details.
Resolution tips:
- Verify the Invoice ID exists before attempting deletion.
- Ensure the API key credential is correctly set up and has sufficient permissions.
- Use the "Continue On Fail" option in n8n to handle errors gracefully when processing multiple items.
Links and References
- Everest TMS official API documentation (refer to their developer portal for detailed API specs)
- n8n documentation on creating and using API credentials
- General REST API best practices for error handling and authentication