Billwerk icon

Billwerk

Automate your subscription business with billwerk

Actions27

Overview

The Billwerk node for n8n enables automation of subscription business processes by integrating with the Billwerk API. Specifically, the Customer → Update operation allows you to update existing customer records in your Billwerk account. This is useful for keeping customer information synchronized between Billwerk and other systems (e.g., CRM, ERP), updating contact details, company data, or custom fields as part of automated workflows.

Practical examples:

  • Automatically update a customer's address when they change it in your CRM.
  • Sync external identifiers or notes from another system into Billwerk.
  • Batch-update VAT IDs or email addresses for compliance or communication purposes.

Properties

Name Type Meaning
Customer ID String The unique identifier of the customer to update in Billwerk.
Customer Data Collection A group of fields containing the new or updated customer information.
└ Customer External ID String An external reference for the customer (e.g., foreign key from another system).
└ Company Name String The name of the customer's company.
└ First Name String The customer's first name.
└ Last Name String The customer's last name.
└ VAT ID String The company's VAT identification number (validated by Billwerk).
└ Email String The customer's email address.
└ Phone Number String The customer's phone number.
└ Notes String Free-text notes about the customer.
└ Address Collection The customer's address details.
  └ Street Name String Street name of the address.
  └ House Number String House/building number.
  └ Line 1 String Additional address line.
  └ Postal/ZIP Code String Postal or ZIP code.
  └ City String City name.
  └ State String State or region.
  └ Country String Country in ISO-3166 alpha-2 format (e.g., "DE" for Germany).
└ Custom Fields FixedCollection List of custom fields to set on the customer record. Each field has a name and value.

Output

The node returns a JSON object representing the updated customer record as received from the Billwerk API. The structure typically includes all standard and custom fields of the customer after the update.

Example output:

{
  "Id": "12345",
  "ExternalCustomerId": "ext-001",
  "CompanyName": "Acme Corp",
  "FirstName": "John",
  "LastName": "Doe",
  "VatId": "DE123456789",
  "EmailAddress": "john.doe@example.com",
  "PhoneNumber": "+49123456789",
  "Notes": "Preferred customer",
  "Address": {
    "Street": "Main St",
    "HouseNumber": "42",
    "AddressLine1": "",
    "PostalCode": "12345",
    "City": "Berlin",
    "State": "",
    "Country": "DE"
  },
  "CustomFields": [
    { "name": "LoyaltyLevel", "value": "Gold" }
  ]
}

Note: The actual output fields may vary depending on the Billwerk API response.

Dependencies

  • External Service: Requires access to the Billwerk API.
  • API Credentials: You must configure valid Billwerk API credentials in n8n under the credential type billwerkApi.
  • n8n Configuration: No additional environment variables are required beyond the API credentials.

Troubleshooting

Common issues:

  • Invalid Customer ID: If the provided Customer ID does not exist, the node will throw an error indicating that the customer was not found.
  • Validation Errors: If required fields (such as Address) are missing or if the VAT ID is invalid, the Billwerk API may reject the request with a validation error.
  • Authentication Failure: Incorrect or missing API credentials will result in authentication errors.

Error handling:

  • If "Continue On Fail" is enabled, errors for individual items will be returned in the output as { "error": "Error message" } objects.
  • Otherwise, the workflow execution will stop on the first encountered error.

Links and References

Discussion