Billing Booth One icon

Billing Booth One

Interact with Billing Booth One API

Actions476

Overview

This node interacts with the Billing Booth One API to update customer information. It is designed to update various customer details such as name, customer group, organisation, contact information, billing preferences, and other optional fields. This node is useful in scenarios where customer data needs to be programmatically updated in the Billing Booth system, for example, updating customer contact details, billing settings, or status changes.

Use Case Examples

  1. Updating a customer's name and contact email after receiving updated information from a CRM system.
  2. Changing a customer's billing group or organisation affiliation based on internal business processes.
  3. Modifying invoice delivery preferences or payment terms for a customer to reflect new agreements.

Properties

Name Meaning
Id Unique identifier of the customer to update.
Name Customer's name to be updated.
Customer Group Id Identifier of the customer group the customer belongs to.
Organisation Id Identifier of the organisation the customer belongs to.
Additional Body Fields Optional additional fields to update various customer attributes such as reference, type, vulnerability status, address, contact details, invoice delivery methods, payment terms, status, and timestamps.

Output

JSON

  • data - Response data from the Billing Booth API after updating the customer.

Dependencies

  • Billing Booth One API
  • API authentication token (Bearer token)

Troubleshooting

  • Ensure the 'Id' property is correctly set to the unique identifier of the customer to update; otherwise, the API call will fail.
  • Verify that the API base URL and authentication token are correctly configured in the node credentials.
  • If required fields like 'Name', 'Customer Group Id', or 'Organisation Id' are missing or invalid, the update operation may be rejected by the API.
  • Check that JSON fields such as 'address', 'tariffs', and 'tags' are properly formatted JSON strings to avoid parsing errors.
  • If the node throws an error about missing binary property, ensure the specified binary property exists in the input data or disable binary data usage.

Links

Discussion