Actions15
Overview
This node integrates with the Tripletex API v2 to manage customer data. Specifically, the "Update Customer" operation allows users to modify existing customer records by providing the customer's ID and updated details such as name, contact information, address, and organizational data.
Common scenarios for this node include:
- Keeping customer records up-to-date in an accounting or ERP system.
- Automating updates when customer information changes in other systems.
- Synchronizing customer data across multiple platforms.
For example, if a customer's phone number or email changes, this node can be used within an n8n workflow to update that information automatically in Tripletex.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to update (required). |
| Name | The customer's full name (required). |
| The customer's email address. | |
| Phone | The customer's phone number. |
| Is Private Person | Boolean indicating if the customer is a private individual (true) or a business (false). |
| Organization Number | The organization number for business customers (only shown if Is Private Person is false). |
| Address Line 1 | First line of the customer's address. |
| Address Line 2 | Second line of the customer's address. |
| Postal Code | Postal code of the customer's address. |
| City | City of the customer's address. |
| Country | Country code of the customer's address (default is "NO"). |
Output
The node outputs JSON data representing the response from the Tripletex API after updating the customer. This typically includes the updated customer object with all its fields as stored in Tripletex.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Tripletex API.
- The node uses the Tripletex environment setting to determine whether to connect to the test or production API endpoint.
- Proper configuration of the API credentials in n8n is necessary for successful requests.
Troubleshooting
- Validation errors: If required fields like "Customer name" or "Customer ID" are missing or empty, the node will throw a validation error before making the API call.
- Authentication failures: Errors related to invalid or missing API credentials will prevent the request from succeeding. Ensure the API key credential is correctly set up.
- API errors: If the Tripletex API returns an error (e.g., customer not found, invalid data), the node will return the error message in the output JSON.
- Network issues: Connectivity problems may cause HTTP request failures; verify network access to the Tripletex API endpoints.
To resolve common errors:
- Double-check all required input parameters.
- Verify API credentials and permissions.
- Review the error messages returned in the node's output for specific API-related issues.
Links and References
- Tripletex API Documentation (official API docs)
- n8n Documentation (for general usage of nodes and credentials)