Actions15
Overview
This node connects to the Tripletex API v2 and allows managing customers, products, orders, inventory, invoices, and webhooks. Specifically, for the Customer - Delete operation, it deletes a customer record identified by a given Customer ID.
Typical use cases include automating customer data cleanup or removal workflows in accounting or ERP systems integrated with Tripletex. For example, when a customer is no longer active or has requested data deletion, this node can be used to remove their record from Tripletex automatically.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to delete |
Output
The output JSON contains the response from the Tripletex API after attempting to delete the specified customer. Typically, this will be an empty object or confirmation message indicating successful deletion. If an error occurs, the output JSON will contain an error field with the error message.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Tripletex API.
- The node uses the Tripletex API base URL, which switches between test and production environments based on the credential configuration.
- Network access to the Tripletex API endpoints is required.
Troubleshooting
- Validation errors: If the Customer ID is missing or empty, the node will throw a validation error before making the API call.
- API errors: Common errors may include "Customer not found" if the provided ID does not exist, or authorization errors if the API key is invalid or lacks permissions.
- Network issues: Ensure that the n8n instance has internet access and can reach the Tripletex API endpoints.
- To resolve errors, verify the Customer ID correctness, API credentials, and network connectivity.
Links and References
- Tripletex API Documentation (official API docs)
- n8n documentation on creating custom nodes