Tripletex

Connect to Tripletex API v2

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. This is useful in scenarios where customer information changes over time, such as updating contact details, addresses, or switching between private person and business customer status.

Practical examples include:

  • Updating a customer's email or phone number after they provide new contact info.
  • Changing the address details when a customer moves.
  • Modifying the organization number for business customers if it was entered incorrectly or changed.

Properties

Name Meaning
Customer ID The unique identifier of the customer to update (required).
Name Customer's full name (required).
Email Customer's email address.
Phone Customer's phone number.
Is Private Person Boolean indicating if the customer is a private individual (true) or a business (false).
Organization Number Organization number for business customers; only applicable 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 updated customer record as returned by the Tripletex API. This typically includes all customer fields reflecting the new state after the update.

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 network access to https://api.tripletex.no or https://api-test.tripletex.tech is required.

Troubleshooting

  • Validation errors: If the "Customer name" field is empty or missing, the node will throw a validation error before making the API call.
  • Authentication failures: Errors related to invalid or missing API credentials will prevent successful requests.
  • Invalid Customer ID: Providing a non-existent or incorrect customer ID will result in API errors indicating the resource was not found.
  • Field constraints: Ensure that fields like "Organization Number" are only set when "Is Private Person" is false; otherwise, the API may reject the request.
  • Network issues: Connectivity problems to the Tripletex API endpoints can cause timeouts or connection errors.

To resolve these issues:

  • Double-check required fields before execution.
  • Verify API credentials and environment configuration.
  • Confirm the customer ID exists in the system.
  • Follow the API documentation for valid field values and constraints.

Links and References

Discussion