Tripletex

Connect to Tripletex API v2

Overview

This node integrates with the Tripletex API v2 to manage 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 management workflows such as removing obsolete or incorrect customer entries from your Tripletex account directly within an n8n workflow. For example, when a customer unsubscribes or is no longer active, this node can be used to delete their record automatically.

Properties

Name Meaning
Customer ID The unique identifier of the customer to delete. This is required to specify which customer record should be removed.

Output

The output JSON contains the response from the Tripletex API after attempting to delete the specified customer. Typically, for a successful DELETE request, the API may return an empty object or confirmation message indicating the deletion status.

No binary data is produced by this operation.

Example output JSON might look like:

{}

or an error structure if deletion fails:

{
  "error": "Error message describing the failure"
}

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 https://api.tripletex.no (production) or https://api-test.tripletex.tech (test) is necessary.

Troubleshooting

  • Validation Errors: If the Customer ID is missing or empty, the node will throw a validation error before making the API call.
  • Authentication Failures: Ensure that the API key credential is correctly configured and has sufficient permissions to delete customers.
  • API Errors: Common errors include trying to delete a non-existent customer or one that cannot be deleted due to dependencies in the system. The API response will contain error details.
  • Network Issues: Verify network connectivity to the Tripletex API endpoints.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if deletion fails for some, returning error details in the output JSON.

Links and References

Discussion